The NSIS installer is only on Windows.

Regards,
Mike

-----Original Message-----
>From: peiman 
>Sent: Aug 12, 2008 11:24 PM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd]  building csound, osx
>
>
>Hello,
>
>I'm trying to build csound from source on osx. It seems to work fine so far,
>except I'm not sure how to install the build! When I write ./install.py the
>installer complains that csound is already installed on the system, which is
>true. Is there anyway to uninstall previously installed csound before
>continuing? Or can the install.py script be changed to overwrite the old
>files, or perhaps there is a different way to install the files on osx?
>
>Also how is it possible to build a double precision version of csound? At
>what stage do I need to define that?
>
>Yet another question (!), the manual says:
>
>"Set the environment variable OPCODEDIR to the directory where plugin
>libraries are installed; in the case of a double precision build,
>OPCODEDIR64 should be set instead. The NSIS installer performs this step."
>
>Could someone please explain what this means?
>
>Thanks in advance
>
>Best
>Peiman
>-- 
>View this message in context: http://www.nabble.com/building-csound%2C-osx-tp18956393p18956393.html
>Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the clarification. But how do I set the variable OPCODEDIR64 on
osx? Or is this done automatically by the installer?

Best
Peiman


Michael Gogins wrote:
> 
> The NSIS installer is only on Windows.
> 
> Regards,
> Mike
> 
> -----Original Message-----
>>From: peiman 
>>Sent: Aug 12, 2008 11:24 PM
>>To: csound@lists.bath.ac.uk
>>Subject: [Csnd]  building csound, osx
>>
>>
>>Hello,
>>
>>I'm trying to build csound from source on osx. It seems to work fine so
far,
>>except I'm not sure how to install the build! When I write ./install.py
the
>>installer complains that csound is already installed on the system, which
is
>>true. Is there anyway to uninstall previously installed csound before
>>continuing? Or can the install.py script be changed to overwrite the old
>>files, or perhaps there is a different way to install the files on osx?
>>
>>Also how is it possible to build a double precision version of csound? At
>>what stage do I need to define that?
>>
>>Yet another question (!), the manual says:
>>
>>"Set the environment variable OPCODEDIR to the directory where plugin
>>libraries are installed; in the case of a double precision build,
>>OPCODEDIR64 should be set instead. The NSIS installer performs this step."
>>
>>Could someone please explain what this means?
>>
>>Thanks in advance
>>
>>Best
>>Peiman
>>-- 
>>View this message in context:
http://www.nabble.com/building-csound%2C-osx-tp18956393p18956393.html
>>Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>>
>>Send bugs reports to this list.
>>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
csound"
> 
> 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/building-csound%2C-osx-tp18956393p18960893.html
Sent from the Csound - General mailing list archive at Nabble.com.

export OPCODEDIR=/my/opcode/dir

Well there are several things I need to check to make a 64-bit OSX
version work. One is to set the default location of the plugins directory,
which is set to the framework in the 32bit one (when built with
buildRelease=1)

The next one is to make sure the framework is correctly constructed
by SConstruct, that everything is placed correctly. I am still wondering
whether it should be called CsoundLib64 or just CsoundLib (I am inclined
to the next, so that a 64 build replaces a 32 build completely and there
are no name confusions).

Then it's checking that everything gets copied to the right places. My
scripts do that for 32bit, but it needs figuring out what to do for 64bit.

Anyway, these are a few pitfalls. Did you build with dynamicCsoundLibrary=1 ?
I need to check whether the SConstruct directives for 64bit on OSX
are correct, they were written by Istvan in the dark (he didn't have
a way of testing)  and were never maintained.

Can we move this discussion to the devel list?

Regards

Victor
At 11:58 13/08/2008, you wrote:

>Thanks for the clarification. But how do I set the variable OPCODEDIR64 on
>osx? Or is this done automatically by the installer?
>
>Best
>Peiman
>
>
>Michael Gogins wrote:
> >
> > The NSIS installer is only on Windows.
> >
> > Regards,
> > Mike
> >
> > -----Original Message-----
> >>From: peiman 
> >>Sent: Aug 12, 2008 11:24 PM
> >>To: csound@lists.bath.ac.uk
> >>Subject: [Csnd]  building csound, osx
> >>
> >>
> >>Hello,
> >>
> >>I'm trying to build csound from source on osx. It seems to work fine so
>far,
> >>except I'm not sure how to install the build! When I write ./install.py
>the
> >>installer complains that csound is already installed on the system, which
>is
> >>true. Is there anyway to uninstall previously installed csound before
> >>continuing? Or can the install.py script be changed to overwrite the old
> >>files, or perhaps there is a different way to install the files on osx?
> >>
> >>Also how is it possible to build a double precision version of csound? At
> >>what stage do I need to define that?
> >>
> >>Yet another question (!), the manual says:
> >>
> >>"Set the environment variable OPCODEDIR to the directory where plugin
> >>libraries are installed; in the case of a double precision build,
> >>OPCODEDIR64 should be set instead. The NSIS installer performs this step."
> >>
> >>Could someone please explain what this means?
> >>
> >>Thanks in advance
> >>
> >>Best
> >>Peiman
> >>--
> >>View this message in context:
>http://www.nabble.com/building-csound%2C-osx-tp18956393p18956393.html
> >>Sent from the Csound - General mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>Send bugs reports to this list.
> >>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>csound"
> >
> >
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> > csound"
> >
> >
>
>--
>View this message in context: 
>http://www.nabble.com/building-csound%2C-osx-tp18956393p18960893.html
>Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>"unsubscribe csound"

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

Hello Peiman,

The environment variables in OS X (at least in 10.3.9) 'live' in a file 
called environment.plist. This file should be in 
/users/username/.MacOSX. I read somewhere that, if this file doesn't 
already exist, you should create it. I made the file, and it worked. 
This is what my file looks like:





OPCODEDIR64
/Volumes/ExternalHD/devel/csound5/lib64
INCDIR
/Users/ernesto/Csound
SFDIR
/Users/ernesto/Desktop/CsoundOut



I hope this helps.

Greetings,

E.

peiman wrote:
> Thanks for the clarification. But how do I set the variable OPCODEDIR64 on
> osx? Or is this done automatically by the installer?
>
> Best
> Peiman
>
>
>   

I would strongly suggest calling the doubles version CsoundLib64.framework.
The doubles build does _not_ replace a float build.  A program that links to
one at compile time will obviously crash if it links to the other at run
time.  By giving them separate names, all hosts will use the correct version
only or fail to launch if it is not found.  In the latter case, the crash
log or command line should give a clear error message about the missing
framework.  If the frameworks have the same name, the crash log will give no
useful indication of what the problem is.  Finally, using separate names
will allow both doubles and floats versions to coexist peacefully in the
same system.  This may be necessary if the user wants to simultaneously
install two hosts that require different float sizes.  (And it may even
allow a single host to offer the option of switching between floats and
doubles!)

Anthony 

Victor Lazzarini wrote on 8/13/08 7:38 AM:

> The next one is to make sure the framework is correctly constructed
> by SConstruct, that everything is placed correctly. I am still wondering
> whether it should be called CsoundLib64 or just CsoundLib (I am inclined
> to the next, so that a 64 build replaces a 32 build completely and there
> are no name confusions).


-------------------------------------------------------------------------
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

Actually it looks like csound won't run unless there is a
CsoundLib64.Framework. But I'm getting real confused here! When building
double precision, both CsoundLib64.Framework and CsoundLib.Framework are
created. Why?

Thanks
Peiman


Anthony Kozar-2 wrote:
> 
> I would strongly suggest calling the doubles version
> CsoundLib64.framework.
> The doubles build does _not_ replace a float build.  A program that links
> to
> one at compile time will obviously crash if it links to the other at run
> time.  By giving them separate names, all hosts will use the correct
> version
> only or fail to launch if it is not found.  In the latter case, the crash
> log or command line should give a clear error message about the missing
> framework.  If the frameworks have the same name, the crash log will give
> no
> useful indication of what the problem is.  Finally, using separate names
> will allow both doubles and floats versions to coexist peacefully in the
> same system.  This may be necessary if the user wants to simultaneously
> install two hosts that require different float sizes.  (And it may even
> allow a single host to offer the option of switching between floats and
> doubles!)
> 
> Anthony 
> 
> Victor Lazzarini wrote on 8/13/08 7:38 AM:
> 
>> The next one is to make sure the framework is correctly constructed
>> by SConstruct, that everything is placed correctly. I am still wondering
>> whether it should be called CsoundLib64 or just CsoundLib (I am inclined
>> to the next, so that a 64 build replaces a 32 build completely and there
>> are no name confusions).
> 
> 
> -------------------------------------------------------------------------
> 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
> 
> 

-- 
View this message in context: http://www.nabble.com/Re%3A--Csnd--building-csound%2C-osx-tp18967574p18969706.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
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