Re: [Denemo-devel] google music notation editor

[Richard Shann]

On Sun, 2009-06-14 at 09:10 -0500, Jeremiah Benham wrote:
> On Sun, Jun 14, 2009 at 08:58:18AM +0100, Richard Shann wrote:
> > 
> > whereas, (unless I am in a complete muddle now) it should create new
> > directories (libsmf, src etc) and Makefiles below the current build
> > directory, which then should allow the command make to create a denemo
> > executable in the (newly created) src directory below the current build
> > directory.
> >
> 
> I like the idea of creating subdirectories rather than putting all the .c/h 
> files into one directory. I think its more organized. I will look into 
> creating seperate build directories. Is this an autogen thing that you are 
> using to create seperate build directories? Is what you are trying to do is 
> place all the .o files into seperate build directories and linked?

No. I am not doing anything, novel. It is a standard thing to run
configure, make and make install in an initially empty directory. You
create an empty directory, cd to it and then run configure, make and
make install. The configure command has to be picked up from where you
have downloaded the source to. So in my case I do ../denemo/configure as
that (../denemo) is where autogen.sh has put the configure file. (That
is I have to do autogen.sh in the usual way first). It is the confgure
script which your autogen.sh has generated that is doing the creation of
the directories and placing Makefiles in them.
Try it. It's really easy. And it means you can test building from the
same sources with various configure options, and keep re-building and
testing as you change the single set of sources, without having to go
back to re-configure, as you would if you build in the same directory as
the sources.

Richard