Csound Csound-dev Csound-tekno Search About

[Cs-dev] Updated info on building Csound on OSX Lion

Date2012-02-10 14:23
FromSteven Yi
Subject[Cs-dev] Updated info on building Csound on OSX Lion
Hi All,

Just FYI, I've updated the wiki page on building Csound on OSX Lion:

https://sourceforge.net/apps/mediawiki/csound/index.php?title=Building_Csound_on_OSX_Lion

Mainly I added a note about pkg-config path and instructions for
building libFLAC, libogg, and libvorbis (for compiling with
libsndfile).

Thanks!
steven

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-02-11 04:55
FromIain Duncan
SubjectRe: [Cs-dev] Updated info on building Csound on OSX Lion
AttachmentsNone  None  

On Fri, Feb 10, 2012 at 6:23 AM, Steven Yi <stevenyi@gmail.com> wrote:
Hi All,

Just FYI, I've updated the wiki page on building Csound on OSX Lion:

https://sourceforge.net/apps/mediawiki/csound/index.php?title=Building_Csound_on_OSX_Lion

Mainly I added a note about pkg-config path and instructions for
building libFLAC, libogg, and libvorbis (for compiling with
libsndfile).


Hey Steven, I notice there's no mention on there of using MacPorts to install the dependent libraries. I was able to build on Os X with only the Csound package itself being built from source and it was much easier. I installed the following using MacPorts:

libsndfile, liblo, scons, cmake, portaudio, portmidi

The only thing that didn't work from macports for me was Jack, and that worked fine downloading the jack os x dmg file.

Is there a reason the wiki page doesn't mention macports? Would it be helpful to include how I did that?

Iain
 
 
Thanks!
steven

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


Date2012-02-11 15:37
FromSteven Yi
SubjectRe: [Cs-dev] Updated info on building Csound on OSX Lion
HI Iain,

I used to use Macports but stopped at Victor's advice.  I think it's
fine if you're building Csound just for your own use, but if you're
going to distribute csound, it makes it more difficult to track down
all of the dependencies as it seems to always pull in something extra.
 I'd prefer homebrew over macports, but I'm comfortable with just
compiling the libs themselves and have better control over the build,
where I need to make sure everything is i386/x86_64.

If you decide to add any information to the Wiki, I'd just add a note
that it's good for personal use but may not be good if you plan to
distribute the Csound you built.

Thanks!
steven

On Sat, Feb 11, 2012 at 4:55 AM, Iain Duncan  wrote:
>
> On Fri, Feb 10, 2012 at 6:23 AM, Steven Yi  wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the wiki page on building Csound on OSX Lion:
>>
>>
>> https://sourceforge.net/apps/mediawiki/csound/index.php?title=Building_Csound_on_OSX_Lion
>>
>> Mainly I added a note about pkg-config path and instructions for
>> building libFLAC, libogg, and libvorbis (for compiling with
>> libsndfile).
>>
>
> Hey Steven, I notice there's no mention on there of using MacPorts to
> install the dependent libraries. I was able to build on Os X with only the
> Csound package itself being built from source and it was much easier. I
> installed the following using MacPorts:
>
> libsndfile, liblo, scons, cmake, portaudio, portmidi
>
> The only thing that didn't work from macports for me was Jack, and that
> worked fine downloading the jack os x dmg file.
>
> Is there a reason the wiki page doesn't mention macports? Would it be
> helpful to include how I did that?
>
> Iain
>
>
>>
>> Thanks!
>> steven
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-02-11 21:05
FromIain Duncan
SubjectRe: [Cs-dev] Updated info on building Csound on OSX Lion
AttachmentsNone  None  
I used to use Macports but stopped at Victor's advice.  I think it's
fine if you're building Csound just for your own use, but if you're
going to distribute csound, it makes it more difficult to track down
all of the dependencies as it seems to always pull in something extra.
 I'd prefer homebrew over macports, but I'm comfortable with just
compiling the libs themselves and have better control over the build,
where I need to make sure everything is i386/x86_64.

If you decide to add any information to the Wiki, I'd just add a note
that it's good for personal use but may not be good if you plan to
distribute the Csound you built.

Ah, thanks for the explanation. That makes sense.

iain