Nicolas Sceaux writes:
> Here is a patch that fixes the python-module rules. Also, GNUmakefile
> is missing from parser/
Thanks. Applied, and really added parser/GNUmakefile.
I'll gladly apply patches like this, but if you feel like getting to
know tla better, you can easily setup your own bran
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> I've applied the patch, executed the split instructions and committed
> to my TLA archive, lilypond--lily-as-lib branch, with a few minor
> --srcdir build issues fixed.
Here is a patch that fixes the python-module rules. Also, GNUmakefile
is missing
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
>> I've applied the patch, executed the split instructions and committed
>> to my TLA archive, lilypond--lily-as-lib branch, with a few minor
>> --srcdir build issues fixed.
>
> I cannot get it:
>
> nicola
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> I've applied the patch, executed the split instructions and committed
> to my TLA archive, lilypond--lily-as-lib branch, with a few minor
> --srcdir build issues fixed.
I cannot get it:
nicolas:~/cvs> tla register-archive [EMAIL PROTECTED]
http://
Nicolas Sceaux writes:
> Maybe AC_DISABLE_STATIC or AC_DISABLE_SHARED in configure.in, then.
Ok. I haven't got the time to look at this now, there also is a litte
problem with libtool.m4; apparently my libtoolize patch to autogen.sh
does not work (at least not with --srcdir builds, or it's some
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Nicolas Sceaux writes:
>
>> What I have understood is that it's a matter of --disable-shared or
>> --disable-static during configure.
>
> Ok. It's a small thing, but I we'll want to disable on of them by
> default, I guess. I'd like to make the pac
Nicolas Sceaux writes:
> What I have understood is that it's a matter of --disable-shared or
> --disable-static during configure.
Ok. It's a small thing, but I we'll want to disable on of them by
default, I guess. I'd like to make the packagers (who need to build
both the static -dev and shared
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wri
> I've opened a branch: lilypond_2_3_5b to see if we can get all
> problems sorted out before breaking HEAD.
>
> Other things that should be fixed:
>
> * all files get compiled twice
What I have understood is that it's a matter of --disable-shared or
--
Nicolas Sceaux writes:
> The attached patch might give a start. "libtoolize --force --copy" has
> to be run in order to update the config.guess, config.sub and
> ltmain.sh files. Also, a libtool.m4 should be copied in stepmake/.
I've taken care of this and made a fix for midi.so.
> I have not lo
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
>> Ok. Actually I was fishing for patches.
>
> ho, hum, now I'm confused (not for the first time these days).
>
>> Didn't you have something
>> useful already? We could just open a CVS branch to experime
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Ok. Actually I was fishing for patches.
ho, hum, now I'm confused (not for the first time these days).
> Didn't you have something
> useful already? We could just open a CVS branch to experiment on.
I did have something for using libtool, but lo
Nicolas Sceaux writes:
>> Ok, so let's have a look how to go about this. Nicolas, any thoughts?
>
> Sorry, I could not say anything that Han-Wen had not already summed up...
> When my vague ideas become clearer, I'll post them
Ok. Actually I was fishing for patches. Didn't you have something
u
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Han-Wen Nienhuys writes:
>
>>> However, if you want me to try to go on and polish lily-as-a-lib, I'll
>>> do that.
>>
>> On 2nd thought, I think it's a worthwhile thing to pursue.
>
> Ok, so let's have a look how to go about this. Nicolas, any thoug
Han-Wen Nienhuys writes:
>> However, if you want me to try to go on and polish lily-as-a-lib, I'll
>> do that.
>
> On 2nd thought, I think it's a worthwhile thing to pursue.
Ok, so let's have a look how to go about this. Nicolas, any thoughts?
> There are 3 things:
>
> * Turning lily into a li
Han-Wen Nienhuys writes:
> There are 3 things:
What about 4:
* think about library interface (mostly ly: now)
It would be nice (TM) to have something like:
(ly:parse-xxx ) -->
(ly:render ) -->
so that lib users can: save parsed music tree, render music from music
tree created from d
Nicolas Sceaux writes:
> As it is now, all is fine for me, I can try little hacks.
Ok.
> However, if you want me to try to go on and polish lily-as-a-lib, I'll
> do that.
I'm not sure. It feels as a good step that we'll maybe need in about
a year, so I think it can wait.
Jan.
--
Jan Nieuwenh
[EMAIL PROTECTED] writes:
> Wed, 26 May 2004 11:23:38 +0200, tu a dit :
>
> > Nicolas Sceaux writes:
> >> I was experimenting this week end with lilypond called directly from
> >> scheme (without using lilypond-bin).
>
> > That's interesting. If you want I can help with install rules, but w
Bonjour Jan!
Wed, 26 May 2004 21:56:10 +0200, tu as dit :
> Han-Wen Nienhuys writes:
>> Also, we will run into platform dependencies. I fear that we might
>> need libtool to build the shared lib portably.
> We might, but we'll worry later, if necessary. A --disable-shared
> configure opti
Wed, 26 May 2004 11:23:38 +0200, tu a dit :
> Nicolas Sceaux writes:
>> I was experimenting this week end with lilypond called directly from
>> scheme (without using lilypond-bin).
> That's interesting. If you want I can help with install rules, but we
> should figure out what to put in th
Han-Wen Nienhuys writes:
> Also, we will run into platform dependencies. I fear that we might
> need libtool to build the shared lib portably.
We might, but we'll worry later, if necessary. A --disable-shared
configure option may take good enough care of broken platforms too...
Jan.
--
Jan Ni
[EMAIL PROTECTED] writes:
> Nicolas Sceaux writes:
>
> > I was experimenting this week end with lilypond called directly from
> > scheme (without using lilypond-bin).
>
> That's interesting. If you want I can help with install rules, but we
> should figure out what to put in the library, and how
Nicolas Sceaux writes:
> I was experimenting this week end with lilypond called directly from
> scheme (without using lilypond-bin).
That's interesting. If you want I can help with install rules, but we
should figure out what to put in the library, and how to install
lilypond-bin. LilyPond as a
Hello,
I was experimenting this week end with lilypond called directly from
scheme (without using lilypond-bin). I had to make few changes in the
stepmake rules in order to generate a .so shared library. Here is a
patch, just in case of... `make shared-lib' generates the lib; this is
rudimentary,
23 matches
Mail list logo
