Re: [Ctool-develop] suggestions to provide a 'real' public API

[Stefan S. <se...@sy...>]

hi again,

here are some more updates on the build system evolution:

Stefan Seefeld wrote:

> * 'make install' should place the headers in <prefix>/include/ctool/
>   and the library in <prefix>/lib such that other programs can
>   detect them there.

the ctdemo tool is now in examples/ctdemo, and a top-level 'Makefile'
will traverse src/ to only build the libs (.a and .so), and then step
into examples/ (and recursively examples/ctdemo/) to build executables.

The libs are built into lib/, ctdemo into bin/. 'make install' installs
the libs into $(prefix)/lib, and the headers into $(prefix)/include/ctool.

Are there other examples to build beside ctdemo ? Should any of them
get installed ?
Also, it would be nice if the test executions would be integrated into
the build system, i.e. 'make test' in the toplevel directory should traverse
the 'regression/' subdir (should we rename that 'test/' ?) and do all the
necessary things.

Oh, and all this works well also if the build tree is outside the source tree.
Here are the required steps:

$ cd ctool
$ cvs update
$ ./autogen.sh
$ mkdir ../ctool-build
$ cd ../ctool-build
$ ../ctool/configure
$ make

All this new build system stuff still needs some refinement, but the basic
infrastructure is in place. I hope to get this new build system up to speed
with everybody's help so it can replace the old Makefile(s) in the
not-so-distant future.

Regards,
		Stefan

PS: now it would really be great if there were any docs to build, i.e. 'make doc'...
     <wink/>