-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ralph Hempel wrote: > I am shortly going to ITP my first package (Lua) and have a few > questions: > > 0. Should I use cygport to build my package? I've got a clean > source tree and I've made changes in a separate tree to make > it easier to generate diffs.
If you want to package lua, you may find this useful: http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/lang/lua5.1/ > Also, I've designed my own make scripts to build everything > correctly in a separate output tree, ie I don't build in the > source tree. cygport provides lndirs() for use in those packages that weren't meant for out-of-tree builds. > 1. Should my build make just a .dll file to link against, or should > I also provide a .a library for static linking? A DLL is a necessity on Cygwin for most libraries; whether to make a static library also depends on the package. Ports' lua package provides both. > 2. If I'm planning on adding a few "standard" Lua libraries like > LuaSQL, LuaFileSystem, and LuaSocket, should they be separate > ITPs? Yes. > 3. I'm currently using Cygwin 1.7 and gcc-4 to build and test > this out, but should I do it for 1.5 as well? gcc-4.3 is not yet finalized; it should not be used for building packages going into the distro. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkSQGoACgkQpiWmPGlmQSMGyQCdEEwEQBNI3CuvuER4QAuGh4ih DUgAnjQz+V9wZPTydylq2zxtDQ3+8sAo =yEJY -----END PGP SIGNATURE-----
