This is the mail archive of the
mailing list for the Cygwin project.
Re: ITP: Guile 1.5.6
Jan Nieuwenhuizen wrote:
Thanks, I'm sure that there are plenty of people, including myself, who
won't mind testing it out for you.
Now, as for building from source, the script included in the source
package is not a valid Cygwin script. It seems to be a
Yes, it is. To avoid confusion, I'll rename those to
cross-guile-1.5.6-1.sh, for reference, and try my best at:
Would it be possible to adapt the generic
build script from the package building page?
Yes, developing under Cygwin is a pleasure, a far cry from using
command.com. It is almost to the point of being transparent from a
linux developer's perspective. As we speak, I am currently running
OpenBox on X11 in another window, in which I am looking at your package
through an rxvt terminal. Cygwin isn't just a dll anymore, it's
becoming a full-fledged OS now. Heck, it even has a /proc and /dev!
The point is that I prefer to think I am developing inside Cygwin, not
Windows... There is a difference.
You're actually *developing* on Windows? Amazing.
Ok, but this is *NOT* what the readme says. It tells people to run the
script. Most people who are going to rebuild the package will be doing
so natively. So if you aren't going to include a build script for
native building, then please outline the options that should be sent to
configure in one command line. This way, we hope that people won't
flood the mailing list with "why won't this compile" or "the script
isn't working for package <foo>" type messages.
Anyway, it should
all be rather staightforwardly
make all install
apart from the sub-package splitting, which already is a shell script.