Re: [Denemo-devel] updated Makefile.am

[Jeremiah Benham]

On Thu, 2008-12-11 at 15:01 +0000, Richard Shann wrote:
> On Thu, 2008-12-11 at 08:16 -0600, Jeremiah Benham wrote:
> > On Thu, 2008-12-11 at 08:32 +0000, Richard Shann wrote:
> > > On Wed, 2008-12-10 at 10:13 -0600, Jeremiah Benham wrote:
> > > > I updated Makefile.am to include CheckPitchs as a symlink into
> > > > educational. I read up on debian package management and found out as
> > > > long as you change this in the rules file everything is fine with out
> > > > install_data_hook from
> > > > 
> > > > $(MAKE)
> > > > 
> > > > to:
> > > > 
> > > > $(MAKE) install DESTDIR=$(CURDIR)/debian/denemo
> > > > 
> > > > 
> > > > This sets up a staging directory to temporarily install into while
> > > > making. 
> > > Hmm, does this mean we cannot simply create symlinks below actions/menus
> > > and have them appear in the final installation? 
> > 
> > I don't know if that would work. I can try it. I think I read somewhere
> > git supports symlinks. 
> > 
> > > Would the procedure be
> > > to create the symlink and then add a line to denemo/Makefile.am?
> > 
> > They method I have seen documented is to create symlinks by placing a
> > line in denemo/Makefile.am. Then the link is created on a make install. 
> I get it - that would be ok (just one thing to do), though not quite so
> obvious as creating the symlink in git & letting the make system take
> care of what to do with it.

I just created a symlink in denemo root directory from MIDI/CheckPithes
to Educational. It did not work. It only worked if I was in The
educational directory and created the symlink like ln
-s ../../MainMenu/blah blah/MIDI/CheckPitches .

Then when I did:
make dist

It converted the link into a copy. So I think if we want to do symlinks
then we need to place it in the Makefile.am

Jeremiah



> > ./autogen.sh and ./configure needs to be run first though. this is not
> > big deal unless we are creating script files every day that require
> > symlinks. Then it would be painful to go through these hoops. 
> > 
> > > If so, perhaps we could have a script to run to fix things up when
> > > installing a symlink?
> > 
> > I just spent 2 days writing a script to recursively generate
> > Makefiles.am's in the actions directory. Then I stumbled on this
> > $DESTDIR that is used for staging that would work with are
> > install_data_hook. Oh well. I learned alot about bash scripting in the
> > process so it was not all for not. 
> > 
> > > > 
> > > > I also updated src/Makefile.am to include all the scheme related .h
> > > > files that were not there before. 
> > > I haven't done a fresh installation in ages - was it broken until now?
> > 
> > These files were not being included when you type in:
> > 
> > make dist
> > 
> > There are now.
> Oh, right, I see.
> >  I am preparing things to be packaged up. I don't know how
> > close we are to release but I just wanted to make sure everything is all
> > set up and ready to go when we get there.  
> Yes, that's a good move. We do have a lot more to offer, and should
> release, but I think there may be one or two regressions still lurking.
> 
> Well, one I already reported is that typically on startup the
> Notes/Rests menu has items that don't belong there in the active mode,
> which would confuse a newcomer. And, of course, there is the windows
> build, we really need someone to take that on.
> 
> I'll see about fixing the Notes/Rests menu on startup. I can probably
> fix that with a quick mode shuffle during the init.denemo script - I
> have fixed the grace note intialization bug that way. Or maybe the mode
> choice is being made too early.
> 
> Richard
> 
> 
> > Jeremiah
> > 
> > > > configure.in was updated to add support for smylinking in a Makefile.am
> > > I'm glad you are on top of this stuff!
> > > Richard
> > > 
> > > 
> > 
>