"Jeroen N. Witmond" <[EMAIL PROTECTED]> writes: >> I threw a switch last night that causes all the .o files to end up at >> the root of the make (src, for instance) rather than alongside their >> src files. After continually stumbing over the .o files in the source >> directory, I decided this was better behavior. There are no conflicts >> that I know of yet, and the nice part is that there's not a lot of >> other code in src. >> >> Feedback on these decisions is welcome. >> > > To prevent stumbling over .o files (or any generated file, for that > matter) in the source directory, you can use a feature from the > automake/configure tools that allows you to build outside the source > directory. (The source distribution of gcc uses this, for instance.) > Simply `cd builddir && /path/to/sourcedir/configure --whatever`.
Ah, yes. This is what I meant. Xerces-C should *not* enforce any specific build dir, but instead should enable the user to set it. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
