Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> On Tuesday 11 May 2004 02:42 pm, dmclean62@... wrote:
> > Looking around, I discovered that the win directory contains a file
> > "compile.txt" that includes directions on compiling under cygwin. Go
> > figure.
> Sorry, I've been kinda not paying attention for a little while. I did the
> cygwin build a little while ago and all the patches that made it work. ;)
> You *must* use the 1.2 branch. The build system has been going through some
> fairly radical changes in CVS HEAD, I understand, and I had decided to wait
> until it stabilized a bit before going back in with Cygwin there. The 1.2
> tarball release *should* build (I did test it right before it was released).
Well, the reality of the situation doesn't seem to be quite that dire. I used the CVS HEAD and I did get it to compile (eventually, with a little work).
> > It looks like I got most of the way before it died, but there were a couple
> > of specific problems that I encountered.
> > portaudio and portmixer - I had to build these by hand, the make files
> > couldn't quite figure them out, but once I made them, make progressed.
> This shouldn't have happened at all. Both PA and PM have makefiles that I
> tuned for Cygwin. If you're using the 1.2 branch, I'd like to see the
> specific errors you're having.
I think that the problem was that the configure script partly confused cygwin and some form of Unix. I think that the make file was trying to make the Unix version, but of course configure had configured the windows version. This would explain why I could make them both by hand, even though they wouldn't make automatically.