Sorry for the duplicate message, but I wanted to collect a range of opinions.

I'd like to clean up the RDKit build "system". My goal is to put
together something that makes the end user's life simpler, i.e. that
doesn't require quite so much manual configuration in order to build
and that handles dependencies more automatically.

The two options I'm considering are:
 1) The various gnu tools (autoconf, libtool, and automake)
http://sources.redhat.com/autobook/
 2) Boost.Build http://www.boost.org/doc/html/bbv2.html

The gnu tools have the advantage of being "standard" (everyone knows
the "./configure; make; make install" dance) and certainly have a
large user base, but they are (IMO) somewhat constrained by the fact
that, in the end, they're still using makefiles.

Boost.Build is more appealing, but it's a bigger shift. It is also
somewhat less standard, but it's easily available for every system
where the RDKit will run (since the RDKit requires the Boost libs) and
doesn't require installation (you only need the bjam executable).

Regardless of which option we choose, this isn't going to be
particularly fun to do, so I'd like to get it "right" the first time
so that the pain doesn't have to be repeated in a year.

Anyone have experiences to share, suggestions, or opinions?

-greg

Reply via email to