Re: Building on CygWin

[Robin Davies]

>     chmod +x /usr/bin/guile-config
>     rm config.cache
>     LDFLAGS='-L/usr/lib/python2.2/config -lpython2.2.dll' ./configure
>
I haven't actually tried this, but

    $ ls -l  /usr/bin/guile-config
    -rwxr-xr-x    1  Robin D unknown      9320 Apr 22 15:48
/usr/bin/guile-config
         ^   ^  ^
and guile-config executes to the extent that it can give a usage message. I
have been deleting config.cache each time I run ./config as a matter of
routine paranoia.

+x permission on cygwin/Windows ME are always on (actually determined by
snooping for #! at the start of a file , I think), since the Windows FAT
filesystem has no corresponding permission bit.

I don't think that's it.

I'm guessing the problem lies with

/usr/bin/i686-pc-cygwin-guile-config :

 #!/bin/sh
 # target-guile-config.in
    case $1 in
     --version)
      echo "1.4"
      exit 0
      ;;
     compile)
      echo
"-I/home/fred/usr/src/cygwin/cygwin-1.3.10/usr/include -I/home/fred/usr/src/
cygwin/cygwin-    1.3.10/usr/include/w32api"
      exit 0
      ;;
     link)
      echo "-lguile -L/home/fred/usr/src/cygwin/cygwin-1.3.10/usr/lib
/home/fred/usr/src/cygwin/cygwin-        1.3.10/usr/bin/cygwin1.dll"
      exit 0
      ;;
esac

> Good point.  New wiki page:
>
>    http://lilypond.org/wiki?CVS
>
Thanks. I'll try the CVS version tonight.

> >> All in all, it seems not too painful for a windows build?
> >
> > Yes. I agree. It was amazingly painless!
>
> Didn't one of us forget a ;-) there?
>
;-) Not at all. It built! With only a couple of very minor workarounds for
probable oddities in the the cygwin configuration. You should try building
packages like JMax. Now, that's painful. lol.