Commit ed305999 authored by Michael Hanus 's avatar Michael Hanus
Browse files

Comments added to Makefile, version number incremented

parent 5bf031f7
......@@ -13,35 +13,41 @@
# Some parameters for this installation
# --------------------------------------
#
# (these parameters might be passed to `make`)
# If the parameter CURRYFRONTEND is set to an executable,
# this executable will be used as the front end for PAKCS.
# Otherwise, the front end will be compiled from the sources
# in subdir "frontend" (if it exists).
export CURRYFRONTEND =
# Is this an installation for a distribution (Debian) package (yes|no)?
# In case of "yes":
# - nothing will be stored during the installation in the home directory
# - the documentation will not be built (since this takes a lot of time)
# - the paramters CURRYLIBSDIR and CURRYTOOLSDIR must be defined and
# refer to the directories containing the Curry system libraries and tools
export DISTPKGINSTALL = no
# In case of an installation as a (Debian) package, the variable
# PAKCSINSTALLDIR should be set to the location where it is finally
# placed after the build (e.g., /usr/lib/pakcs). It is required that
# during the build, this directory does not exist, otherwise
# the build fails. If this variable is set and the installed system will
# be moved to this location after the build, it will be
# In order to build the system in a place different from the place of
# the final installation (e.g., when building it as a (Debian) package),
# the variable PAKCSINSTALLDIR should be set to the location where it
# will be finally installed after the build (e.g., /usr/lib/pakcs).
# It is required that during the build, this directory does not exist,
# otherwise the build fails. If this variable is set and the
# installed system will be moved to this location after the build, it will be
# used as the root directory for all generated components of the system.
export PAKCSINSTALLDIR =
########################################################################
# The major version numbers:
MAJORVERSION=1
# The minor version number:
MINORVERSION=14
# The revision version number:
REVISIONVERSION=1
REVISIONVERSION=2
# The build version number:
BUILDVERSION=7
BUILDVERSION=0
# Complete version:
VERSION=$(MAJORVERSION).$(MINORVERSION).$(REVISIONVERSION)
# The version date:
......@@ -115,8 +121,8 @@ ifeq ($(DISTPKGINSTALL),yes)
else
@rm -f $(MAKELOG)
@echo "Make started at `date`" > $(MAKELOG)
$(MAKE) config 2>&1 | tee -a $(MAKELOG)
$(MAKE) build 2>&1 | tee -a $(MAKELOG)
$(MAKE) config 2>&1 | tee -a $(MAKELOG)
$(MAKE) build 2>&1 | tee -a $(MAKELOG)
@echo "Make finished at `date`" >> $(MAKELOG)
@echo "Make process logged in file $(MAKELOG)"
endif
......
This is PAKCS (the Portland Aachen Kiel Curry system),
an implementation of Curry developed by RWTH Aachen,
PAKCS: The Portland Aachen Kiel Curry system
============================================
PAKCS is an implementation of the multi-paradigm declarative language
[Curry](http://www.curry-language.org) developed by RWTH Aachen,
University of Kiel and Portland State University
(email contact: pakcs@curry-language.org)
This directory contains:
RELNOTES.txt:
`RELNOTES.txt`:
Some information about the current release and changes w.r.t. previous
releases of PAKCS.
RESOURCES.html:
`RESOURCES.html`:
A description of various resources related to PAKCS and Curry.
This is helpful for new users.
INSTALL.txt:
Instructions to install the system.
`INSTALL.txt`:
Instructions how to install the system.
`GITINSTALL.txt`:
Instructions how to install the system from the GIT repository
(only intended for developers).
bin:
A directory containing various scripts that implement the main
commands to execute the components of PAKCS.
`bin`:
A directory containing various executables
to execute the components of PAKCS.
cpns:
`cpns`:
This directory contains scripts and executables for the
Curry Port Name Server (CPNS) which is responsible for managing the
symbolic names assigned to the named ports on a local machine
(see library Ports for more details).
symbolic names assigned to the named sockes and ports on a local machine
(see libraries `NamedSocket` and `Ports` for more details).
curry2prolog:
`curry2prolog`:
This directory contains the compiler from Curry into Prolog which
is the basis of the main component of PAKCS: the interactive
development environment.
currytools:
`currytools`:
This directory contains various tools for Curry
(see the README there for a more detailed description).
docs:
`docs`:
This directory contains some documentation (Curry Report, PAKCS User Manual,
DTD for XML representation of FlatCurry).
examples:
`examples`:
This directory contains a collection of example Curry programs
and test files (prefixed by "test") to check the system using
the currytest tool. All tests can be executed by the shell script
"doTest" in this directory.
`test.sh` in this directory.
`frontend`:
This directory contains the Curry frontend, i.e., a parser for
Curry programs. It is adapted from the parser originally developed for the
[Muenster Curry Compiler](http://danae.uni-muenster.de/~lux/curry/).
frontend:
This directory contains the sources of the Curry front-end, i.e., a parser
for Curry programs. It is adapted from the parser of the Muenster Curry
Compiler (MCC).
`include`:
This directory contains some resources which are included
by various tools delivered with KiCS2.
lib:
`lib`:
This directory contains a collection of standard libraries
implemented in Curry (including the standard prelude).
scripts:
This directory contains scripts used in PAKCS.
`scripts`:
This directory contains some templates for scripts used in PAKCS.
`testsuite`:
This directory contains a collection of Curry programs
implementing unit tests to check the functionality of the system using
the currytest tool. All tests can be executed by the shell script
`doTest` in this directory. Since these test suite is based on
a test tool which is no longer supported, one should use the new
tests contained in `testsuite2`.
`testsuite2`:
This directory contains a collection of Curry programs
implementing unit and property tests to check the functionality
of the system using CurryCheck. All tests can be executed by the
shell script `test.sh` in this directory.
tools:
`tools`:
This directory contains various tools for PAKCS
(see the README there for a more detailed description).
www:
`www`:
This directory contains scripts and executables for the
event handler server that is required to execute dynamic web
pages implemented with the libraries HTML or WUI.
......
PAKCS: Release Notes
====================
Release notes for PAKCS Version 1.14.1 (February 9, 2017)
---------------------------------------------------------
Release notes for PAKCS Version 1.14.2 (February 21, 2017)
----------------------------------------------------------
Changes to version 1.14.0:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment