Jan Nieuwenhuizen wrote:
OK, under bash it still complains about the cygwin1.dll and the missing _ctype_
export.
Under bare bones DOS shell, lilypond.exe still tries to access cygwin1.dll
(missing) and the other one when renamed, sorry to say Jan, but both are still
required.
OK, thank you for renaming the exe files to *.exe as required for windows.
I liked the other directory structure - I know Unix lads think it's crazy but I
like the idea of having my program where I know : in ...\lilypond-Vxxx rather
than the usual Unix tree.
Ok, you will tell me it does not make sense where resources are shared, you have
a point but I'm not sharing Guile or lily resources with any other program at
this point.
I'd love if you could keep the same directory structure as for win.1.2.0 (it
would make it simpler for the layman windows user).
Outstanding :
python scripts to be renamed *.py
still/again that dll issue, sorry to nag you, but will you please tell me why
you really want it, why not forget about it ?
> Hi,
>
> There's another test release at:
>
> http://appel.dyndns.org/lilypond/gnu-windows/lilypond-1.3.38.jcn2.zip
> http://appel.dyndns.org/lilypond/gnu-windows/guile-1.3.4.zip
>
> The double-link bug should be fixed now, hopefully.
>
> LilyPond uses Guile, so get them both. If you don't install in root,
> you'll have to set these:
>
> export LILYPONDPREFIX=<your_root>/Cygnus/usr/share/lilypond
> export GUILE_LOAD_PATH=<your_root>/Cygnus/usr/share/guile/1.3.4
>
> (if you don't use bash, but a strictly dos compatible shell, use
> `set' for `export' and change '/' to '\').
set GUILE_LOAD_PATH=//C/Program/LilyPond-1.3.38/share/guile/1.3.4
In a DOS shell works for me and guile is recognised !!! So don't bother changing
that.
> Until Cygnus' new release (any day now) comes out, you'll need to
> get the cygwin1-net-485.dll.zip too.
>
> Greetings,
>
> Jan.
OK, now further trials in the bare dos shell (after installing both guile shared
directories only, not sources and changing the version number to 1.3.4 in my
Fanchon.ly because it did not like 1.2.0) ly2dvi yields :
===========
.... (snipped lots of traces) ....
programming error: Orphaned score-element. (Continuing; cross thumbs)
programming error: Orphaned score-element. (Continuing; cross thumbs)
[0[//C/Program/LilyPond-1.3.38/share/lilypond/cmtfm/cmti10.tfm]][1][2][3][4][5]p
aper output to Fanchon.tex...ERROR: Unbound variable: regexp?
ly2dvi hmm, I could not find an output file name
===========
And the tex file generated is the one attached to this message along with the
input file (I hope you put my frenglish.ly somewhere useful on your disk becasue
I just use it unconditionnally).
This file, needless to say, works for 1.2.0 (though the contents is not perfect
by any means).
It does the same with my only other self made .ly.
By the way I confirm you don't need either bash or ash at all, just take this
out of ly2dvi and call lilypond directly (unless you have a reason I don't know,
does it have to do with standard error output ?).
Also in the bare dos shell, when I run ly2dvi --help, it ends in :
===========
files may be (a mix of) input to or output from lilypond(1)
ly2dvi Unknown Exit Code
===========
It does not seem to do any harm, but I dislike swear words like these.
Anyway well done, it goes quite a bit further now, but not quite there yet (or
am I missing something ?).
Best regards,
Alain.
Fanchon.ly
Fanchon.tex
