g-b-s and bin dir

[Warren Young]

I'm attempting to create my first Cygwin package, and decided to use the 
generic-build-script method.

The package is ctags (http://ctags.sourceforge.net/), which builds just 
fine out of the box.  With a bit of scripting [*] I have the build 
process automated.  Problem is, the generated binary tarball has no 
binaries in it.  It only has usr/share/doc/*.  I don't see the binaries 
in ctags-$VER/.inst/usr/bin, either.

I don't know if this is because of some nonstandardness in the ctags 
autoconf setup, or if g-b-s is not passing the right options to the 
configure script.

Exuberant Ctags uses autoconf only; no automake.  The install target in 
the top-level Makefile puts the binaries in $(bindir), which is set from 
the corresponding autoconf variable.  As g-b-s runs configure, ${bindir) 
ends up being /usr/bin, so when the g-b-s inst step runs, the binaries 
go to /usr/bin, not to $UNPACKED_TARBALL/.inst/usr/bin.

Who is at fault here, and how do I fix it?



[*] I've attached the build script I'm using.  It's a driver for g-b-s, 
to handle things that I think g-b-s should handle already.  Whoever is 
maintaining g-b-s these days can feel free to rob whatever code they 
want from this.

With this interface, you just say "./build ctags 5.5.4 1" to create 
ctags-5.5.4-1[-src].tar.bz2.  It requires that you have a README file in 
the current directory, which is based on the generic README file from 
the cygwin.com docs; the build script does variable replacement in it 
for package name, version number, and release number.  I've attached my 
original README file so you can see what the build script has to work 
with.  The build script also requires that the original source tarball 
be in the current directory.

This mechanism works best if you have a directory dedicated to a given 
package.  I use ~/src/ctags, for instance.  The build script, the 
README, and any tarballs are here.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: build
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20051027/b1ab3e30/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: README
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20051027/b1ab3e30/attachment-0001.ksh>