1.4.7 building on cygwin

[Gerrit P. Haase]

Hi,

I don't like that part of the lily-build (install) on cygwin.

/bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -d /etc/postinstall
/bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 ./out/post-gs.sh 
/etc/postinstall/ 
&&  /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/post-lily.sh /etc/postinstall/ 
&&  /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/post-miktex.sh /etc/postinstall/ 
&&  /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/post-python.sh /etc/postinstall/ 
&&true
true
/bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -d 
install:        no input file specified
make[2]: [local-install-outfiles] Error 1 (ignored)
true
(/bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -d /etc/profile.d/ || 
true) 
&&  /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/lily-gs.sh /etc/profile.d/ 
&&   /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/lily-miktex.sh /etc/profile.d/ 
&&   /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/lily-python.sh /etc/profile.d/ 
&&   /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/zlily-profile.sh /etc/profile.d/ 
&&   /bin/sh ../.././stepmake/stepmake/../bin/install-sh -c -m 644 
./out/lilypond-profile.sh /etc/profile.d/ 

Is it really neccessary to do this as postinstall/profile.d scripts?
The usual way on cygwin is to add a config script to the dists like iu-config
for the inetutils script.
After installing the binary it is needed to run that script.
It may be useful to do this automatic, if a user just want to install his 
binary stuff and run it immediately, but it is not needed when building on 
cygwin.
BTW it is only useful if one uses the packages you recommend to use 
with lilypond like python 1.5.

Cygwin dist has included python 2.1.1 it is installed in the usual unix way
(including PATH settings).
Cygwin comes with ghostscript (it is in standard PATHs included)
from the script:
[...]
datadir="/usr/local/share/lilypond"

# For direct ps output fonts
GS_FONTPATH="$datadir/afm:$datadir/pfa"

# For direct ps output: ps/lilyponddefs.ps
GS_LIB="$datadir/ps"
[...]
That overrides my own settings.

It is tetex not miktex included  (tetex is in the standard PATH settings 
and if one makes use of it, it is set up correct).
I would like it more if the paths were compiled in the executables,
there should be no problem to setup things for the 'standard' cygwin paths.

Is there a site in wiki or where is in the docu the description where
all needed environment settings are described?

Thanks,

Gerrit


-- 
=^..^=