This page is for communitating features of the new BuildTools version 1.0

One this page we can share our thought on what should go into a new version of the BuildTools.

Technical Aspects

Use of newer autotools

Changing:

1. Autoconf 2.61 (currently 2.59). Advantages?

1. Automake 1.10 (currently 1.9.6). Advantages?

1. Libtool stays at 1.5.22; nothing new has been released yet. However, that version has a number of bugs that we currently patch "by hand". Maybe we can use a new non-official version? All that is needed is really the libtool.m4 file, and we might be able to distribute a good working version together with BuildTools? This way, we can also easily suggest fixes to the Libtool developers and include their changes.

AW: I will start with this on my settings now, using Bonmin as the example. At some point I will also create a pseudo "CoinAll" project which we can use to test the new coin.m4 etc on.

Creating libtool only once

At the moment, the libtool script is created for every subprojects, and those annoying timeconsuming tests are run many times. It should be possible to change that so that the libtool script is created only once in the packages base directory.

AW: I'm going to look into this.

Avoiding aclocal.m4 creation

At the moment, we create a aclocal.m4 file in maintainer mode, that combines libtool.m4 and our coin.m4. Instead, we can probably use the -I flag for aclocal. Also, we think about disaggregating coin.m4 into different files, if the tests are truely in dependent.

AW: I'm going to look into this.

New or improved features

Different handling of DOS compilation

Lou's suggested handling of --enable-doscompile?