lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make scripts on Windows (cygwin)


From: David Kastrup
Subject: Re: make scripts on Windows (cygwin)
Date: Sun, 21 Oct 2012 14:01:58 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)

Federico Bruni <address@hidden> writes:

> I'd like to update the italian translation before 2.16.1 release.
> I have a problem: I'm abroad until Friday and I only have a Windows laptop.
>
> I guess that you will recommend LilyDev. Not tried yet, as I'm not
> really interested in compiling Lilypond.
> I just need to be able to run some make commands for the translation
> maintenance.
>
> I've installed Cygwin and the packages needed for compiling (well, I
> hope so).

If you are not interested in wasting the rest of your week (and probably
the next month) throwing good time after bad time fighting things that
almost, but not quite work, you should seriously give LilyDev a try.
Its main motivation is not having gcc available (that one is perfectly
available standalone on Windows) but rather all the little things when
you "just need to be able to run some make commands".

Disclaimer: I have not touched either Windows, Cygwin, or virtual
environments for years.  But I still habe the scars to show.

> But I get an error when I run configure:
>
> $ ./configure
> configure: error: cannot run /bin/sh stepmake/bin/config.sub
>
> $ sh
> sh.exe          shasum          shimeng.dll     shrpubw.exe
> sha1sum.exe     shdocvw.dll     shimgvw.dll     shsetup.dll
> sha224sum.exe   shell32.dll     shlwapi.dll     shsvcs.dll
> sha256sum.exe   shellstyle.dll  shmtool.exe     shuf.exe
> sha384sum.exe   shfolder.dll    shopt           shunimpl.dll
> sha512sum.exe   shgina.dll      shpafact.dll    shutdown.exe
> shacct.dll      shift           shred.exe       shwebsvc.dll
>
> $ sh configure
> configure: error: cannot run /bin/sh stepmake/bin/config.sub
>
>
> Can any Windows user help me?

Well, Cygwin has an idea of where /bin is situated.  ls /bin might tell
you that.  Or maybe not.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]