This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
First time packager questions
- From: Ralph Hempel <rhempel at bmts dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 05 Nov 2008 19:27:57 -0500
- Subject: First time packager questions
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.
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.
The make scripts even generate a staged version of the final
installation directories to make tarball generation easy.
1. Should my build make just a .dll file to link against, or should
I also provide a .a library for static linking?
It's easy to get mixed up with static and dynamic linking so
I'd rather provide one "standard" way to do this.
2. If I'm planning on adding a few "standard" Lua libraries like
LuaSQL, LuaFileSystem, and LuaSocket, should they be separate
ITPs?
I'd rather build all the libraries at once and provide them in
the build system, since it's a real pain for a typical user to
build these libraries under Cygwin.
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?
I could go back and use Cygwin 1.5 and the standard gcc but
if 1.7 will be out soon, then I'd rather make a clean break.
Cheers, Ralph