[Coin-discuss] in what order should makes be done

[Laszlo Ladanyi]

I figured out a better way to do automatic dependencies. I'll incorporate that
into the makefiles, after that the output should be half of what it is now.
Also, it is a good idea to print something when invoking another makefile,
just to know where the build process is. I'll add that, too.

-Laci

On Wed, 27 Jul 2005, Michael Hennebry wrote:

> On Wed, 27 Jul 2005, Kasper Bonne Rasmussen wrote:
> 
> >
> >
> > On Tue, 26 Jul 2005, Michael Hennebry wrote:
> > > The documentation, to the degree it exists,
> > > does not make clear what depends on what.
> >
> > The Makefiles call each other as needed. Just enter the directory
> > containing the module you want to build and use gmake, at least that works
> > for me.
> 
> Just the answer I was trying to avoid.
> Whenever I update, something breaks.
> 
> > If it fails, make sure COIN/Makefiles/Makefile.location contains the
> > correct locations for what ever failed and try again.
> 
> Coin's build system is a complex beast, different parts
> of which are maintained by different people.
> Success can be worse than failure if one has not yet
> done the desired tinkering in a module that was brought
> in by a dependency.
> The tinkering has to be done in a large makefile.
> Admittedly, some of the comments do help with this.
> 
> A build produces so much output that it can be hard
> just to detect whether another module was brought in.
> 
> -- 
> Mike   hennebry at web.cs.ndsu.NoDak.edu
> "There are three kinds of people,
> those who can count and those who can't."
> 
> _______________________________________________
> Coin-discuss mailing list
> Coin-discuss at list.coin-or.org
> http://list.coin-or.org/mailman/listinfo/coin-discuss
>