Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:3611] SourceForge compile farm

Date2003-12-03 01:29
Fromsteven
Subject[CSOUND-DEV:3611] SourceForge compile farm
Hi all,

I was wondering if anyone has tried using the sourceforge compile farm:

http://sourceforge.net/docman/display_doc.php?docid=762&group_id=1

It looks like a good way to test compiles on MacOSX and Linux if don't 
have access to those platforms (or if you don't want to have to reboot 
on a dual-boot system). 

steven

Date2003-12-03 11:55
Fromramsdell@mitre.org (John D. Ramsdell)
Subject[CSOUND-DEV:3617] Re: SourceForge compile farm
steven  writes:

> I was wondering if anyone has tried using the sourceforge compile
> farm:

I guess I should try this for MacOSX tests.  I'll put this on my list
of things to do.  Thanks.

John

Date2003-12-25 02:39
Fromramsdell@mitre.org (John D. Ramsdell)
Subject[CSOUND-DEV:3821] Csound compiles on MacOS X SourceForge compile farm
steven  writes:

> I was wondering if anyone has tried using the sourceforge compile
> farm:

Steven,

Thank you for prodding me to use the SourceForge compile farm.  I
connected to the PPC - G4 MacOS X 10.2 SERVER Edition machine, and
extracted the latest version of the csound module, but like you, was
unable to make autoreconf produce a working GNU build system.  For me,
it failed to produce a usable version of the libtool script.

I uploaded csound-4.23.0.tar.gz from the wxcsound package version
1.0.2 release.  I found two minor edits allowed the system to build
and install on MacOS X.  The file csound/dpwelib.h and csound/pvoc.c
had to be changed so that they do not attempt to load malloc.h when
compiling on Darwin.  The key seems to be running autoreconf on the
latest version of Cygwin when producing a distribution.  

I've updated those two files in the csound module and updated the
version number in configure.ac to 4.23.1, but have not made a release.
Shall I release an MacOS X friendly version of Csound as version
4.23.1 of the csound package?

John