Hello, 

I just wanted to say that I have been using OS X 10.5 on my computer for a
few weeks now and last week I went ahead and compiled Csound 5.09 from
scratch because I needed the Python interface to try Chuckk's new tkinter
front end.  I was also thinking ahead to making packages for 10.5 in the
future.

Basically, I started with a nearly "clean" Leopard system -- I had installed
Victor's 5.09 PPC package but uninstalled it when I found that it would not
work for Python (unsurprisingly).  I downloaded the latest source code for
nearly all of Csound's dependencies and many optional components, built each
of them, and finally built Csound.  There were a few snags along the way but
I documented the entire experience so that it is hopefully repeatable.  I
was unable to get the new linear algebra opcodes to compile.  And I did not
try to build Jack support or DSSI opcodes.  Otherwise, I think that I did
succeed in building everything else.  Installing everything into the correct
locations was another matter as I did not see an OS X script in CVS for
this, so I hacked the install.py script as a partial solution.

Victor, you mentioned that you have more files/scripts that you use for
packaging Csound releases.  Could you share those with me please?

I'll post more details about the problems I had while building later.

Thanks.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Anthony,

this is the way I do things:

1. I ignore install.py, because I am packaging.
2. I use Apple's Package Builder, so I suppose you can try it too. It
is not that difficult. The main thing is to build a directory structure
for the locations of your installed files. This is what I have

Package CsoundLib:
./CsoundLib/Install_Resources/            ---> install scripts
                           /Package_Contents/          ---> directory 
structure from root( "/")
                                                           /Library/Frameworks/CsoundLib.framework/ 

                                                                       /Frameworks/Python.framework
                                                         /System/Library/Frameworks/Python.framework

In CsoundLib.framework you copy the whole framework. In
Python.framework you copy the Python module (if compiled
for MacPython (if you have built it) goes in /Library  else
for Apple Python in /System/Library).

Package SupportLibs:

./SupportLibs/Install_Resources/            ---> install scripts
                           /Package_Contents/          ---> directory 
structure from root( "/")
                                                          /usr/local/lib

All the dependency libraries.

Package CsoundApps

./CsoundApps/Install_Resources/            ---> install scripts
                           /Package_Contents/          ---> directory 
structure from root( "/")
                                                           /usr/local/bin
                                                           /System/Application
                                                           /Library/Audio/Plug-ins/LADSPA

Frontends

3. Then it's just running the application builder to get
the installers.

I am attaching all the scripts I use to copy things etc.

Build-Scripts: the scripts that build csound and go on the
top-level dir of sources

Packager-scripts: these are the PackageMaker (.pmproj) files
plus Install_Resources scripts for each package and one
archiver script.

All these assume package scripts and files to go in ./csound5_install
which is at the same level ./csound5 (the sources). Also the
manual sources to be in ./manual

I commented some of the shell scripts. See if you can make any
sense of them. I can try to zip up all the installation directory
structures, if need them later.

Regards

Victor



At 02:55 28/10/2008, you wrote:
>Hello,
>
>I just wanted to say that I have been using OS X 10.5 on my computer for a
>few weeks now and last week I went ahead and compiled Csound 5.09 from
>scratch because I needed the Python interface to try Chuckk's new tkinter
>front end.  I was also thinking ahead to making packages for 10.5 in the
>future.
>
>Basically, I started with a nearly "clean" Leopard system -- I had installed
>Victor's 5.09 PPC package but uninstalled it when I found that it would not
>work for Python (unsurprisingly).  I downloaded the latest source code for
>nearly all of Csound's dependencies and many optional components, built each
>of them, and finally built Csound.  There were a few snags along the way but
>I documented the entire experience so that it is hopefully repeatable.  I
>was unable to get the new linear algebra opcodes to compile.  And I did not
>try to build Jack support or DSSI opcodes.  Otherwise, I think that I did
>succeed in building everything else.  Installing everything into the correct
>locations was another matter as I did not see an OS X script in CVS for
>this, so I hacked the install.py script as a partial solution.
>
>Victor, you mentioned that you have more files/scripts that you use for
>packaging Csound releases.  Could you share those with me please?
>
>I'll post more details about the problems I had while building later.
>
>Thanks.
>
>Anthony Kozar
>mailing-lists-1001 AT anthonykozar DOT net
>http://anthonykozar.net/
>
>
>-------------------------------------------------------------------------
>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & win great prizes
>Grand prize is a trip for two to an Open Source event anywhere in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

I'm just skimming this list at the moment, so excuse if this is off:
Why not build the APIs++ to a directory inside the source directory  
and them use a separate script to move them to the appropriate place?  
That way the moving can be done by hand if necessary.
David

On 29/10/2008, at 2:14 AM, peiman khosravi wrote:

> Hi,
>
> I use a bash script to install the files in a different location  
> than usr/local/bin as I want to have both float and double build on  
> the same machine. I tried this last night with a new 64bit build of  
> the latest release and it's working fine.
>
> Best
> Peiman
>
> 2008/10/28 Anthony Kozar 
> Hello,
>
> I just wanted to say that I have been using OS X 10.5 on my computer  
> for a
> few weeks now and last week I went ahead and compiled Csound 5.09 from
> scratch because I needed the Python interface to try Chuckk's new  
> tkinter
> front end.  I was also thinking ahead to making packages for 10.5 in  
> the
> future.
>
> Basically, I started with a nearly "clean" Leopard system -- I had  
> installed
> Victor's 5.09 PPC package but uninstalled it when I found that it  
> would not
> work for Python (unsurprisingly).  I downloaded the latest source  
> code for
> nearly all of Csound's dependencies and many optional components,  
> built each
> of them, and finally built Csound.  There were a few snags along the  
> way but
> I documented the entire experience so that it is hopefully  
> repeatable.  I
> was unable to get the new linear algebra opcodes to compile.  And I  
> did not
> try to build Jack support or DSSI opcodes.  Otherwise, I think that  
> I did
> succeed in building everything else.  Installing everything into the  
> correct
> locations was another matter as I did not see an OS X script in CVS  
> for
> this, so I hacked the install.py script as a partial solution.
>
> Victor, you mentioned that you have more files/scripts that you use  
> for
> packaging Csound releases.  Could you share those with me please?
>
> I'll post more details about the problems I had while building later.
>
> Thanks.
>
> Anthony Kozar
> mailing-lists-1001 AT anthonykozar DOT net
> http://anthonykozar.net/
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

________________________________________________
David Worrall.
- Experimental Polymedia:	www.avatar.com.au
- Education for Financial Independence: www.mindthemarkets.com.au
Australian research affiliations:
- Capital Markets Cooperative Research Centre: www.cmcrc.com
- Sonic Communications Research Group:	creative.canberra.edu.au/scrg
- MARCS Auditory Laboratories: marcs.uws.edu.au




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

that's what I do...

Peiman

On 28 Oct 2008, at 19:07, DavidW wrote:

> I'm just skimming this list at the moment, so excuse if this is off:
> Why not build the APIs++ to a directory inside the source directory
> and them use a separate script to move them to the appropriate place?
> That way the moving can be done by hand if necessary.
> David
>
> On 29/10/2008, at 2:14 AM, peiman khosravi wrote:
>
>> Hi,
>>
>> I use a bash script to install the files in a different location
>> than usr/local/bin as I want to have both float and double build on
>> the same machine. I tried this last night with a new 64bit build of
>> the latest release and it's working fine.
>>
>> Best
>> Peiman
>>
>> 2008/10/28 Anthony Kozar 
>> Hello,
>>
>> I just wanted to say that I have been using OS X 10.5 on my computer
>> for a
>> few weeks now and last week I went ahead and compiled Csound 5.09  
>> from
>> scratch because I needed the Python interface to try Chuckk's new
>> tkinter
>> front end.  I was also thinking ahead to making packages for 10.5 in
>> the
>> future.
>>
>> Basically, I started with a nearly "clean" Leopard system -- I had
>> installed
>> Victor's 5.09 PPC package but uninstalled it when I found that it
>> would not
>> work for Python (unsurprisingly).  I downloaded the latest source
>> code for
>> nearly all of Csound's dependencies and many optional components,
>> built each
>> of them, and finally built Csound.  There were a few snags along the
>> way but
>> I documented the entire experience so that it is hopefully
>> repeatable.  I
>> was unable to get the new linear algebra opcodes to compile.  And I
>> did not
>> try to build Jack support or DSSI opcodes.  Otherwise, I think that
>> I did
>> succeed in building everything else.  Installing everything into the
>> correct
>> locations was another matter as I did not see an OS X script in CVS
>> for
>> this, so I hacked the install.py script as a partial solution.
>>
>> Victor, you mentioned that you have more files/scripts that you use
>> for
>> packaging Csound releases.  Could you share those with me please?
>>
>> I'll post more details about the problems I had while building later.
>>
>> Thanks.
>>
>> Anthony Kozar
>> mailing-lists-1001 AT anthonykozar DOT net
>> http://anthonykozar.net/
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ 
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ________________________________________________
> David Worrall.
> - Experimental Polymedia:	www.avatar.com.au
> - Education for Financial Independence: www.mindthemarkets.com.au
> Australian research affiliations:
> - Capital Markets Cooperative Research Centre: www.cmcrc.com
> - Sonic Communications Research Group:	creative.canberra.edu.au/scrg
> - MARCS Auditory Laboratories: marcs.uws.edu.au
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks very much, Victor, for the detailed instructions!  I will certainly
look at these just as soon as I have some time.  (Hopefully this weekend
...)

Anthony

Victor Lazzarini wrote on 10/28/08 9:01 AM:

> Anthony,
> 
> this is the way I do things:

[...]

> I commented some of the shell scripts. See if you can make any
> sense of them. I can try to zip up all the installation directory
> structures, if need them later.
> 
> Regards
> 
> Victor


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Anthony Kozar wrote on 10/27/08 10:55 PM:

> I'll post more details about the problems I had while building later.

(Note:  all of these issues were experienced with the Csound 5.09 source
package downloaded from Sourceforge -- maybe some have already been
corrected in the latest CVS).

First, I had some problems with SConstruct and GNU GetText.  I tried
compiling with useGettext=1 before I knew whether or not it comes with OS X
10.5.  I assumed that SConstruct would test for the correct headers and
libraries (like it does with most other dependencies) and let me know if
there was a problem.  I didn't receive an error during the configuration
phase, but instead while compiling Csound:

    H/text.h:111:21: error: libintl.h: No such file or directory

So, I think that there should be a test in SConstruct for libintl.h and
libintl.  Something like this?

getTextFound = configure.CheckLibWithHeader("intl", "libintl.h", language =
"C")

I then compiled and installed GetText and the build failed with

    Undefined symbols:
      "_libintl_dgettext", referenced from:
          _csoundLocalizeString in getstring.os
    ld: symbol(s) not found

so I had to add customLIBS.append('intl') to custom.py to fix this.  I think
that SConstruct should probably add this library to the link on OS X (is it
not explicitly needed on Linux?).

There were also errors compiling ChuaOscillator.cpp:

/Volumes/Data/Users/anthony/Developer/libraries/boost_1_36_0/boost/exception
/exception.hpp: In member function 'const char*
boost::exception::_diagnostic_information(const char*) const':
    
/Volumes/Data/Users/anthony/Developer/libraries/boost_1_36_0/boost/exception
/exception.hpp:74: error: cannot use typeid with -fno-rtti
    
/Volumes/Data/Users/anthony/Developer/libraries/boost_1_36_0/boost/exception
/exception.hpp:81: error: cannot use typeid with -fno-rtti


The problem is that SConstruct is adding the -fno-rtti flag on line 1161
(Csound 5.09-tagged version) for builds on the 'darwin' platform.
Commenting out this line allowed compilation to proceed successfully, but I
did not recompile any C++ libraries that were already built.  Is there a
reason that this flag is being set?

I also had trouble linking the counterpoint program:

    ld: library not found for -lcsnd
    collect2: ld returned 1 exit status
    scons: *** [counterpoint] Error 1

My hack of a solution was to do 'ln -s lib_csnd.dylib libcsnd.dylib' then
run SCons again.

The other problems that I had were mostly related to not having the right
paths in custom.py when I started.  PortMidi was problematic because it does
not seem to install everything that is needed to /usr/local/ and the
PortAudio folks recommend NOT installing their library for some reason but
then hide the binaries in an invisible directory.  I think I would try
installing it next time to save some trouble.

I will be posting a full account of my experience to my blog on cSounds.com
in the near future.  Finally, I tacked on a few warnings to the end of this
message that I noticed while compiling the CoreAudio and some other modules.
Looks like the CoreAudio client code may need to be rewritten in the future.
I don't know if the no-strict-aliasing warning is significant.

Thanks.  (I am not using CVS on the OS X machine yet, but I can commit
necessary changes once I get to that point if needed).

Anthony


Some Warnings in the CoreAudio module:
    
    InOut/rtcoreaudio.c: In function 'coreaudio_open':
    InOut/rtcoreaudio.c:393: warning: 'AudioDeviceAddIOProc' is deprecated
(declared at 
/System/Library/Frameworks/CoreAudio.framework/Headers/AudioHardware.h:2067)
    InOut/rtcoreaudio.c: In function 'rtclose_':
    InOut/rtcoreaudio.c:542: warning: 'AudioDeviceRemoveIOProc' is
deprecated (declared at
/System/Library/Frameworks/CoreAudio.framework/Headers/AudioHardware.h:2081)


A Warning in the sfont module (also Loris python module, CsoundAC, and API
wrappers):
    cc1: warning: -ftree-vectorize enables strict aliasing.
-fno-strict-aliasing is ignored when Auto Vectorization is used.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net