[BuildTools] Revised trunk/coin.m4 with --enable-doscompile

[Andreas Waechter]

Hi,

Lou's changes look great, and I should have included them earlier when he 
had sent them to me.  The good thing is that now we don't have to do that 
detour through me anymore, since Lou has write permission :)

When things have been tested with the trunk version, I can make it stable.

When we are ready to release:

One thing that has changed is that the libtool script should now be 
created in the base directory, so that it can be reused in the 
subdirectories.  For this, the configure.ac file in each project's base 
directory should be changed eventually to make use of this enhancement. 
Since I have more or less permission from the PMs to incorporate 
BuildTools updates, I can do that, and at the same time switch to the new 
stable branch in BuildTools.  Sounds good?

Cheers

Andreas

On Wed, 24 Jan 2007, Ted Ralphs wrote:

> I don't think there's any point in moving things to stable before we test. 
> The purpose of moving to stable is to indicate to users that the code is OK 
> to use, which I don't think it is yet. Of course, the clients of the build 
> tools project are other PMs, so perhaps the same rules are slightly 
> different. Nonetheless, for developers, it makes no difference where the 
> testing version lives. I think the whole point of our scheme is to leave 
> things in trunk until they are ready to be used by non-developers.
>
> Cheers,
>
> Ted
>
> Andreas Waechter wrote:
>> Well, I think we should make the script flexible enough to do either.  And 
>> since right now we are talking about adding a number of changes (such as 
>> reusing the libtool script from the base directory), we should do it with 
>> trunk IMHO.  Later on, it would be great to check everything periodically 
>> instable after less invasive changes.  What do you think?
>
> -- 
> Dr. Ted Ralphs
> Associate Professor
> Industrial and Systems Engineering
> Lehigh University
> (610)758-4784
> tkralphs at lehigh.edu
> www.lehigh.edu/~tkr2
>