bear wrote:
> On Mac I wasn't worried about pkg-config because it will be a binary
> option: running on leopard? yes=use system, no=use ours

But wouldn't it be nice that the only thing you do, on any platform, any
version, is:

./configure
make

When OSAF is shipping official bits we'd probably need to configure such
that we build and ship our own versions of OpenSSL etc. to create the
tarball. We'd need a separate build for .debs that could use proper
dependencies.

> On Windows: use ours

Currently there is no reason it has to be so, as we use the same
compiler that official Windows Python was compiled with. So we could
make configure detect Windows Python etc. and have it use that if
available.


The configure I made is currently really simple, and the changes needed
to change Makefile into Makefile.in are also really simple, just check
the what I put on the leopard branch.


I've been learning the GNU autotools, and here is a good tutorial to
help build configure.in (it talks about other stuff as well):

http://autotoolset.sourceforge.net/tutorial.html

The autoconf manual a lot more, for example here are some ways to write
a check/options to decide whether or not to build with some option:

http://www.gnu.org/software/autoconf/manual/autoconf.html#External-Software


Other nice things we can let configure do is check that all build
requisites are there. Currently our full build can go on for quite some
time before it stops due to some missing thing. In such cases configure
could also tell you what you need to do to correct the issue.

Using configure could also get us closer to getting into Linux
distributions I think, as it is such a common thing to use.

Or if configure syntax feels too archaic, perhaps we should research
(again) if a more python-based build system could be implemented
(heavily customized setup.py in external/, internal/, chandler/ perhaps)?

-- 
  Heikki Toivonen


Attachment: signature.asc
Description: OpenPGP digital signature

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to