| I just went ahead and renamed all the conflicting files.
Original Message:
-----------------
From: ramsdell@mitre.org (John D. Ramsdell)
Date: 01 Feb 2004 10:14:05 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4032] Re: How to configure
"gogins@pipeline.com" writes:
> The advantage of my new build system is that extending Csound will
> require merely adding new sources to the one Makefile.am.
Some people think that the single Makefile.am approach to a build
system is superior to the Makefile.am per directory approach. In
fact, this is the approach I tried first for the csound module. It
failed for me because there are so many files named main.c in the
various utility directories. To make it work, you must make sure
there are no duplicate file names anywhere in the directory tree.
Since I didn't think I could rename files, I ended up putting
top-level source files into the csound directory, and then everything
worked out after that change.
One other tip, I strongly recommend you create a libtool-less GNU
build system first, and only after it has been shown to be solid code,
add in libtool support.
John
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ . |