Thu Dec 11 09:16:00 GMT 2014
Based on the feedback of Marco and Corinna, I propose the following
cygport file for the chicken upgrade:
# package name
# setup.hint generation
SUMMARY="A practical and portable scheme system."
DESCRIPTION="A practical and portable scheme system.
CHICKEN is a compiler for the Scheme programming language. CHICKEN
produces portable and efficient C, supports almost all of the R5RS
Scheme language standard, and includes many enhancements and
REQUIRES="make gcc-core gcc-g++"
# source and patch files
if [ $AR = "i686" ]
MAKEOPTS="PREFIX=/usr PLATFORM=cygwin ARCH=x86"
elif [ $AR = "x86_64" ]
MAKEOPTS="PREFIX=/usr PLATFORM=cygwin ARCH=x86-64 HACKED_APPLY="
ECHO "Unknown Architecture"
cygmake -i check
Marco has provided me with logs from a 64bit build and those look fine.
There might be a minor nitpick that I don't know how to get to work:
I need to update an internal database of available chicken modules.
However due to the internal design, I need to call this either so
that PREFIX equals DESTDIR during make install or the *installed*
binary after unpacking the cygwin package tarball. Is there an
infrastructure for such things?
The last resort would be to tell the user to do it...
May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.
More information about the Cygwin-apps