Jan,
> I tried to strip the kpathsea lib from texk, but it wouldn't
> configure without a tex installation (which I don't have in my
> cross-build environment).
>
> Two questions:
>
> * How did you configure+ compile kpathsea? After stripping kpathsea
> from texk, a number of configure files were missing: klibtool,
> config.guess etc. after adding all missing stuff, kpathsea wouldn't
> configure without fooling it to find a TeX distribution. After that,
> it wouldn't compile:
>
I have little experience in cross-compiling, but I think the problem here is
that the customised libtool (klibtool) expects to build kpathsea as part of
the texk tree.
So I unpacked the whole texk-7.2.tar.gz.
Ran ./configure to configure the lot. No configure arguments required. Then
cd kpathsea && make.
No problems. A few warnings about __cdecl being redefined. That was it. I
know it is a bit of a pain having to unpack and configure everything.
Having kpathsea certainly makes building lilypond easier. The build process
can find the font files etc on its own.
> * Like I said, I'm currently distributing binaries for Windows.
> Now that
> you're able to build with kpathsea support, and I'm not, would you be
> willing to build and or distribute them? I'd like to be able to build
> them myself (too), but I can't do any testing anyway.
I certainly could build them and make them available. I am not sure how
long I am going to be active with windows. The reason I came to lilypond is
that I am planning to switch to linux, and wanted to make sure that I could
get software for the things I need to do - like music typesetting. However,
now the build is set up it wouldn't be much to keep doing them. Isn't Jeff
Reed still providing them?
>
> > I'm using MikTex 1.20e.
> >
> > What other cygwin issues are there?
>
I might have a look at some of these, when I have no real work to do.
> O, and pl75 fixes a number of small bugs, you'll want to try that.
>
Yes, works fine.
I have had some problems running mudela-book to build the dvi manuals. One
of the system() commands is actually 2 commands separated with a ';'. Win95
(poor thing!) isn't up to that.
Here is a patch which works fine and shouldn't upset any else!
--- mudela-book.py Thu May 11 22:33:44 2000
+++ mudela-book.py Sun Jul 30 03:01:22 2000
cwd = os.getcwd ()
include_path = [cwd]
dep_prefix = ''
@@ -694,9 +694,14 @@
texfiles = string.join (tex, ' ')
system ('lilypond %s %s' % (lilyopts, texfiles))
for e in eps:
- cmd = r"""tex '\nonstopmode \input %s'; dvips -E -o %s %s""" % \
+ if os.environ.has_key('OS') and \
+ os.environ['OS'] == 'Windows_95':
+ cmd = r"""ash -c 'tex " \nonstopmode \input %s " ;
dvips -E -o %s %s ' """ % \
+ (e, e + '.eps', e)
+ else:
+ cmd = r"""tex '\nonstopmode \input %s' ; dvips -E -o %s
%s""" % \
(e, e + '.eps', e)
system (cmd)
for g in png:
> Thanks for your efforts + Greetings,
Its good to contribute!
Best wishes,
Mark
