This is the mail archive of the
mailing list for the Cygwin project.
RE: Packaging GAP
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin-apps at cygwin dot com>
- Date: Mon, 6 Oct 2003 20:26:27 -0500
- Subject: RE: Packaging GAP
> I am considering trying to package "GAP", a famous group manipulation
> ( http://www-gap.dcs.st-and.ac.uk/~gap/ ). It is very large (full
> install is almost 300MB!), but does compile out of the box on cygwin
> with one tiny exception.
> I haven't tried to package anything before, so am currently reading the
> various guidelines.
I suggest using "Method 2". I also suggest being *very* careful with the sample
script: *don't* do a "./script.sh all" in your source directory or you'll lose
any changes you've made.
> But I thought I would ask early if such a large
> package would be accepted?
Just don't put it in the "Base" category ;-).
> Also, the tiny exception
> Part of the makefile does "strip gap", which fails due to the fact the
> executable is of course called "gap.exe". Many things in cygwin seem to
> work with or without the ".exe", so is this something that should be
> fixed at the "strip" end, or by fiddling with the configure script?
Probably at the script end. New autotools use the variable EXEEXT, and would
specify that in the Makefile.in like:
Then at configure-time, EXEEXT gets set to either nothing or ".exe" or whatever
as appropriate. This is all automatic and you don't have to do anything if
you're using autotools, but if you have a hand-rolled configure you have to do
Gary R. Van Sickle