Fri Oct 27 11:59:00 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
According to djh on 10/26/2006 8:58 PM:
> Forgive my ignorance, but I did read the chapter for managing packages
> and it explained up to boffo being an application and a library
> (external source usage), but I didn't see any reference to what
> exactly goes into the packages with "....-devel" names..
The cygwin-apps archives have discussed this before. Basically, if you
ship a package with .dlls, it is wise to break it into three parts:
- the libboffo1 package, which contains just the dll, so that other
packages that use your dll only depend on this small package (you can then
bump the package name to a higher number if a new release of the dll is
not API compatible)
- the boffo package, which contains the exe that uses the dll, for use on
the command line
- the boffo-devel package, which contains the .h and .a files necessary
for some other package to dynamically compile against libboffo1
If your package does not contain any dlls that might reasonable be used by
external packages, then you don't really need to worry about this.
> Is there any documentation around for how to handle/create the
> <packag-name>"-devel" packages?
cygport is capable of doing this; hopefully you can gather the information
you need about having one project produce multiple packages by reading the
Life is short - so eat dessert first!
Eric Blake email@example.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v184.108.40.206 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Cygwin-apps