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
--disable-static during configure.
> * flower should become libflower-xyz.so
> * lily should become liblily-xyz.so
> - possibly more than one lib: lyparser, lily, gui/pango
> * main should be factored out
OK. What's happening now is that there is a libflower.la, flower using
the `library' stepmake rules, and liblilypond-bin-2.3.5.so (hidden in
lily/out/.libs/) and liblilypond-bin.la, lily using the
`shared-library' stepmake rules (which have to be re-written anyway,
as they mention libflower.la explicitely...)
flower and lily should be using the same rules, which would generate a
shared-library, adding -rpath and -revision (or -version-info?) flags
at the end of the `libtool --mode=link' command.
[hm, I'm just thinking loud, Jan, not explaining you things you
know :)]
There may be several directories:
lily/
MODULE_LIB_DEPS=flower
NAME=lily
STEPMAKE_TEMPLATES= c++ library po
parser/
MODULE_LIB_DEPS=flower lily (?)
NAME=lyparser
STEPMAKE_TEMPLATES= c++ library po
gui/ using the library rules
MODULE_LIB_DEPS=flower lily (?)
NAME=lygui
STEPMAKE_TEMPLATES= c library po
XXXX/ using the executable rules
MODULE_LIB_DEPS=flower lily lyparser lygui
NAME=lilypond-bin
STEPMAKE_TEMPLATES= c++ executable po help2man
I don't know well enough the C++ part to determine which should go
where in that case. maybe:
* parser/
includable-lexer.cc
lexer.ll
my-lily-lexer.cc
my-lily-parser.cc
parser.yy
parse-scm.cc
source.cc
source-file.cc
binary-source-file.cc
input.cc
keyword.cc
* gui/
pangofc-afm-decoder.cc
* XXXX/
main.cc
* lily/
all others.
> * doesn't link with PANGO CVS
>
> Jan.
nicolas
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
