Csound Csound-dev Csound-tekno Search About

help building fresh with homebrew *over* existing cabbage install

Date2015-11-17 03:08
FromKevin Welsh
Subjecthelp building fresh with homebrew *over* existing cabbage install
My goal is to use homebrew to install a fresh build of csound over the
one packaged with the most recent cabbage release, so that I can use
the new csound features from within cabbage.

When I do:
brew install -HEAD csound

it appears to fetch and build 6.05, and I forced an overwrite when it
linked the first time.  But when I run csound form a console it still
reports:
Csound version 6.04 (double samples) Feb 26 2015

I tried uninstalling via homebrew, confirming my csound command was
gone, and rebuilding via the homebrew command, this time it didn't
require forcing the overwrite, but I still run csound and it reports:
Csound version 6.04 (double samples) Feb 26 2015

What am I doing wrong or forgetting to do to upgrade this?

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-11-17 11:29
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
For what it's worth, I just updated the OSX installer so that it ships with the latest version of Csound, i.e., 6.06.

On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com> wrote:
My goal is to use homebrew to install a fresh build of csound over the
one packaged with the most recent cabbage release, so that I can use
the new csound features from within cabbage.

When I do:
brew install -HEAD csound

it appears to fetch and build 6.05, and I forced an overwrite when it
linked the first time.  But when I run csound form a console it still
reports:
Csound version 6.04 (double samples) Feb 26 2015

I tried uninstalling via homebrew, confirming my csound command was
gone, and rebuilding via the homebrew command, this time it didn't
require forcing the overwrite, but I still run csound and it reports:
Csound version 6.04 (double samples) Feb 26 2015

What am I doing wrong or forgetting to do to upgrade this?

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 12:38
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Well, then now I'm really confused.

I uninstalled the homebrew version, confirmed that "csound" command no
longer worked at the command line.
I installed a fresh download from http://www.cabbageaudio.com/download/

Cabbage appears to work fine, but in the output window it reports 6.04
still... and from a command line it still says "command not found", as
if I have no csound at all.

On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh  wrote:
> For what it's worth, I just updated the OSX installer so that it ships with
> the latest version of Csound, i.e., 6.06.
>
> On 17 November 2015 at 03:08, Kevin Welsh  wrote:
>>
>> My goal is to use homebrew to install a fresh build of csound over the
>> one packaged with the most recent cabbage release, so that I can use
>> the new csound features from within cabbage.
>>
>> When I do:
>> brew install -HEAD csound
>>
>> it appears to fetch and build 6.05, and I forced an overwrite when it
>> linked the first time.  But when I run csound form a console it still
>> reports:
>> Csound version 6.04 (double samples) Feb 26 2015
>>
>> I tried uninstalling via homebrew, confirming my csound command was
>> gone, and rebuilding via the homebrew command, this time it didn't
>> require forcing the overwrite, but I still run csound and it reports:
>> Csound version 6.04 (double samples) Feb 26 2015
>>
>> What am I doing wrong or forgetting to do to upgrade this?
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-11-17 13:55
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Cabbage links to the Csound library whereas running csound from the command line calls the csound application, which in turns calls the Csound library. Cabbage only needs to underlying libraries. 

On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com> wrote:
Well, then now I'm really confused.

I uninstalled the homebrew version, confirmed that "csound" command no
longer worked at the command line.
I installed a fresh download from http://www.cabbageaudio.com/download/

Cabbage appears to work fine, but in the output window it reports 6.04
still... and from a command line it still says "command not found", as
if I have no csound at all.

On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> For what it's worth, I just updated the OSX installer so that it ships with
> the latest version of Csound, i.e., 6.06.
>
> On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com> wrote:
>>
>> My goal is to use homebrew to install a fresh build of csound over the
>> one packaged with the most recent cabbage release, so that I can use
>> the new csound features from within cabbage.
>>
>> When I do:
>> brew install -HEAD csound
>>
>> it appears to fetch and build 6.05, and I forced an overwrite when it
>> linked the first time.  But when I run csound form a console it still
>> reports:
>> Csound version 6.04 (double samples) Feb 26 2015
>>
>> I tried uninstalling via homebrew, confirming my csound command was
>> gone, and rebuilding via the homebrew command, this time it didn't
>> require forcing the overwrite, but I still run csound and it reports:
>> Csound version 6.04 (double samples) Feb 26 2015
>>
>> What am I doing wrong or forgetting to do to upgrade this?
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 14:29
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
So I'm guessing this means for some reason my csound library isn't
getting upgraded?

On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh  wrote:
> Cabbage links to the Csound library whereas running csound from the command
> line calls the csound application, which in turns calls the Csound library.
> Cabbage only needs to underlying libraries.
>
> On 17 November 2015 at 12:38, Kevin Welsh  wrote:
>>
>> Well, then now I'm really confused.
>>
>> I uninstalled the homebrew version, confirmed that "csound" command no
>> longer worked at the command line.
>> I installed a fresh download from http://www.cabbageaudio.com/download/
>>
>> Cabbage appears to work fine, but in the output window it reports 6.04
>> still... and from a command line it still says "command not found", as
>> if I have no csound at all.
>>
>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh  wrote:
>> > For what it's worth, I just updated the OSX installer so that it ships
>> > with
>> > the latest version of Csound, i.e., 6.06.
>> >
>> > On 17 November 2015 at 03:08, Kevin Welsh  wrote:
>> >>
>> >> My goal is to use homebrew to install a fresh build of csound over the
>> >> one packaged with the most recent cabbage release, so that I can use
>> >> the new csound features from within cabbage.
>> >>
>> >> When I do:
>> >> brew install -HEAD csound
>> >>
>> >> it appears to fetch and build 6.05, and I forced an overwrite when it
>> >> linked the first time.  But when I run csound form a console it still
>> >> reports:
>> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>
>> >> I tried uninstalling via homebrew, confirming my csound command was
>> >> gone, and rebuilding via the homebrew command, this time it didn't
>> >> require forcing the overwrite, but I still run csound and it reports:
>> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>
>> >> What am I doing wrong or forgetting to do to upgrade this?
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-11-17 14:44
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I'm not sure what's going on because I'm pretty sure the last version of Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is coming from? I have no idea how homebrew works, is it fetching the wrong package? I've only ever built Csound on OSX using cmake and the terminal.

On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com> wrote:
So I'm guessing this means for some reason my csound library isn't
getting upgraded?

On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> Cabbage links to the Csound library whereas running csound from the command
> line calls the csound application, which in turns calls the Csound library.
> Cabbage only needs to underlying libraries.
>
> On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com> wrote:
>>
>> Well, then now I'm really confused.
>>
>> I uninstalled the homebrew version, confirmed that "csound" command no
>> longer worked at the command line.
>> I installed a fresh download from http://www.cabbageaudio.com/download/
>>
>> Cabbage appears to work fine, but in the output window it reports 6.04
>> still... and from a command line it still says "command not found", as
>> if I have no csound at all.
>>
>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> > For what it's worth, I just updated the OSX installer so that it ships
>> > with
>> > the latest version of Csound, i.e., 6.06.
>> >
>> > On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >>
>> >> My goal is to use homebrew to install a fresh build of csound over the
>> >> one packaged with the most recent cabbage release, so that I can use
>> >> the new csound features from within cabbage.
>> >>
>> >> When I do:
>> >> brew install -HEAD csound
>> >>
>> >> it appears to fetch and build 6.05, and I forced an overwrite when it
>> >> linked the first time.  But when I run csound form a console it still
>> >> reports:
>> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>
>> >> I tried uninstalling via homebrew, confirming my csound command was
>> >> gone, and rebuilding via the homebrew command, this time it didn't
>> >> require forcing the overwrite, but I still run csound and it reports:
>> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>
>> >> What am I doing wrong or forgetting to do to upgrade this?
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 14:49
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
But I uninstalled the homebrew version, and confirmed that the console
version of csound was gone too... I was trying to rule that out as the
problem, just running the newest cabbage release and the csound it
comes with.

My thought is homebrew somehow messed up a file permission or config
for loading the library that has left it running a stale version...


On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
> I'm not sure what's going on because I'm pretty sure the last version of
> Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is
> coming from? I have no idea how homebrew works, is it fetching the wrong
> package? I've only ever built Csound on OSX using cmake and the terminal.
>
> On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>
>> So I'm guessing this means for some reason my csound library isn't
>> getting upgraded?
>>
>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh  wrote:
>> > Cabbage links to the Csound library whereas running csound from the
>> > command
>> > line calls the csound application, which in turns calls the Csound
>> > library.
>> > Cabbage only needs to underlying libraries.
>> >
>> > On 17 November 2015 at 12:38, Kevin Welsh  wrote:
>> >>
>> >> Well, then now I'm really confused.
>> >>
>> >> I uninstalled the homebrew version, confirmed that "csound" command no
>> >> longer worked at the command line.
>> >> I installed a fresh download from http://www.cabbageaudio.com/download/
>> >>
>> >> Cabbage appears to work fine, but in the output window it reports 6.04
>> >> still... and from a command line it still says "command not found", as
>> >> if I have no csound at all.
>> >>
>> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh  wrote:
>> >> > For what it's worth, I just updated the OSX installer so that it
>> >> > ships
>> >> > with
>> >> > the latest version of Csound, i.e., 6.06.
>> >> >
>> >> > On 17 November 2015 at 03:08, Kevin Welsh  wrote:
>> >> >>
>> >> >> My goal is to use homebrew to install a fresh build of csound over
>> >> >> the
>> >> >> one packaged with the most recent cabbage release, so that I can use
>> >> >> the new csound features from within cabbage.
>> >> >>
>> >> >> When I do:
>> >> >> brew install -HEAD csound
>> >> >>
>> >> >> it appears to fetch and build 6.05, and I forced an overwrite when
>> >> >> it
>> >> >> linked the first time.  But when I run csound form a console it
>> >> >> still
>> >> >> reports:
>> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >>
>> >> >> I tried uninstalling via homebrew, confirming my csound command was
>> >> >> gone, and rebuilding via the homebrew command, this time it didn't
>> >> >> require forcing the overwrite, but I still run csound and it
>> >> >> reports:
>> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >>
>> >> >> What am I doing wrong or forgetting to do to upgrade this?
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-11-17 14:59
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install

Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks folder. If so, try moving or deleting that. The current homebrew build of Csound has problems. I have not found time to look into it and won't now until I get back home in December.  I recommend not using it at this time until I or someone else can look into it.


On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com> wrote:
But I uninstalled the homebrew version, and confirmed that the console
version of csound was gone too... I was trying to rule that out as the
problem, just running the newest cabbage release and the csound it
comes with.

My thought is homebrew somehow messed up a file permission or config
for loading the library that has left it running a stale version...


On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> I'm not sure what's going on because I'm pretty sure the last version of
> Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is
> coming from? I have no idea how homebrew works, is it fetching the wrong
> package? I've only ever built Csound on OSX using cmake and the terminal.
>
> On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com> wrote:
>>
>> So I'm guessing this means for some reason my csound library isn't
>> getting upgraded?
>>
>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> > Cabbage links to the Csound library whereas running csound from the
>> > command
>> > line calls the csound application, which in turns calls the Csound
>> > library.
>> > Cabbage only needs to underlying libraries.
>> >
>> > On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >>
>> >> Well, then now I'm really confused.
>> >>
>> >> I uninstalled the homebrew version, confirmed that "csound" command no
>> >> longer worked at the command line.
>> >> I installed a fresh download from http://www.cabbageaudio.com/download/
>> >>
>> >> Cabbage appears to work fine, but in the output window it reports 6.04
>> >> still... and from a command line it still says "command not found", as
>> >> if I have no csound at all.
>> >>
>> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> >> > For what it's worth, I just updated the OSX installer so that it
>> >> > ships
>> >> > with
>> >> > the latest version of Csound, i.e., 6.06.
>> >> >
>> >> > On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >> >>
>> >> >> My goal is to use homebrew to install a fresh build of csound over
>> >> >> the
>> >> >> one packaged with the most recent cabbage release, so that I can use
>> >> >> the new csound features from within cabbage.
>> >> >>
>> >> >> When I do:
>> >> >> brew install -HEAD csound
>> >> >>
>> >> >> it appears to fetch and build 6.05, and I forced an overwrite when
>> >> >> it
>> >> >> linked the first time.  But when I run csound form a console it
>> >> >> still
>> >> >> reports:
>> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >>
>> >> >> I tried uninstalling via homebrew, confirming my csound command was
>> >> >> gone, and rebuilding via the homebrew command, this time it didn't
>> >> >> require forcing the overwrite, but I still run csound and it
>> >> >> reports:
>> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >>
>> >> >> What am I doing wrong or forgetting to do to upgrade this?
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 15:14
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
That was it!  Removing that framework directory suddenly makes cabbage
report 6.06.

On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
> Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
> folder. If so, try moving or deleting that. The current homebrew build of
> Csound has problems. I have not found time to look into it and won't now
> until I get back home in December.  I recommend not using it at this time
> until I or someone else can look into it.
>
>
> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>
>> But I uninstalled the homebrew version, and confirmed that the console
>> version of csound was gone too... I was trying to rule that out as the
>> problem, just running the newest cabbage release and the csound it
>> comes with.
>>
>> My thought is homebrew somehow messed up a file permission or config
>> for loading the library that has left it running a stale version...
>>
>>
>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>> > I'm not sure what's going on because I'm pretty sure the last version of
>> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is
>> > coming from? I have no idea how homebrew works, is it fetching the wrong
>> > package? I've only ever built Csound on OSX using cmake and the
>> > terminal.
>> >
>> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>> >>
>> >> So I'm guessing this means for some reason my csound library isn't
>> >> getting upgraded?
>> >>
>> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh  wrote:
>> >> > Cabbage links to the Csound library whereas running csound from the
>> >> > command
>> >> > line calls the csound application, which in turns calls the Csound
>> >> > library.
>> >> > Cabbage only needs to underlying libraries.
>> >> >
>> >> > On 17 November 2015 at 12:38, Kevin Welsh  wrote:
>> >> >>
>> >> >> Well, then now I'm really confused.
>> >> >>
>> >> >> I uninstalled the homebrew version, confirmed that "csound" command
>> >> >> no
>> >> >> longer worked at the command line.
>> >> >> I installed a fresh download from
>> >> >> http://www.cabbageaudio.com/download/
>> >> >>
>> >> >> Cabbage appears to work fine, but in the output window it reports
>> >> >> 6.04
>> >> >> still... and from a command line it still says "command not found",
>> >> >> as
>> >> >> if I have no csound at all.
>> >> >>
>> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>> >> >> wrote:
>> >> >> > For what it's worth, I just updated the OSX installer so that it
>> >> >> > ships
>> >> >> > with
>> >> >> > the latest version of Csound, i.e., 6.06.
>> >> >> >
>> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> My goal is to use homebrew to install a fresh build of csound
>> >> >> >> over
>> >> >> >> the
>> >> >> >> one packaged with the most recent cabbage release, so that I can
>> >> >> >> use
>> >> >> >> the new csound features from within cabbage.
>> >> >> >>
>> >> >> >> When I do:
>> >> >> >> brew install -HEAD csound
>> >> >> >>
>> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>> >> >> >> when
>> >> >> >> it
>> >> >> >> linked the first time.  But when I run csound form a console it
>> >> >> >> still
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> I tried uninstalling via homebrew, confirming my csound command
>> >> >> >> was
>> >> >> >> gone, and rebuilding via the homebrew command, this time it
>> >> >> >> didn't
>> >> >> >> require forcing the overwrite, but I still run csound and it
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>> >> >> >>
>> >> >> >> Csound mailing list
>> >> >> >> Csound@listserv.heanet.ie
>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> >> Send bugs reports to
>> >> >> >>         https://github.com/csound/csound/issues
>> >> >> >> Discussions of bugs and features can be posted here
>> >> >> >
>> >> >> >
>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >> >> > to
>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> >> > features
>> >> >> > can
>> >> >> > be posted here
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-11-17 15:41
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I guess OSX checks the user Library folder before the system one.

On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com> wrote:
That was it!  Removing that framework directory suddenly makes cabbage
report 6.06.

On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi <stevenyi@gmail.com> wrote:
> Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
> folder. If so, try moving or deleting that. The current homebrew build of
> Csound has problems. I have not found time to look into it and won't now
> until I get back home in December.  I recommend not using it at this time
> until I or someone else can look into it.
>
>
> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com> wrote:
>>
>> But I uninstalled the homebrew version, and confirmed that the console
>> version of csound was gone too... I was trying to rule that out as the
>> problem, just running the newest cabbage release and the csound it
>> comes with.
>>
>> My thought is homebrew somehow messed up a file permission or config
>> for loading the library that has left it running a stale version...
>>
>>
>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> > I'm not sure what's going on because I'm pretty sure the last version of
>> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is
>> > coming from? I have no idea how homebrew works, is it fetching the wrong
>> > package? I've only ever built Csound on OSX using cmake and the
>> > terminal.
>> >
>> > On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >>
>> >> So I'm guessing this means for some reason my csound library isn't
>> >> getting upgraded?
>> >>
>> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> >> > Cabbage links to the Csound library whereas running csound from the
>> >> > command
>> >> > line calls the csound application, which in turns calls the Csound
>> >> > library.
>> >> > Cabbage only needs to underlying libraries.
>> >> >
>> >> > On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >> >>
>> >> >> Well, then now I'm really confused.
>> >> >>
>> >> >> I uninstalled the homebrew version, confirmed that "csound" command
>> >> >> no
>> >> >> longer worked at the command line.
>> >> >> I installed a fresh download from
>> >> >> http://www.cabbageaudio.com/download/
>> >> >>
>> >> >> Cabbage appears to work fine, but in the output window it reports
>> >> >> 6.04
>> >> >> still... and from a command line it still says "command not found",
>> >> >> as
>> >> >> if I have no csound at all.
>> >> >>
>> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie>
>> >> >> wrote:
>> >> >> > For what it's worth, I just updated the OSX installer so that it
>> >> >> > ships
>> >> >> > with
>> >> >> > the latest version of Csound, i.e., 6.06.
>> >> >> >
>> >> >> > On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> My goal is to use homebrew to install a fresh build of csound
>> >> >> >> over
>> >> >> >> the
>> >> >> >> one packaged with the most recent cabbage release, so that I can
>> >> >> >> use
>> >> >> >> the new csound features from within cabbage.
>> >> >> >>
>> >> >> >> When I do:
>> >> >> >> brew install -HEAD csound
>> >> >> >>
>> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>> >> >> >> when
>> >> >> >> it
>> >> >> >> linked the first time.  But when I run csound form a console it
>> >> >> >> still
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> I tried uninstalling via homebrew, confirming my csound command
>> >> >> >> was
>> >> >> >> gone, and rebuilding via the homebrew command, this time it
>> >> >> >> didn't
>> >> >> >> require forcing the overwrite, but I still run csound and it
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>> >> >> >>
>> >> >> >> Csound mailing list
>> >> >> >> Csound@listserv.heanet.ie
>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> >> Send bugs reports to
>> >> >> >>         https://github.com/csound/csound/issues
>> >> >> >> Discussions of bugs and features can be posted here
>> >> >> >
>> >> >> >
>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >> >> > to
>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> >> > features
>> >> >> > can
>> >> >> > be posted here
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 15:42
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
That doesn't seem write though. Perhaps there were some environment variables set up when trying homebrew.

On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie> wrote:
I guess OSX checks the user Library folder before the system one.

On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com> wrote:
That was it!  Removing that framework directory suddenly makes cabbage
report 6.06.

On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi <stevenyi@gmail.com> wrote:
> Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
> folder. If so, try moving or deleting that. The current homebrew build of
> Csound has problems. I have not found time to look into it and won't now
> until I get back home in December.  I recommend not using it at this time
> until I or someone else can look into it.
>
>
> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com> wrote:
>>
>> But I uninstalled the homebrew version, and confirmed that the console
>> version of csound was gone too... I was trying to rule that out as the
>> problem, just running the newest cabbage release and the csound it
>> comes with.
>>
>> My thought is homebrew somehow messed up a file permission or config
>> for loading the library that has left it running a stale version...
>>
>>
>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> > I'm not sure what's going on because I'm pretty sure the last version of
>> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04 is
>> > coming from? I have no idea how homebrew works, is it fetching the wrong
>> > package? I've only ever built Csound on OSX using cmake and the
>> > terminal.
>> >
>> > On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >>
>> >> So I'm guessing this means for some reason my csound library isn't
>> >> getting upgraded?
>> >>
>> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> >> > Cabbage links to the Csound library whereas running csound from the
>> >> > command
>> >> > line calls the csound application, which in turns calls the Csound
>> >> > library.
>> >> > Cabbage only needs to underlying libraries.
>> >> >
>> >> > On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com> wrote:
>> >> >>
>> >> >> Well, then now I'm really confused.
>> >> >>
>> >> >> I uninstalled the homebrew version, confirmed that "csound" command
>> >> >> no
>> >> >> longer worked at the command line.
>> >> >> I installed a fresh download from
>> >> >> http://www.cabbageaudio.com/download/
>> >> >>
>> >> >> Cabbage appears to work fine, but in the output window it reports
>> >> >> 6.04
>> >> >> still... and from a command line it still says "command not found",
>> >> >> as
>> >> >> if I have no csound at all.
>> >> >>
>> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie>
>> >> >> wrote:
>> >> >> > For what it's worth, I just updated the OSX installer so that it
>> >> >> > ships
>> >> >> > with
>> >> >> > the latest version of Csound, i.e., 6.06.
>> >> >> >
>> >> >> > On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> My goal is to use homebrew to install a fresh build of csound
>> >> >> >> over
>> >> >> >> the
>> >> >> >> one packaged with the most recent cabbage release, so that I can
>> >> >> >> use
>> >> >> >> the new csound features from within cabbage.
>> >> >> >>
>> >> >> >> When I do:
>> >> >> >> brew install -HEAD csound
>> >> >> >>
>> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>> >> >> >> when
>> >> >> >> it
>> >> >> >> linked the first time.  But when I run csound form a console it
>> >> >> >> still
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> I tried uninstalling via homebrew, confirming my csound command
>> >> >> >> was
>> >> >> >> gone, and rebuilding via the homebrew command, this time it
>> >> >> >> didn't
>> >> >> >> require forcing the overwrite, but I still run csound and it
>> >> >> >> reports:
>> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >> >> >>
>> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>> >> >> >>
>> >> >> >> Csound mailing list
>> >> >> >> Csound@listserv.heanet.ie
>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> >> Send bugs reports to
>> >> >> >>         https://github.com/csound/csound/issues
>> >> >> >> Discussions of bugs and features can be posted here
>> >> >> >
>> >> >> >
>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >> >> > to
>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> >> > features
>> >> >> > can
>> >> >> > be posted here
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-11-17 16:40
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install
That is correct.  If the linker path is relative, it will check local
to the executable, then the local Framework folder, then the system
Framework folder.

On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
> That doesn't seem write though. Perhaps there were some environment
> variables set up when trying homebrew.
>
> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>
>> I guess OSX checks the user Library folder before the system one.
>>
>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>
>>> That was it!  Removing that framework directory suddenly makes cabbage
>>> report 6.06.
>>>
>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>> > folder. If so, try moving or deleting that. The current homebrew build
>>> > of
>>> > Csound has problems. I have not found time to look into it and won't
>>> > now
>>> > until I get back home in December.  I recommend not using it at this
>>> > time
>>> > until I or someone else can look into it.
>>> >
>>> >
>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>> >>
>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>> >> version of csound was gone too... I was trying to rule that out as the
>>> >> problem, just running the newest cabbage release and the csound it
>>> >> comes with.
>>> >>
>>> >> My thought is homebrew somehow messed up a file permission or config
>>> >> for loading the library that has left it running a stale version...
>>> >>
>>> >>
>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>> >> > version of
>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>> >> > is
>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>> >> > wrong
>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>> >> > terminal.
>>> >> >
>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>> >> >>
>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>> >> >> getting upgraded?
>>> >> >>
>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>> >> >> wrote:
>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>> >> >> > the
>>> >> >> > command
>>> >> >> > line calls the csound application, which in turns calls the
>>> >> >> > Csound
>>> >> >> > library.
>>> >> >> > Cabbage only needs to underlying libraries.
>>> >> >> >
>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>> >> >> > wrote:
>>> >> >> >>
>>> >> >> >> Well, then now I'm really confused.
>>> >> >> >>
>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>> >> >> >> command
>>> >> >> >> no
>>> >> >> >> longer worked at the command line.
>>> >> >> >> I installed a fresh download from
>>> >> >> >> http://www.cabbageaudio.com/download/
>>> >> >> >>
>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>> >> >> >> reports
>>> >> >> >> 6.04
>>> >> >> >> still... and from a command line it still says "command not
>>> >> >> >> found",
>>> >> >> >> as
>>> >> >> >> if I have no csound at all.
>>> >> >> >>
>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>> >> >> >> wrote:
>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>> >> >> >> > it
>>> >> >> >> > ships
>>> >> >> >> > with
>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>> >> >> >> >
>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>> >> >> >> > wrote:
>>> >> >> >> >>
>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>> >> >> >> >> over
>>> >> >> >> >> the
>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>> >> >> >> >> can
>>> >> >> >> >> use
>>> >> >> >> >> the new csound features from within cabbage.
>>> >> >> >> >>
>>> >> >> >> >> When I do:
>>> >> >> >> >> brew install -HEAD csound
>>> >> >> >> >>
>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>> >> >> >> >> when
>>> >> >> >> >> it
>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>> >> >> >> >> it
>>> >> >> >> >> still
>>> >> >> >> >> reports:
>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>> >> >> >> >>
>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>> >> >> >> >> command
>>> >> >> >> >> was
>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>> >> >> >> >> didn't
>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>> >> >> >> >> reports:
>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>> >> >> >> >>
>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>> >> >> >> >>
>>> >> >> >> >> Csound mailing list
>>> >> >> >> >> Csound@listserv.heanet.ie
>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> >> >> >> Send bugs reports to
>>> >> >> >> >>         https://github.com/csound/csound/issues
>>> >> >> >> >> Discussions of bugs and features can be posted here
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>> >> >> >> > reports
>>> >> >> >> > to
>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>> >> >> >> > and
>>> >> >> >> > features
>>> >> >> >> > can
>>> >> >> >> > be posted here
>>> >> >> >>
>>> >> >> >> Csound mailing list
>>> >> >> >> Csound@listserv.heanet.ie
>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> >> >> Send bugs reports to
>>> >> >> >>         https://github.com/csound/csound/issues
>>> >> >> >> Discussions of bugs and features can be posted here
>>> >> >> >
>>> >> >> >
>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>> >> >> > to
>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>> >> >> > features
>>> >> >> > can
>>> >> >> > be posted here
>>> >> >>
>>> >> >> Csound mailing list
>>> >> >> Csound@listserv.heanet.ie
>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> >> Send bugs reports to
>>> >> >>         https://github.com/csound/csound/issues
>>> >> >> Discussions of bugs and features can be posted here
>>> >> >
>>> >> >
>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>> >> > features
>>> >> > can
>>> >> > be posted here
>>> >>
>>> >> Csound mailing list
>>> >> Csound@listserv.heanet.ie
>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> Send bugs reports to
>>> >>         https://github.com/csound/csound/issues
>>> >> Discussions of bugs and features can be posted here
>>> >
>>> > Csound mailing list Csound@listserv.heanet.ie
>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>> > features can
>>> > be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-01 05:59
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks everyone, this did get my cabbage working with the newest
csound version, however I still have no CLI version.  What would be
the best/safest way to continue using the freshest versions with
cabbage, but maintaining CLI functionality too?

On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
> That is correct.  If the linker path is relative, it will check local
> to the executable, then the local Framework folder, then the system
> Framework folder.
>
> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>> That doesn't seem write though. Perhaps there were some environment
>> variables set up when trying homebrew.
>>
>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>
>>> I guess OSX checks the user Library folder before the system one.
>>>
>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>
>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>> report 6.06.
>>>>
>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>> > of
>>>> > Csound has problems. I have not found time to look into it and won't
>>>> > now
>>>> > until I get back home in December.  I recommend not using it at this
>>>> > time
>>>> > until I or someone else can look into it.
>>>> >
>>>> >
>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>> >>
>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>> >> problem, just running the newest cabbage release and the csound it
>>>> >> comes with.
>>>> >>
>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>> >> for loading the library that has left it running a stale version...
>>>> >>
>>>> >>
>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>> >> > version of
>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>> >> > is
>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>> >> > wrong
>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>> >> > terminal.
>>>> >> >
>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>> >> >>
>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>> >> >> getting upgraded?
>>>> >> >>
>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>> >> >> wrote:
>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>> >> >> > the
>>>> >> >> > command
>>>> >> >> > line calls the csound application, which in turns calls the
>>>> >> >> > Csound
>>>> >> >> > library.
>>>> >> >> > Cabbage only needs to underlying libraries.
>>>> >> >> >
>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>> >> >> > wrote:
>>>> >> >> >>
>>>> >> >> >> Well, then now I'm really confused.
>>>> >> >> >>
>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>> >> >> >> command
>>>> >> >> >> no
>>>> >> >> >> longer worked at the command line.
>>>> >> >> >> I installed a fresh download from
>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>> >> >> >>
>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>> >> >> >> reports
>>>> >> >> >> 6.04
>>>> >> >> >> still... and from a command line it still says "command not
>>>> >> >> >> found",
>>>> >> >> >> as
>>>> >> >> >> if I have no csound at all.
>>>> >> >> >>
>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>> >> >> >> wrote:
>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>> >> >> >> > it
>>>> >> >> >> > ships
>>>> >> >> >> > with
>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>> >> >> >> >
>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>> >> >> >> > wrote:
>>>> >> >> >> >>
>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>> >> >> >> >> over
>>>> >> >> >> >> the
>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>> >> >> >> >> can
>>>> >> >> >> >> use
>>>> >> >> >> >> the new csound features from within cabbage.
>>>> >> >> >> >>
>>>> >> >> >> >> When I do:
>>>> >> >> >> >> brew install -HEAD csound
>>>> >> >> >> >>
>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>> >> >> >> >> when
>>>> >> >> >> >> it
>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>> >> >> >> >> it
>>>> >> >> >> >> still
>>>> >> >> >> >> reports:
>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>> >> >> >> >>
>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>> >> >> >> >> command
>>>> >> >> >> >> was
>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>> >> >> >> >> didn't
>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>> >> >> >> >> reports:
>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>> >> >> >> >>
>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>> >> >> >> >>
>>>> >> >> >> >> Csound mailing list
>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> >> >> >> >> Send bugs reports to
>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>> >> >> >> >
>>>> >> >> >> >
>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>> >> >> >> > reports
>>>> >> >> >> > to
>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>> >> >> >> > and
>>>> >> >> >> > features
>>>> >> >> >> > can
>>>> >> >> >> > be posted here
>>>> >> >> >>
>>>> >> >> >> Csound mailing list
>>>> >> >> >> Csound@listserv.heanet.ie
>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> >> >> >> Send bugs reports to
>>>> >> >> >>         https://github.com/csound/csound/issues
>>>> >> >> >> Discussions of bugs and features can be posted here
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>> >> >> > to
>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>> >> >> > features
>>>> >> >> > can
>>>> >> >> > be posted here
>>>> >> >>
>>>> >> >> Csound mailing list
>>>> >> >> Csound@listserv.heanet.ie
>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> >> >> Send bugs reports to
>>>> >> >>         https://github.com/csound/csound/issues
>>>> >> >> Discussions of bugs and features can be posted here
>>>> >> >
>>>> >> >
>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>> >> > features
>>>> >> > can
>>>> >> > be posted here
>>>> >>
>>>> >> Csound mailing list
>>>> >> Csound@listserv.heanet.ie
>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> >> Send bugs reports to
>>>> >>         https://github.com/csound/csound/issues
>>>> >> Discussions of bugs and features can be posted here
>>>> >
>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>> > features can
>>>> > be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>>
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features can
>> be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 02:33
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I poked around in the source tree and the only build documentation I
found is specifically for homebrew... is it still broken?  It could be
I'm looking in the wrong place, or maybe it's so easy that
instructions aren't needed assuming basic familiarity with the system
tools, but I don't know anything about building software in OSX.

Is there a doc or set of instructions I could refer to for help getting started?

On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
> Thanks everyone, this did get my cabbage working with the newest
> csound version, however I still have no CLI version.  What would be
> the best/safest way to continue using the freshest versions with
> cabbage, but maintaining CLI functionality too?
>
> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>> That is correct.  If the linker path is relative, it will check local
>> to the executable, then the local Framework folder, then the system
>> Framework folder.
>>
>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>> That doesn't seem write though. Perhaps there were some environment
>>> variables set up when trying homebrew.
>>>
>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>
>>>> I guess OSX checks the user Library folder before the system one.
>>>>
>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>
>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>> report 6.06.
>>>>>
>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>> > of
>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>> > now
>>>>> > until I get back home in December.  I recommend not using it at this
>>>>> > time
>>>>> > until I or someone else can look into it.
>>>>> >
>>>>> >
>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>> >>
>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>> >> comes with.
>>>>> >>
>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>> >> for loading the library that has left it running a stale version...
>>>>> >>
>>>>> >>
>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>> >> > version of
>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>> >> > is
>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>> >> > wrong
>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>> >> > terminal.
>>>>> >> >
>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>> >> >>
>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>> >> >> getting upgraded?
>>>>> >> >>
>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>> >> >> wrote:
>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>> >> >> > the
>>>>> >> >> > command
>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>> >> >> > Csound
>>>>> >> >> > library.
>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>> >> >> >
>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>> >> >> > wrote:
>>>>> >> >> >>
>>>>> >> >> >> Well, then now I'm really confused.
>>>>> >> >> >>
>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>> >> >> >> command
>>>>> >> >> >> no
>>>>> >> >> >> longer worked at the command line.
>>>>> >> >> >> I installed a fresh download from
>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>> >> >> >>
>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>> >> >> >> reports
>>>>> >> >> >> 6.04
>>>>> >> >> >> still... and from a command line it still says "command not
>>>>> >> >> >> found",
>>>>> >> >> >> as
>>>>> >> >> >> if I have no csound at all.
>>>>> >> >> >>
>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>> >> >> >> wrote:
>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>> >> >> >> > it
>>>>> >> >> >> > ships
>>>>> >> >> >> > with
>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>> >> >> >> >
>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>> >> >> >> > wrote:
>>>>> >> >> >> >>
>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>> >> >> >> >> over
>>>>> >> >> >> >> the
>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>> >> >> >> >> can
>>>>> >> >> >> >> use
>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>> >> >> >> >>
>>>>> >> >> >> >> When I do:
>>>>> >> >> >> >> brew install -HEAD csound
>>>>> >> >> >> >>
>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>> >> >> >> >> when
>>>>> >> >> >> >> it
>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>> >> >> >> >> it
>>>>> >> >> >> >> still
>>>>> >> >> >> >> reports:
>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>> >> >> >> >>
>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>> >> >> >> >> command
>>>>> >> >> >> >> was
>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>> >> >> >> >> didn't
>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>> >> >> >> >> reports:
>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>> >> >> >> >>
>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>> >> >> >> >>
>>>>> >> >> >> >> Csound mailing list
>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> >> >> Send bugs reports to
>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>> >> >> >> >
>>>>> >> >> >> >
>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>> >> >> >> > reports
>>>>> >> >> >> > to
>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>> >> >> >> > and
>>>>> >> >> >> > features
>>>>> >> >> >> > can
>>>>> >> >> >> > be posted here
>>>>> >> >> >>
>>>>> >> >> >> Csound mailing list
>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> >> Send bugs reports to
>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>> >> >> >
>>>>> >> >> >
>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>> >> >> > to
>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> >> >> > features
>>>>> >> >> > can
>>>>> >> >> > be posted here
>>>>> >> >>
>>>>> >> >> Csound mailing list
>>>>> >> >> Csound@listserv.heanet.ie
>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> Send bugs reports to
>>>>> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> Discussions of bugs and features can be posted here
>>>>> >> >
>>>>> >> >
>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> >> > features
>>>>> >> > can
>>>>> >> > be posted here
>>>>> >>
>>>>> >> Csound mailing list
>>>>> >> Csound@listserv.heanet.ie
>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> Send bugs reports to
>>>>> >>         https://github.com/csound/csound/issues
>>>>> >> Discussions of bugs and features can be posted here
>>>>> >
>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> > features can
>>>>> > be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>>
>>>
>>> Csound mailing list Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>> be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 08:10
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install

You can just build using cmake as you would on any system. Only you will have to build any libraries you need too, like libsndfile, portaudio, etc.

On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
I poked around in the source tree and the only build documentation I
found is specifically for homebrew... is it still broken?  It could be
I'm looking in the wrong place, or maybe it's so easy that
instructions aren't needed assuming basic familiarity with the system
tools, but I don't know anything about building software in OSX.

Is there a doc or set of instructions I could refer to for help getting started?

On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
> Thanks everyone, this did get my cabbage working with the newest
> csound version, however I still have no CLI version.  What would be
> the best/safest way to continue using the freshest versions with
> cabbage, but maintaining CLI functionality too?
>
> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi <stevenyi@gmail.com> wrote:
>> That is correct.  If the linker path is relative, it will check local
>> to the executable, then the local Framework folder, then the system
>> Framework folder.
>>
>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>> That doesn't seem write though. Perhaps there were some environment
>>> variables set up when trying homebrew.
>>>
>>> On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie> wrote:
>>>>
>>>> I guess OSX checks the user Library folder before the system one.
>>>>
>>>> On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>
>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>> report 6.06.
>>>>>
>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>> > of
>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>> > now
>>>>> > until I get back home in December.  I recommend not using it at this
>>>>> > time
>>>>> > until I or someone else can look into it.
>>>>> >
>>>>> >
>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>> >>
>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>> >> comes with.
>>>>> >>
>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>> >> for loading the library that has left it running a stale version...
>>>>> >>
>>>>> >>
>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>> >> > version of
>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>> >> > is
>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>> >> > wrong
>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>> >> > terminal.
>>>>> >> >
>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>> >> >>
>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>> >> >> getting upgraded?
>>>>> >> >>
>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie>
>>>>> >> >> wrote:
>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>> >> >> > the
>>>>> >> >> > command
>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>> >> >> > Csound
>>>>> >> >> > library.
>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>> >> >> >
>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com>
>>>>> >> >> > wrote:
>>>>> >> >> >>
>>>>> >> >> >> Well, then now I'm really confused.
>>>>> >> >> >>
>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>> >> >> >> command
>>>>> >> >> >> no
>>>>> >> >> >> longer worked at the command line.
>>>>> >> >> >> I installed a fresh download from
>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>> >> >> >>
>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>> >> >> >> reports
>>>>> >> >> >> 6.04
>>>>> >> >> >> still... and from a command line it still says "command not
>>>>> >> >> >> found",
>>>>> >> >> >> as
>>>>> >> >> >> if I have no csound at all.
>>>>> >> >> >>
>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh <rorywalsh@ear.ie>
>>>>> >> >> >> wrote:
>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>> >> >> >> > it
>>>>> >> >> >> > ships
>>>>> >> >> >> > with
>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>> >> >> >> >
>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh <tgrey1@gmail.com>
>>>>> >> >> >> > wrote:
>>>>> >> >> >> >>
>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>> >> >> >> >> over
>>>>> >> >> >> >> the
>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>> >> >> >> >> can
>>>>> >> >> >> >> use
>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>> >> >> >> >>
>>>>> >> >> >> >> When I do:
>>>>> >> >> >> >> brew install -HEAD csound
>>>>> >> >> >> >>
>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>> >> >> >> >> when
>>>>> >> >> >> >> it
>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>> >> >> >> >> it
>>>>> >> >> >> >> still
>>>>> >> >> >> >> reports:
>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>> >> >> >> >>
>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>> >> >> >> >> command
>>>>> >> >> >> >> was
>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>> >> >> >> >> didn't
>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>> >> >> >> >> reports:
>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>> >> >> >> >>
>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>> >> >> >> >>
>>>>> >> >> >> >> Csound mailing list
>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> >> >> Send bugs reports to
>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>> >> >> >> >
>>>>> >> >> >> >
>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>> >> >> >> > reports
>>>>> >> >> >> > to
>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>> >> >> >> > and
>>>>> >> >> >> > features
>>>>> >> >> >> > can
>>>>> >> >> >> > be posted here
>>>>> >> >> >>
>>>>> >> >> >> Csound mailing list
>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> >> Send bugs reports to
>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>> >> >> >
>>>>> >> >> >
>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>> >> >> > to
>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> >> >> > features
>>>>> >> >> > can
>>>>> >> >> > be posted here
>>>>> >> >>
>>>>> >> >> Csound mailing list
>>>>> >> >> Csound@listserv.heanet.ie
>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> >> Send bugs reports to
>>>>> >> >>         https://github.com/csound/csound/issues
>>>>> >> >> Discussions of bugs and features can be posted here
>>>>> >> >
>>>>> >> >
>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> >> > features
>>>>> >> > can
>>>>> >> > be posted here
>>>>> >>
>>>>> >> Csound mailing list
>>>>> >> Csound@listserv.heanet.ie
>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> >> Send bugs reports to
>>>>> >>         https://github.com/csound/csound/issues
>>>>> >> Discussions of bugs and features can be posted here
>>>>> >
>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>> > features can
>>>>> > be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>>
>>>
>>> Csound mailing list Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>> be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 08:19
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks Rory!  Well, that does sound easy.  I had tried that and it
failed, I assumed any needed libraries should already be installed
(including any dev libs) since it has already been built via homebrew
on this system, but perhaps not.

It failed on:
[ 66%] Linking CXX shared library ../libvirtual.dylib
ld: library not found for -lpng
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libvirtual.dylib] Error 1
make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
make: *** [all] Error 2

At least now that I know this *SHOULD* work I won't feel like I'm
completely wasting time trying to figure it out from there.

On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
> You can just build using cmake as you would on any system. Only you will
> have to build any libraries you need too, like libsndfile, portaudio, etc.
>
> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>
>> I poked around in the source tree and the only build documentation I
>> found is specifically for homebrew... is it still broken?  It could be
>> I'm looking in the wrong place, or maybe it's so easy that
>> instructions aren't needed assuming basic familiarity with the system
>> tools, but I don't know anything about building software in OSX.
>>
>> Is there a doc or set of instructions I could refer to for help getting
>> started?
>>
>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>> > Thanks everyone, this did get my cabbage working with the newest
>> > csound version, however I still have no CLI version.  What would be
>> > the best/safest way to continue using the freshest versions with
>> > cabbage, but maintaining CLI functionality too?
>> >
>> > On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>> >> That is correct.  If the linker path is relative, it will check local
>> >> to the executable, then the local Framework folder, then the system
>> >> Framework folder.
>> >>
>> >> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>> >>> That doesn't seem write though. Perhaps there were some environment
>> >>> variables set up when trying homebrew.
>> >>>
>> >>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>> >>>>
>> >>>> I guess OSX checks the user Library folder before the system one.
>> >>>>
>> >>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>> >>>>>
>> >>>>> That was it!  Removing that framework directory suddenly makes
>> >>>>> cabbage
>> >>>>> report 6.06.
>> >>>>>
>> >>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>> >>>>> wrote:
>> >>>>> > Check that there isn't a CsoundLib64.framework in
>> >>>>> > ~/Library/Frameworks
>> >>>>> > folder. If so, try moving or deleting that. The current homebrew
>> >>>>> > build
>> >>>>> > of
>> >>>>> > Csound has problems. I have not found time to look into it and
>> >>>>> > won't
>> >>>>> > now
>> >>>>> > until I get back home in December.  I recommend not using it at
>> >>>>> > this
>> >>>>> > time
>> >>>>> > until I or someone else can look into it.
>> >>>>> >
>> >>>>> >
>> >>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>> >>>>> > wrote:
>> >>>>> >>
>> >>>>> >> But I uninstalled the homebrew version, and confirmed that the
>> >>>>> >> console
>> >>>>> >> version of csound was gone too... I was trying to rule that out
>> >>>>> >> as the
>> >>>>> >> problem, just running the newest cabbage release and the csound
>> >>>>> >> it
>> >>>>> >> comes with.
>> >>>>> >>
>> >>>>> >> My thought is homebrew somehow messed up a file permission or
>> >>>>> >> config
>> >>>>> >> for loading the library that has left it running a stale
>> >>>>> >> version...
>> >>>>> >>
>> >>>>> >>
>> >>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>> >>>>> >> wrote:
>> >>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>> >>>>> >> > version of
>> >>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where
>> >>>>> >> > 6.04
>> >>>>> >> > is
>> >>>>> >> > coming from? I have no idea how homebrew works, is it fetching
>> >>>>> >> > the
>> >>>>> >> > wrong
>> >>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>> >>>>> >> > terminal.
>> >>>>> >> >
>> >>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh 
>> >>>>> >> > wrote:
>> >>>>> >> >>
>> >>>>> >> >> So I'm guessing this means for some reason my csound library
>> >>>>> >> >> isn't
>> >>>>> >> >> getting upgraded?
>> >>>>> >> >>
>> >>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>> >>>>> >> >> wrote:
>> >>>>> >> >> > Cabbage links to the Csound library whereas running csound
>> >>>>> >> >> > from
>> >>>>> >> >> > the
>> >>>>> >> >> > command
>> >>>>> >> >> > line calls the csound application, which in turns calls the
>> >>>>> >> >> > Csound
>> >>>>> >> >> > library.
>> >>>>> >> >> > Cabbage only needs to underlying libraries.
>> >>>>> >> >> >
>> >>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>> >>>>> >> >> > wrote:
>> >>>>> >> >> >>
>> >>>>> >> >> >> Well, then now I'm really confused.
>> >>>>> >> >> >>
>> >>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>> >>>>> >> >> >> command
>> >>>>> >> >> >> no
>> >>>>> >> >> >> longer worked at the command line.
>> >>>>> >> >> >> I installed a fresh download from
>> >>>>> >> >> >> http://www.cabbageaudio.com/download/
>> >>>>> >> >> >>
>> >>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>> >>>>> >> >> >> reports
>> >>>>> >> >> >> 6.04
>> >>>>> >> >> >> still... and from a command line it still says "command not
>> >>>>> >> >> >> found",
>> >>>>> >> >> >> as
>> >>>>> >> >> >> if I have no csound at all.
>> >>>>> >> >> >>
>> >>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>> >>>>> >> >> >> 
>> >>>>> >> >> >> wrote:
>> >>>>> >> >> >> > For what it's worth, I just updated the OSX installer so
>> >>>>> >> >> >> > that
>> >>>>> >> >> >> > it
>> >>>>> >> >> >> > ships
>> >>>>> >> >> >> > with
>> >>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>> >>>>> >> >> >> >
>> >>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh
>> >>>>> >> >> >> > 
>> >>>>> >> >> >> > wrote:
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of
>> >>>>> >> >> >> >> csound
>> >>>>> >> >> >> >> over
>> >>>>> >> >> >> >> the
>> >>>>> >> >> >> >> one packaged with the most recent cabbage release, so
>> >>>>> >> >> >> >> that I
>> >>>>> >> >> >> >> can
>> >>>>> >> >> >> >> use
>> >>>>> >> >> >> >> the new csound features from within cabbage.
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> When I do:
>> >>>>> >> >> >> >> brew install -HEAD csound
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an
>> >>>>> >> >> >> >> overwrite
>> >>>>> >> >> >> >> when
>> >>>>> >> >> >> >> it
>> >>>>> >> >> >> >> linked the first time.  But when I run csound form a
>> >>>>> >> >> >> >> console
>> >>>>> >> >> >> >> it
>> >>>>> >> >> >> >> still
>> >>>>> >> >> >> >> reports:
>> >>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>> >>>>> >> >> >> >> command
>> >>>>> >> >> >> >> was
>> >>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time
>> >>>>> >> >> >> >> it
>> >>>>> >> >> >> >> didn't
>> >>>>> >> >> >> >> require forcing the overwrite, but I still run csound
>> >>>>> >> >> >> >> and it
>> >>>>> >> >> >> >> reports:
>> >>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade
>> >>>>> >> >> >> >> this?
>> >>>>> >> >> >> >>
>> >>>>> >> >> >> >> Csound mailing list
>> >>>>> >> >> >> >> Csound@listserv.heanet.ie
>> >>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> >> >> >> >> Send bugs reports to
>> >>>>> >> >> >> >>         https://github.com/csound/csound/issues
>> >>>>> >> >> >> >> Discussions of bugs and features can be posted here
>> >>>>> >> >> >> >
>> >>>>> >> >> >> >
>> >>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>> >>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>> >> >> >> > reports
>> >>>>> >> >> >> > to
>> >>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of
>> >>>>> >> >> >> > bugs
>> >>>>> >> >> >> > and
>> >>>>> >> >> >> > features
>> >>>>> >> >> >> > can
>> >>>>> >> >> >> > be posted here
>> >>>>> >> >> >>
>> >>>>> >> >> >> Csound mailing list
>> >>>>> >> >> >> Csound@listserv.heanet.ie
>> >>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> >> >> >> Send bugs reports to
>> >>>>> >> >> >>         https://github.com/csound/csound/issues
>> >>>>> >> >> >> Discussions of bugs and features can be posted here
>> >>>>> >> >> >
>> >>>>> >> >> >
>> >>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>> >>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>> >> >> > reports
>> >>>>> >> >> > to
>> >>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>> >>>>> >> >> > and
>> >>>>> >> >> > features
>> >>>>> >> >> > can
>> >>>>> >> >> > be posted here
>> >>>>> >> >>
>> >>>>> >> >> Csound mailing list
>> >>>>> >> >> Csound@listserv.heanet.ie
>> >>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> >> >> Send bugs reports to
>> >>>>> >> >>         https://github.com/csound/csound/issues
>> >>>>> >> >> Discussions of bugs and features can be posted here
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>> >> > reports to
>> >>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >>>>> >> > features
>> >>>>> >> > can
>> >>>>> >> > be posted here
>> >>>>> >>
>> >>>>> >> Csound mailing list
>> >>>>> >> Csound@listserv.heanet.ie
>> >>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> >> Send bugs reports to
>> >>>>> >>         https://github.com/csound/csound/issues
>> >>>>> >> Discussions of bugs and features can be posted here
>> >>>>> >
>> >>>>> > Csound mailing list Csound@listserv.heanet.ie
>> >>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >>>>> > to
>> >>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>> >>>>> > features can
>> >>>>> > be posted here
>> >>>>>
>> >>>>> Csound mailing list
>> >>>>> Csound@listserv.heanet.ie
>> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> Send bugs reports to
>> >>>>>         https://github.com/csound/csound/issues
>> >>>>> Discussions of bugs and features can be posted here
>> >>>>
>> >>>>
>> >>>
>> >>> Csound mailing list Csound@listserv.heanet.ie
>> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >>> https://github.com/csound/csound/issues Discussions of bugs and
>> >>> features can
>> >>> be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 09:10
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
You’re missing libpng in this case.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
> 
> Thanks Rory!  Well, that does sound easy.  I had tried that and it
> failed, I assumed any needed libraries should already be installed
> (including any dev libs) since it has already been built via homebrew
> on this system, but perhaps not.
> 
> It failed on:
> [ 66%] Linking CXX shared library ../libvirtual.dylib
> ld: library not found for -lpng
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[2]: *** [libvirtual.dylib] Error 1
> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
> make: *** [all] Error 2
> 
> At least now that I know this *SHOULD* work I won't feel like I'm
> completely wasting time trying to figure it out from there.
> 
> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>> You can just build using cmake as you would on any system. Only you will
>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>> 
>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>> 
>>> I poked around in the source tree and the only build documentation I
>>> found is specifically for homebrew... is it still broken?  It could be
>>> I'm looking in the wrong place, or maybe it's so easy that
>>> instructions aren't needed assuming basic familiarity with the system
>>> tools, but I don't know anything about building software in OSX.
>>> 
>>> Is there a doc or set of instructions I could refer to for help getting
>>> started?
>>> 
>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>> Thanks everyone, this did get my cabbage working with the newest
>>>> csound version, however I still have no CLI version.  What would be
>>>> the best/safest way to continue using the freshest versions with
>>>> cabbage, but maintaining CLI functionality too?
>>>> 
>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>> That is correct.  If the linker path is relative, it will check local
>>>>> to the executable, then the local Framework folder, then the system
>>>>> Framework folder.
>>>>> 
>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>> variables set up when trying homebrew.
>>>>>> 
>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>> 
>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>> 
>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>> 
>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>> cabbage
>>>>>>>> report 6.06.
>>>>>>>> 
>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>> wrote:
>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>> ~/Library/Frameworks
>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>> build
>>>>>>>>> of
>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>> won't
>>>>>>>>> now
>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>> this
>>>>>>>>> time
>>>>>>>>> until I or someone else can look into it.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>> console
>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>> as the
>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>> it
>>>>>>>>>> comes with.
>>>>>>>>>> 
>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>> config
>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>> version...
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>> wrote:
>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>> version of
>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>> 6.04
>>>>>>>>>>> is
>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>> the
>>>>>>>>>>> wrong
>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>> terminal.
>>>>>>>>>>> 
>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>> isn't
>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>> 
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>> from
>>>>>>>>>>>>> the
>>>>>>>>>>>>> command
>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>> Csound
>>>>>>>>>>>>> library.
>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>> command
>>>>>>>>>>>>>> no
>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>> as
>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>> reports
>>>>>>>>>>>>> to
>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>> and
>>>>>>>>>>>>> features
>>>>>>>>>>>>> can
>>>>>>>>>>>>> be posted here
>>>>>>>>>>>> 
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>> reports to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features
>>>>>>>>>>> can
>>>>>>>>>>> be posted here
>>>>>>>>>> 
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> 
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>> to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> features can
>>>>>>>>> be posted here
>>>>>>>> 
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>> features can
>>>>>> be posted here
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>        https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features can
>> be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 09:26
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Run cmake-gui and disable all libraries that you don't need. Once you get some kind of build going you can start to enable the various libraries. Baby steps all the way! 

On 9 December 2015 at 09:10, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
You’re missing libpng in this case.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 9 Dec 2015, at 08:19, Kevin Welsh <tgrey1@gmail.com> wrote:
>
> Thanks Rory!  Well, that does sound easy.  I had tried that and it
> failed, I assumed any needed libraries should already be installed
> (including any dev libs) since it has already been built via homebrew
> on this system, but perhaps not.
>
> It failed on:
> [ 66%] Linking CXX shared library ../libvirtual.dylib
> ld: library not found for -lpng
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[2]: *** [libvirtual.dylib] Error 1
> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
> make: *** [all] Error 2
>
> At least now that I know this *SHOULD* work I won't feel like I'm
> completely wasting time trying to figure it out from there.
>
> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
>> You can just build using cmake as you would on any system. Only you will
>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>
>> On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
>>>
>>> I poked around in the source tree and the only build documentation I
>>> found is specifically for homebrew... is it still broken?  It could be
>>> I'm looking in the wrong place, or maybe it's so easy that
>>> instructions aren't needed assuming basic familiarity with the system
>>> tools, but I don't know anything about building software in OSX.
>>>
>>> Is there a doc or set of instructions I could refer to for help getting
>>> started?
>>>
>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>> Thanks everyone, this did get my cabbage working with the newest
>>>> csound version, however I still have no CLI version.  What would be
>>>> the best/safest way to continue using the freshest versions with
>>>> cabbage, but maintaining CLI functionality too?
>>>>
>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>>>> That is correct.  If the linker path is relative, it will check local
>>>>> to the executable, then the local Framework folder, then the system
>>>>> Framework folder.
>>>>>
>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>> variables set up when trying homebrew.
>>>>>>
>>>>>> On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie> wrote:
>>>>>>>
>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>
>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>>>>
>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>> cabbage
>>>>>>>> report 6.06.
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi <stevenyi@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>> ~/Library/Frameworks
>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>> build
>>>>>>>>> of
>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>> won't
>>>>>>>>> now
>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>> this
>>>>>>>>> time
>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>> console
>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>> as the
>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>> it
>>>>>>>>>> comes with.
>>>>>>>>>>
>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>> config
>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>> version...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie>
>>>>>>>>>> wrote:
>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>> version of
>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>> 6.04
>>>>>>>>>>> is
>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>> the
>>>>>>>>>>> wrong
>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>> terminal.
>>>>>>>>>>>
>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>> isn't
>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>> from
>>>>>>>>>>>>> the
>>>>>>>>>>>>> command
>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>> Csound
>>>>>>>>>>>>> library.
>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>> command
>>>>>>>>>>>>>> no
>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>> as
>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>> <rorywalsh@ear.ie>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>> <tgrey1@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>> reports
>>>>>>>>>>>>> to
>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>> and
>>>>>>>>>>>>> features
>>>>>>>>>>>>> can
>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>> reports to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features
>>>>>>>>>>> can
>>>>>>>>>>> be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>> to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> features can
>>>>>>>>> be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>> features can
>>>>>> be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>        https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features can
>> be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 09:42
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks Victor!  I have just installed libpng from a fresh source
download, using their cmake instructions (cmake .
-DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
get the same error.

Should libs be installed somewhere else in OSX?

On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
 wrote:
> You’re missing libpng in this case.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>
>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>> failed, I assumed any needed libraries should already be installed
>> (including any dev libs) since it has already been built via homebrew
>> on this system, but perhaps not.
>>
>> It failed on:
>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>> ld: library not found for -lpng
>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>> make[2]: *** [libvirtual.dylib] Error 1
>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>> make: *** [all] Error 2
>>
>> At least now that I know this *SHOULD* work I won't feel like I'm
>> completely wasting time trying to figure it out from there.
>>
>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>> You can just build using cmake as you would on any system. Only you will
>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>
>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>
>>>> I poked around in the source tree and the only build documentation I
>>>> found is specifically for homebrew... is it still broken?  It could be
>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>> instructions aren't needed assuming basic familiarity with the system
>>>> tools, but I don't know anything about building software in OSX.
>>>>
>>>> Is there a doc or set of instructions I could refer to for help getting
>>>> started?
>>>>
>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>> csound version, however I still have no CLI version.  What would be
>>>>> the best/safest way to continue using the freshest versions with
>>>>> cabbage, but maintaining CLI functionality too?
>>>>>
>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>> to the executable, then the local Framework folder, then the system
>>>>>> Framework folder.
>>>>>>
>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>> variables set up when trying homebrew.
>>>>>>>
>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>
>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>
>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>
>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>> cabbage
>>>>>>>>> report 6.06.
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>> wrote:
>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>> build
>>>>>>>>>> of
>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>> won't
>>>>>>>>>> now
>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>> this
>>>>>>>>>> time
>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>> console
>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>> as the
>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>> it
>>>>>>>>>>> comes with.
>>>>>>>>>>>
>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>> config
>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>> version...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>> version of
>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>> 6.04
>>>>>>>>>>>> is
>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>> the
>>>>>>>>>>>> wrong
>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>> terminal.
>>>>>>>>>>>>
>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>> isn't
>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>> from
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> command
>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>> and
>>>>>>>>>>>>>> features
>>>>>>>>>>>>>> can
>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>> reports to
>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> features
>>>>>>>>>>>> can
>>>>>>>>>>>> be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>> to
>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>> features can
>>>>>>>>>> be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>> features can
>>>>>>> be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>> be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 09:44
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Actually Rory, I need libpng!  I'm planning to write a cabbage version
of Menno Knevel's ImagePlayer instrument for Blue.  But thanks anyway,
that's still a useful feature to know about.

On Wed, Dec 9, 2015 at 4:26 AM, Rory Walsh  wrote:
> Run cmake-gui and disable all libraries that you don't need. Once you get
> some kind of build going you can start to enable the various libraries. Baby
> steps all the way!
>
> On 9 December 2015 at 09:10, Victor Lazzarini 
> wrote:
>>
>> You’re missing libpng in this case.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>> >
>> > Thanks Rory!  Well, that does sound easy.  I had tried that and it
>> > failed, I assumed any needed libraries should already be installed
>> > (including any dev libs) since it has already been built via homebrew
>> > on this system, but perhaps not.
>> >
>> > It failed on:
>> > [ 66%] Linking CXX shared library ../libvirtual.dylib
>> > ld: library not found for -lpng
>> > clang: error: linker command failed with exit code 1 (use -v to see
>> > invocation)
>> > make[2]: *** [libvirtual.dylib] Error 1
>> > make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>> > make: *** [all] Error 2
>> >
>> > At least now that I know this *SHOULD* work I won't feel like I'm
>> > completely wasting time trying to figure it out from there.
>> >
>> > On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>> >> You can just build using cmake as you would on any system. Only you
>> >> will
>> >> have to build any libraries you need too, like libsndfile, portaudio,
>> >> etc.
>> >>
>> >> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>> >>>
>> >>> I poked around in the source tree and the only build documentation I
>> >>> found is specifically for homebrew... is it still broken?  It could be
>> >>> I'm looking in the wrong place, or maybe it's so easy that
>> >>> instructions aren't needed assuming basic familiarity with the system
>> >>> tools, but I don't know anything about building software in OSX.
>> >>>
>> >>> Is there a doc or set of instructions I could refer to for help
>> >>> getting
>> >>> started?
>> >>>
>> >>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>> >>>> Thanks everyone, this did get my cabbage working with the newest
>> >>>> csound version, however I still have no CLI version.  What would be
>> >>>> the best/safest way to continue using the freshest versions with
>> >>>> cabbage, but maintaining CLI functionality too?
>> >>>>
>> >>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi 
>> >>>> wrote:
>> >>>>> That is correct.  If the linker path is relative, it will check
>> >>>>> local
>> >>>>> to the executable, then the local Framework folder, then the system
>> >>>>> Framework folder.
>> >>>>>
>> >>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh 
>> >>>>> wrote:
>> >>>>>> That doesn't seem write though. Perhaps there were some environment
>> >>>>>> variables set up when trying homebrew.
>> >>>>>>
>> >>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>> >>>>>>>
>> >>>>>>> I guess OSX checks the user Library folder before the system one.
>> >>>>>>>
>> >>>>>>> On 17 November 2015 at 15:14, Kevin Welsh 
>> >>>>>>> wrote:
>> >>>>>>>>
>> >>>>>>>> That was it!  Removing that framework directory suddenly makes
>> >>>>>>>> cabbage
>> >>>>>>>> report 6.06.
>> >>>>>>>>
>> >>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>> >>>>>>>> wrote:
>> >>>>>>>>> Check that there isn't a CsoundLib64.framework in
>> >>>>>>>>> ~/Library/Frameworks
>> >>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>> >>>>>>>>> build
>> >>>>>>>>> of
>> >>>>>>>>> Csound has problems. I have not found time to look into it and
>> >>>>>>>>> won't
>> >>>>>>>>> now
>> >>>>>>>>> until I get back home in December.  I recommend not using it at
>> >>>>>>>>> this
>> >>>>>>>>> time
>> >>>>>>>>> until I or someone else can look into it.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>> >>>>>>>>>> console
>> >>>>>>>>>> version of csound was gone too... I was trying to rule that out
>> >>>>>>>>>> as the
>> >>>>>>>>>> problem, just running the newest cabbage release and the csound
>> >>>>>>>>>> it
>> >>>>>>>>>> comes with.
>> >>>>>>>>>>
>> >>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>> >>>>>>>>>> config
>> >>>>>>>>>> for loading the library that has left it running a stale
>> >>>>>>>>>> version...
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>> >>>>>>>>>> wrote:
>> >>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>> >>>>>>>>>>> version of
>> >>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure
>> >>>>>>>>>>> where
>> >>>>>>>>>>> 6.04
>> >>>>>>>>>>> is
>> >>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>> >>>>>>>>>>> the
>> >>>>>>>>>>> wrong
>> >>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and
>> >>>>>>>>>>> the
>> >>>>>>>>>>> terminal.
>> >>>>>>>>>>>
>> >>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>> >>>>>>>>>>>> isn't
>> >>>>>>>>>>>> getting upgraded?
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
>> >>>>>>>>>>>> 
>> >>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>> >>>>>>>>>>>>> from
>> >>>>>>>>>>>>> the
>> >>>>>>>>>>>>> command
>> >>>>>>>>>>>>> line calls the csound application, which in turns calls the
>> >>>>>>>>>>>>> Csound
>> >>>>>>>>>>>>> library.
>> >>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Well, then now I'm really confused.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>> >>>>>>>>>>>>>> command
>> >>>>>>>>>>>>>> no
>> >>>>>>>>>>>>>> longer worked at the command line.
>> >>>>>>>>>>>>>> I installed a fresh download from
>> >>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>> >>>>>>>>>>>>>> reports
>> >>>>>>>>>>>>>> 6.04
>> >>>>>>>>>>>>>> still... and from a command line it still says "command not
>> >>>>>>>>>>>>>> found",
>> >>>>>>>>>>>>>> as
>> >>>>>>>>>>>>>> if I have no csound at all.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>> >>>>>>>>>>>>>> 
>> >>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>> >>>>>>>>>>>>>>> that
>> >>>>>>>>>>>>>>> it
>> >>>>>>>>>>>>>>> ships
>> >>>>>>>>>>>>>>> with
>> >>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>> >>>>>>>>>>>>>>> 
>> >>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>> >>>>>>>>>>>>>>>> csound
>> >>>>>>>>>>>>>>>> over
>> >>>>>>>>>>>>>>>> the
>> >>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>> >>>>>>>>>>>>>>>> that I
>> >>>>>>>>>>>>>>>> can
>> >>>>>>>>>>>>>>>> use
>> >>>>>>>>>>>>>>>> the new csound features from within cabbage.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> When I do:
>> >>>>>>>>>>>>>>>> brew install -HEAD csound
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>> >>>>>>>>>>>>>>>> overwrite
>> >>>>>>>>>>>>>>>> when
>> >>>>>>>>>>>>>>>> it
>> >>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>> >>>>>>>>>>>>>>>> console
>> >>>>>>>>>>>>>>>> it
>> >>>>>>>>>>>>>>>> still
>> >>>>>>>>>>>>>>>> reports:
>> >>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>> >>>>>>>>>>>>>>>> command
>> >>>>>>>>>>>>>>>> was
>> >>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>> >>>>>>>>>>>>>>>> it
>> >>>>>>>>>>>>>>>> didn't
>> >>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>> >>>>>>>>>>>>>>>> and it
>> >>>>>>>>>>>>>>>> reports:
>> >>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>> >>>>>>>>>>>>>>>> this?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Csound mailing list
>> >>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>> >>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>>>>>>>>>>>>> Send bugs reports to
>> >>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>> >>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>>>>>>>>>>>> reports
>> >>>>>>>>>>>>>>> to
>> >>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>> >>>>>>>>>>>>>>> bugs
>> >>>>>>>>>>>>>>> and
>> >>>>>>>>>>>>>>> features
>> >>>>>>>>>>>>>>> can
>> >>>>>>>>>>>>>>> be posted here
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Csound mailing list
>> >>>>>>>>>>>>>> Csound@listserv.heanet.ie
>> >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>>>>>>>>>>> Send bugs reports to
>> >>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>> >>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>>>>>>>>>> reports
>> >>>>>>>>>>>>> to
>> >>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>> >>>>>>>>>>>>> and
>> >>>>>>>>>>>>> features
>> >>>>>>>>>>>>> can
>> >>>>>>>>>>>>> be posted here
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Csound mailing list
>> >>>>>>>>>>>> Csound@listserv.heanet.ie
>> >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>>>>>>>>> Send bugs reports to
>> >>>>>>>>>>>>        https://github.com/csound/csound/issues
>> >>>>>>>>>>>> Discussions of bugs and features can be posted here
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>>>>>>>> reports to
>> >>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>> >>>>>>>>>>> and
>> >>>>>>>>>>> features
>> >>>>>>>>>>> can
>> >>>>>>>>>>> be posted here
>> >>>>>>>>>>
>> >>>>>>>>>> Csound mailing list
>> >>>>>>>>>> Csound@listserv.heanet.ie
>> >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>>>>>>> Send bugs reports to
>> >>>>>>>>>>        https://github.com/csound/csound/issues
>> >>>>>>>>>> Discussions of bugs and features can be posted here
>> >>>>>>>>>
>> >>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>> >>>>>>>>> reports
>> >>>>>>>>> to
>> >>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>> >>>>>>>>> features can
>> >>>>>>>>> be posted here
>> >>>>>>>>
>> >>>>>>>> Csound mailing list
>> >>>>>>>> Csound@listserv.heanet.ie
>> >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>>>>> Send bugs reports to
>> >>>>>>>>        https://github.com/csound/csound/issues
>> >>>>>>>> Discussions of bugs and features can be posted here
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >>>>>> to
>> >>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>> >>>>>> features can
>> >>>>>> be posted here
>> >>>>>
>> >>>>> Csound mailing list
>> >>>>> Csound@listserv.heanet.ie
>> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>>> Send bugs reports to
>> >>>>>        https://github.com/csound/csound/issues
>> >>>>> Discussions of bugs and features can be posted here
>> >>>
>> >>> Csound mailing list
>> >>> Csound@listserv.heanet.ie
>> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>> Send bugs reports to
>> >>>        https://github.com/csound/csound/issues
>> >>> Discussions of bugs and features can be posted here
>> >>
>> >> Csound mailing list Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> https://github.com/csound/csound/issues Discussions of bugs and
>> >> features can
>> >> be posted here
>> >
>> > Csound mailing list
>> > Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> > Send bugs reports to
>> >        https://github.com/csound/csound/issues
>> > Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 09:53
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
> 
> Thanks Victor!  I have just installed libpng from a fresh source
> download, using their cmake instructions (cmake .
> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
> get the same error.
> 
> Should libs be installed somewhere else in OSX?
> 
> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>  wrote:
>> You’re missing libpng in this case.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>> 
>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>> failed, I assumed any needed libraries should already be installed
>>> (including any dev libs) since it has already been built via homebrew
>>> on this system, but perhaps not.
>>> 
>>> It failed on:
>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>> ld: library not found for -lpng
>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>> make[2]: *** [libvirtual.dylib] Error 1
>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>> make: *** [all] Error 2
>>> 
>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>> completely wasting time trying to figure it out from there.
>>> 
>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>> You can just build using cmake as you would on any system. Only you will
>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>> 
>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>> 
>>>>> I poked around in the source tree and the only build documentation I
>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>> tools, but I don't know anything about building software in OSX.
>>>>> 
>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>> started?
>>>>> 
>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>> the best/safest way to continue using the freshest versions with
>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>> 
>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>> Framework folder.
>>>>>>> 
>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>> variables set up when trying homebrew.
>>>>>>>> 
>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>> 
>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>> 
>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>> 
>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>> cabbage
>>>>>>>>>> report 6.06.
>>>>>>>>>> 
>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>> wrote:
>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>> build
>>>>>>>>>>> of
>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>> won't
>>>>>>>>>>> now
>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>> this
>>>>>>>>>>> time
>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>> console
>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>> as the
>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>> it
>>>>>>>>>>>> comes with.
>>>>>>>>>>>> 
>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>> config
>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>> version...
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>> version of
>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>> is
>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>> the
>>>>>>>>>>>>> wrong
>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>> reports to
>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> features
>>>>>>>>>>>>> can
>>>>>>>>>>>>> be posted here
>>>>>>>>>>>> 
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>> 
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>> to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features can
>>>>>>>>>>> be posted here
>>>>>>>>>> 
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>> features can
>>>>>>>> be posted here
>>>>>>> 
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>       https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> 
>>>> Csound mailing list Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>> be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 09:58
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Have a look at this:

https://cmake.org/Wiki/CMake_Useful_Variables

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Dec 2015, at 09:53, Victor Lazzarini  wrote:
> 
> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952 
> 
>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>> 
>> Thanks Victor!  I have just installed libpng from a fresh source
>> download, using their cmake instructions (cmake .
>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>> get the same error.
>> 
>> Should libs be installed somewhere else in OSX?
>> 
>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>  wrote:
>>> You’re missing libpng in this case.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>> 
>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>> failed, I assumed any needed libraries should already be installed
>>>> (including any dev libs) since it has already been built via homebrew
>>>> on this system, but perhaps not.
>>>> 
>>>> It failed on:
>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>> ld: library not found for -lpng
>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>> make: *** [all] Error 2
>>>> 
>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>> completely wasting time trying to figure it out from there.
>>>> 
>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>> You can just build using cmake as you would on any system. Only you will
>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>> 
>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>> 
>>>>>> I poked around in the source tree and the only build documentation I
>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>> 
>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>> started?
>>>>>> 
>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>> 
>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>> Framework folder.
>>>>>>>> 
>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>> 
>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>> 
>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>> 
>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>> 
>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>> cabbage
>>>>>>>>>>> report 6.06.
>>>>>>>>>>> 
>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>> build
>>>>>>>>>>>> of
>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>> won't
>>>>>>>>>>>> now
>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>> this
>>>>>>>>>>>> time
>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>> console
>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>> as the
>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>> it
>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>> config
>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>> version...
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>> is
>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>> features
>>>>>>>>>>>>>> can
>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>> 
>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>> to
>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> features can
>>>>>>>>>>>> be posted here
>>>>>>>>>>> 
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> features can
>>>>>>>>> be posted here
>>>>>>>> 
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>> 
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> 
>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>> be posted here
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:02
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I'm sorry if that was unclear, those were the commands I used for
installing libpng.  I don't recall passing any options to cmake when I
ran it here, probably because I didn't think I was doing it right to
begin with so I was just sort of messing around.

I just ran "make clean ; cmake . ; make" and came up with the same error.

I'll take a look at the cmake variables doc you just sent too.  I'm
guessing the important one I need out of all of that is
"CMAKE_LIBRARY_PATH", however I still think if I override that without
knowing the default location for my system, all of my other libs will
then be missing ;)


On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
 wrote:
> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>
>> Thanks Victor!  I have just installed libpng from a fresh source
>> download, using their cmake instructions (cmake .
>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>> get the same error.
>>
>> Should libs be installed somewhere else in OSX?
>>
>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>  wrote:
>>> You’re missing libpng in this case.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>
>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>> failed, I assumed any needed libraries should already be installed
>>>> (including any dev libs) since it has already been built via homebrew
>>>> on this system, but perhaps not.
>>>>
>>>> It failed on:
>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>> ld: library not found for -lpng
>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>> make: *** [all] Error 2
>>>>
>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>> completely wasting time trying to figure it out from there.
>>>>
>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>> You can just build using cmake as you would on any system. Only you will
>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>
>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>
>>>>>> I poked around in the source tree and the only build documentation I
>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>
>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>> started?
>>>>>>
>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>
>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>> Framework folder.
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>
>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>
>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>
>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>
>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>> cabbage
>>>>>>>>>>> report 6.06.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>> build
>>>>>>>>>>>> of
>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>> won't
>>>>>>>>>>>> now
>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>> this
>>>>>>>>>>>> time
>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>> console
>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>> as the
>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>> it
>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>
>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>> config
>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>> version...
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>> is
>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>> features
>>>>>>>>>>>>>> can
>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>> to
>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> features can
>>>>>>>>>>>> be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> features can
>>>>>>>>> be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>       https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>> be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:06
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
"cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
failed on lpng.

On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
> I'm sorry if that was unclear, those were the commands I used for
> installing libpng.  I don't recall passing any options to cmake when I
> ran it here, probably because I didn't think I was doing it right to
> begin with so I was just sort of messing around.
>
> I just ran "make clean ; cmake . ; make" and came up with the same error.
>
> I'll take a look at the cmake variables doc you just sent too.  I'm
> guessing the important one I need out of all of that is
> "CMAKE_LIBRARY_PATH", however I still think if I override that without
> knowing the default location for my system, all of my other libs will
> then be missing ;)
>
>
> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>  wrote:
>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
>> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>
>>> Thanks Victor!  I have just installed libpng from a fresh source
>>> download, using their cmake instructions (cmake .
>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>> get the same error.
>>>
>>> Should libs be installed somewhere else in OSX?
>>>
>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>  wrote:
>>>> You’re missing libpng in this case.
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>
>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>> failed, I assumed any needed libraries should already be installed
>>>>> (including any dev libs) since it has already been built via homebrew
>>>>> on this system, but perhaps not.
>>>>>
>>>>> It failed on:
>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>> ld: library not found for -lpng
>>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>> make: *** [all] Error 2
>>>>>
>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>> completely wasting time trying to figure it out from there.
>>>>>
>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>> You can just build using cmake as you would on any system. Only you will
>>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>>
>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>
>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>
>>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>>> started?
>>>>>>>
>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>> Framework folder.
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>
>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>
>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>
>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>> cabbage
>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>>> build
>>>>>>>>>>>>> of
>>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>>> won't
>>>>>>>>>>>>> now
>>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>>> this
>>>>>>>>>>>>> time
>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>>> console
>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>>> it
>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>>> config
>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>> to
>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> features can
>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>> features can
>>>>>>>>>> be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>       https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>> be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:27
FromGuillermo Senna
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I don't use Mac, but is libpng* located in /usr/local/lib? Maybe you 
just need a symbolic link.

On 09/12/15 07:06, Kevin Welsh wrote:
> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
> failed on lpng.
>
> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>> I'm sorry if that was unclear, those were the commands I used for
>> installing libpng.  I don't recall passing any options to cmake when I
>> ran it here, probably because I didn't think I was doing it right to
>> begin with so I was just sort of messing around.
>>
>> I just ran "make clean ; cmake . ; make" and came up with the same error.
>>
>> I'll take a look at the cmake variables doc you just sent too.  I'm
>> guessing the important one I need out of all of that is
>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>> knowing the default location for my system, all of my other libs will
>> then be missing ;)
>>
>>
>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>  wrote:
>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
>>> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>>
>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>> download, using their cmake instructions (cmake .
>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>>> get the same error.
>>>>
>>>> Should libs be installed somewhere else in OSX?
>>>>
>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>  wrote:
>>>>> You’re missing libpng in this case.
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>>
>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>> (including any dev libs) since it has already been built via homebrew
>>>>>> on this system, but perhaps not.
>>>>>>
>>>>>> It failed on:
>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>> ld: library not found for -lpng
>>>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>> make: *** [all] Error 2
>>>>>>
>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>> completely wasting time trying to figure it out from there.
>>>>>>
>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>>> You can just build using cmake as you would on any system. Only you will
>>>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>>>
>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>
>>>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>>>> started?
>>>>>>>>
>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>>> Framework folder.
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>
>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>>
>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>>>> build
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>> now
>>>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>>>> this
>>>>>>>>>>>>>> time
>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features can
>>>>>>>>>>> be posted here
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>> be posted here
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:32
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
The problem here seems to be that libpng has been detected by Cmake, otherwise 
it would not even try to build libvirtual. But then it fails because it cannot find it.

For what it’s worth, I have libpng installed in /usr/local/lib and never had problems
with it:

ligeti:src victor$ ls /usr/local/lib/libpng
libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la

However, this could be a homebrew issue (I had the impression you are
using it). Did you try installing libpng from inside homebrew?

Regards
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Dec 2015, at 10:06, Kevin Welsh  wrote:
> 
> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
> failed on lpng.
> 
> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>> I'm sorry if that was unclear, those were the commands I used for
>> installing libpng.  I don't recall passing any options to cmake when I
>> ran it here, probably because I didn't think I was doing it right to
>> begin with so I was just sort of messing around.
>> 
>> I just ran "make clean ; cmake . ; make" and came up with the same error.
>> 
>> I'll take a look at the cmake variables doc you just sent too.  I'm
>> guessing the important one I need out of all of that is
>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>> knowing the default location for my system, all of my other libs will
>> then be missing ;)
>> 
>> 
>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>  wrote:
>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
>>> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>> 
>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>> download, using their cmake instructions (cmake .
>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>>> get the same error.
>>>> 
>>>> Should libs be installed somewhere else in OSX?
>>>> 
>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>  wrote:
>>>>> You’re missing libpng in this case.
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>> 
>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>> 
>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>> (including any dev libs) since it has already been built via homebrew
>>>>>> on this system, but perhaps not.
>>>>>> 
>>>>>> It failed on:
>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>> ld: library not found for -lpng
>>>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>> make: *** [all] Error 2
>>>>>> 
>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>> completely wasting time trying to figure it out from there.
>>>>>> 
>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>>> You can just build using cmake as you would on any system. Only you will
>>>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>>> 
>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>> 
>>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>> 
>>>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>>>> started?
>>>>>>>> 
>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>> 
>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>>> Framework folder.
>>>>>>>>>> 
>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>> 
>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>> 
>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>>>> build
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>> now
>>>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>>>> this
>>>>>>>>>>>>>> time
>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features can
>>>>>>>>>>> be posted here
>>>>>>>>>> 
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> 
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> 
>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>> be posted here
>>>>>> 
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>      https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:33
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Yes, because I *just* installed it there manually via the commands:
cmake . -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install

Confirmed with ls:
[05:32:20][tgrey@OTR:~/csound/src/csound-develop]$ ls -l /usr/local/lib/libpng*
lrwxr-xr-x  1 root  admin      10 Dec  9 04:36 /usr/local/lib/libpng.a
-> libpng16.a
lrwxr-xr-x  1 root  admin      14 Dec  9 04:36
/usr/local/lib/libpng.dylib -> libpng16.dylib
-rwxr-xr-x  1 root  wheel  630324 May 12  2014 /usr/local/lib/libpng12.0.dylib
-rwxr-xr-x  1 root  admin  317892 Dec  9 04:36
/usr/local/lib/libpng16.16.19.0.dylib
lrwxr-xr-x  1 root  admin      22 Dec  9 04:36
/usr/local/lib/libpng16.16.dylib -> libpng16.16.19.0.dylib
-rw-r--r--  1 root  admin  406792 Dec  9 04:36 /usr/local/lib/libpng16.a
lrwxr-xr-x  1 root  admin      17 Dec  9 04:36
/usr/local/lib/libpng16.dylib -> libpng16.16.dylib

/usr/local/lib/libpng:
total 16
-rw-r--r--  1 root  admin  1381 Dec  9 04:36 libpng16-noconfig.cmake
-rw-r--r--  1 root  admin  3000 Dec  9 04:32 libpng16.cmake

Is there somewhere better that it *SHOULD* be installed?  Is there
something in OSX analogous to "ldconfig" that I need to run?

On Wed, Dec 9, 2015 at 5:27 AM, Guillermo Senna  wrote:
> I don't use Mac, but is libpng* located in /usr/local/lib? Maybe you just
> need a symbolic link.
>
>
> On 09/12/15 07:06, Kevin Welsh wrote:
>>
>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
>> failed on lpng.
>>
>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>>>
>>> I'm sorry if that was unclear, those were the commands I used for
>>> installing libpng.  I don't recall passing any options to cmake when I
>>> ran it here, probably because I didn't think I was doing it right to
>>> begin with so I was just sort of messing around.
>>>
>>> I just ran "make clean ; cmake . ; make" and came up with the same error.
>>>
>>> I'll take a look at the cmake variables doc you just sent too.  I'm
>>> guessing the important one I need out of all of that is
>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>>> knowing the default location for my system, all of my other libs will
>>> then be missing ;)
>>>
>>>
>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>>  wrote:
>>>>
>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell
>>>> Cmake where your libraries are;
>>>> I am not quite sure why Cmake is not picking it correctly. Try to do a
>>>> make clean and make again.
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>>>
>>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>>> download, using their cmake instructions (cmake .
>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>>>> get the same error.
>>>>>
>>>>> Should libs be installed somewhere else in OSX?
>>>>>
>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>>  wrote:
>>>>>>
>>>>>> You’re missing libpng in this case.
>>>>>> ========================
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>>>
>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>>> (including any dev libs) since it has already been built via homebrew
>>>>>>> on this system, but perhaps not.
>>>>>>>
>>>>>>> It failed on:
>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>>> ld: library not found for -lpng
>>>>>>> clang: error: linker command failed with exit code 1 (use -v to see
>>>>>>> invocation)
>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>>> make: *** [all] Error 2
>>>>>>>
>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>>> completely wasting time trying to figure it out from there.
>>>>>>>
>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>>>>
>>>>>>>> You can just build using cmake as you would on any system. Only you
>>>>>>>> will
>>>>>>>> have to build any libraries you need too, like libsndfile,
>>>>>>>> portaudio, etc.
>>>>>>>>
>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>>>
>>>>>>>>> I poked around in the source tree and the only build documentation
>>>>>>>>> I
>>>>>>>>> found is specifically for homebrew... is it still broken?  It could
>>>>>>>>> be
>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>>> instructions aren't needed assuming basic familiarity with the
>>>>>>>>> system
>>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>>
>>>>>>>>> Is there a doc or set of instructions I could refer to for help
>>>>>>>>> getting
>>>>>>>>> started?
>>>>>>>>>
>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh 
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>>> csound version, however I still have no CLI version.  What would
>>>>>>>>>> be
>>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi 
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> That is correct.  If the linker path is relative, it will check
>>>>>>>>>>> local
>>>>>>>>>>> to the executable, then the local Framework folder, then the
>>>>>>>>>>> system
>>>>>>>>>>> Framework folder.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh 
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
>>>>>>>>>>>> environment
>>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>>
>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
>>>>>>>>>>>>> one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
>>>>>>>>>>>>>>> homebrew
>>>>>>>>>>>>>>> build
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>>> now
>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using it
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that
>>>>>>>>>>>>>>>> out
>>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission
>>>>>>>>>>>>>>>> or
>>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
>>>>>>>>>>>>>>>>> last
>>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure
>>>>>>>>>>>>>>>>> where
>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
>>>>>>>>>>>>>>>>> fetching
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
>>>>>>>>>>>>>>>>>> library
>>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
>>>>>>>>>>>>>>>>>>>> "csound"
>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window
>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command
>>>>>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer
>>>>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
>>>>>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>> reports to
>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> features can
>>>>>>>>>>>> be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>> features can
>>>>>>>> be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>          https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:37
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
libpng has been installed from a homebrew csound build in the past,
but this current instance is a manual download of the source, and
built by hand.

On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
 wrote:
> The problem here seems to be that libpng has been detected by Cmake, otherwise
> it would not even try to build libvirtual. But then it fails because it cannot find it.
>
> For what it’s worth, I have libpng installed in /usr/local/lib and never had problems
> with it:
>
> ligeti:src victor$ ls /usr/local/lib/libpng
> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
>
> However, this could be a homebrew issue (I had the impression you are
> using it). Did you try installing libpng from inside homebrew?
>
> Regards
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 9 Dec 2015, at 10:06, Kevin Welsh  wrote:
>>
>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
>> failed on lpng.
>>
>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>>> I'm sorry if that was unclear, those were the commands I used for
>>> installing libpng.  I don't recall passing any options to cmake when I
>>> ran it here, probably because I didn't think I was doing it right to
>>> begin with so I was just sort of messing around.
>>>
>>> I just ran "make clean ; cmake . ; make" and came up with the same error.
>>>
>>> I'll take a look at the cmake variables doc you just sent too.  I'm
>>> guessing the important one I need out of all of that is
>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>>> knowing the default location for my system, all of my other libs will
>>> then be missing ;)
>>>
>>>
>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>>  wrote:
>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
>>>> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>>>
>>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>>> download, using their cmake instructions (cmake .
>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>>>> get the same error.
>>>>>
>>>>> Should libs be installed somewhere else in OSX?
>>>>>
>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>>  wrote:
>>>>>> You’re missing libpng in this case.
>>>>>> ========================
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>>>
>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>>> (including any dev libs) since it has already been built via homebrew
>>>>>>> on this system, but perhaps not.
>>>>>>>
>>>>>>> It failed on:
>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>>> ld: library not found for -lpng
>>>>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>>> make: *** [all] Error 2
>>>>>>>
>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>>> completely wasting time trying to figure it out from there.
>>>>>>>
>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>>>> You can just build using cmake as you would on any system. Only you will
>>>>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>>>>
>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>>>
>>>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>>
>>>>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>>>>> started?
>>>>>>>>>
>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>>>> Framework folder.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>>
>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>>>>> build
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>>> now
>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> features can
>>>>>>>>>>>> be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>> be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>      https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>       https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:42
FromGuillermo Senna
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I found some posts saying something about update_dyld_shared_cache.

On 09/12/15 07:37, Kevin Welsh wrote:
> libpng has been installed from a homebrew csound build in the past,
> but this current instance is a manual download of the source, and
> built by hand.
>
> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
>  wrote:
>> The problem here seems to be that libpng has been detected by Cmake, otherwise
>> it would not even try to build libvirtual. But then it fails because it cannot find it.
>>
>> For what it’s worth, I have libpng installed in /usr/local/lib and never had problems
>> with it:
>>
>> ligeti:src victor$ ls /usr/local/lib/libpng
>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
>>
>> However, this could be a homebrew issue (I had the impression you are
>> using it). Did you try installing libpng from inside homebrew?
>>
>> Regards
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 9 Dec 2015, at 10:06, Kevin Welsh  wrote:
>>>
>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
>>> failed on lpng.
>>>
>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>>>> I'm sorry if that was unclear, those were the commands I used for
>>>> installing libpng.  I don't recall passing any options to cmake when I
>>>> ran it here, probably because I didn't think I was doing it right to
>>>> begin with so I was just sort of messing around.
>>>>
>>>> I just ran "make clean ; cmake . ; make" and came up with the same error.
>>>>
>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
>>>> guessing the important one I need out of all of that is
>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>>>> knowing the default location for my system, all of my other libs will
>>>> then be missing ;)
>>>>
>>>>
>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>>>  wrote:
>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>>>>
>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>>>> download, using their cmake instructions (cmake .
>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
>>>>>> get the same error.
>>>>>>
>>>>>> Should libs be installed somewhere else in OSX?
>>>>>>
>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>>>  wrote:
>>>>>>> You’re missing libpng in this case.
>>>>>>> ========================
>>>>>>> Dr Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>>
>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>>>>
>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>>>> (including any dev libs) since it has already been built via homebrew
>>>>>>>> on this system, but perhaps not.
>>>>>>>>
>>>>>>>> It failed on:
>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>>>> ld: library not found for -lpng
>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>>>> make: *** [all] Error 2
>>>>>>>>
>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>>>> completely wasting time trying to figure it out from there.
>>>>>>>>
>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh  wrote:
>>>>>>>>> You can just build using cmake as you would on any system. Only you will
>>>>>>>>> have to build any libraries you need too, like libsndfile, portaudio, etc.
>>>>>>>>>
>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>>>
>>>>>>>>>> Is there a doc or set of instructions I could refer to for help getting
>>>>>>>>>> started?
>>>>>>>>>>
>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>>>>> Framework folder.
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes
>>>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current homebrew
>>>>>>>>>>>>>>>> build
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it and
>>>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>>>> now
>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using it at
>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed that the
>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule that out
>>>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the csound
>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file permission or
>>>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not sure where
>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it fetching
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound library
>>>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running csound
>>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns calls the
>>>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says "command not
>>>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX installer so
>>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build of
>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release, so
>>>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form a
>>>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this time
>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run csound
>>>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to upgrade
>>>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> features can
>>>>>>>>>>>>> be posted here
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>>> be posted here
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:48
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Why not just use all the libraries Victor has packaged in his installer. Just point cmake to those and you won't need to rebuild them all manually?  

On 9 December 2015 at 10:42, Guillermo Senna <gsenna@gmail.com> wrote:
I found some posts saying something about update_dyld_shared_cache.


On 09/12/15 07:37, Kevin Welsh wrote:
libpng has been installed from a homebrew csound build in the past,
but this current instance is a manual download of the source, and
built by hand.

On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
The problem here seems to be that libpng has been detected by Cmake, otherwise
it would not even try to build libvirtual. But then it fails because it cannot find it.

For what it’s worth, I have libpng installed in /usr/local/lib and never had problems
with it:

ligeti:src victor$ ls /usr/local/lib/libpng
libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la

However, this could be a homebrew issue (I had the impression you are
using it). Did you try installing libpng from inside homebrew?

Regards
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 9 Dec 2015, at 10:06, Kevin Welsh <tgrey1@gmail.com> wrote:

Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
"cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
failed on lpng.

On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
I'm sorry if that was unclear, those were the commands I used for
installing libpng.  I don't recall passing any options to cmake when I
ran it here, probably because I didn't think I was doing it right to
begin with so I was just sort of messing around.

I just ran "make clean ; cmake . ; make" and came up with the same error.

I'll take a look at the cmake variables doc you just sent too.  I'm
guessing the important one I need out of all of that is
"CMAKE_LIBRARY_PATH", however I still think if I override that without
knowing the default location for my system, all of my other libs will
then be missing ;)


On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
CMAKE_INSTALL_PREFIX only affects Csound installation. You need to tell Cmake where your libraries are;
I am not quite sure why Cmake is not picking it correctly. Try to do a make clean and make again.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 9 Dec 2015, at 09:42, Kevin Welsh <tgrey1@gmail.com> wrote:

Thanks Victor!  I have just installed libpng from a fresh source
download, using their cmake instructions (cmake .
-DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I still
get the same error.

Should libs be installed somewhere else in OSX?

On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
<Victor.Lazzarini@nuim.ie> wrote:
You’re missing libpng in this case.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 9 Dec 2015, at 08:19, Kevin Welsh <tgrey1@gmail.com> wrote:

Thanks Rory!  Well, that does sound easy.  I had tried that and it
failed, I assumed any needed libraries should already be installed
(including any dev libs) since it has already been built via homebrew
on this system, but perhaps not.

It failed on:
[ 66%] Linking CXX shared library ../libvirtual.dylib
ld: library not found for -lpng
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libvirtual.dylib] Error 1
make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
make: *** [all] Error 2

At least now that I know this *SHOULD* work I won't feel like I'm
completely wasting time trying to figure it out from there.

On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
You can just build using cmake as you would on any system. Only you will
have to build any libraries you need too, like libsndfile, portaudio, etc.

On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
I poked around in the source tree and the only build documentation I
found is specifically for homebrew... is it still broken?  It could be
I'm looking in the wrong place, or maybe it's so easy that
instructions aren't needed assuming basic familiarity with the system
tools, but I don't know anything about building software in OSX.

Is there a doc or set of instructions I could refer to for help getting
started?

On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
Thanks everyone, this did get my cabbage working with the newest
csound version, however I still have no CLI version.  What would be
the best/safest way to continue using the freshest versions with
cabbage, but maintaining CLI functionality too?

On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi <stevenyi@gmail.com> wrote:
That is correct.  If the linker path is relative, it will check local
to the executable, then the local Framework folder, then the system
Framework folder.

On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
That doesn't seem write though. Perhaps there were some environment
variables set up when trying homebrew.

On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie> wrote:
I guess OSX checks the user Library folder before the system one.

On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com> wrote:
That was it!  Removing that framework directory suddenly makes
cabbage
report 6.06.

On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi <stevenyi@gmail.com>
wrote:
Check that there isn't a CsoundLib64.framework in
~/Library/Frameworks
folder. If so, try moving or deleting that. The current homebrew
build
of
Csound has problems. I have not found time to look into it and
won't
now
until I get back home in December.  I recommend not using it at
this
time
until I or someone else can look into it.


On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh <tgrey1@gmail.com>
wrote:
But I uninstalled the homebrew version, and confirmed that the
console
version of csound was gone too... I was trying to rule that out
as the
problem, just running the newest cabbage release and the csound
it
comes with.

My thought is homebrew somehow messed up a file permission or
config
for loading the library that has left it running a stale
version...


On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh <rorywalsh@ear.ie>
wrote:
I'm not sure what's going on because I'm pretty sure the last
version of
Cabbage you installed on OSX installed 6.05, I'm not sure where
6.04
is
coming from? I have no idea how homebrew works, is it fetching
the
wrong
package? I've only ever built Csound on OSX using cmake and the
terminal.

On 17 November 2015 at 14:29, Kevin Welsh <tgrey1@gmail.com>
wrote:
So I'm guessing this means for some reason my csound library
isn't
getting upgraded?

On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh <rorywalsh@ear.ie>
wrote:
Cabbage links to the Csound library whereas running csound
from
the
command
line calls the csound application, which in turns calls the
Csound
library.
Cabbage only needs to underlying libraries.

On 17 November 2015 at 12:38, Kevin Welsh <tgrey1@gmail.com>
wrote:
Well, then now I'm really confused.

I uninstalled the homebrew version, confirmed that "csound"
command
no
longer worked at the command line.
I installed a fresh download from
http://www.cabbageaudio.com/download/

Cabbage appears to work fine, but in the output window it
reports
6.04
still... and from a command line it still says "command not
found",
as
if I have no csound at all.

On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
<rorywalsh@ear.ie>
wrote:
For what it's worth, I just updated the OSX installer so
that
it
ships
with
the latest version of Csound, i.e., 6.06.

On 17 November 2015 at 03:08, Kevin Welsh
<tgrey1@gmail.com>
wrote:
My goal is to use homebrew to install a fresh build of
csound
over
the
one packaged with the most recent cabbage release, so
that I
can
use
the new csound features from within cabbage.

When I do:
brew install -HEAD csound

it appears to fetch and build 6.05, and I forced an
overwrite
when
it
linked the first time.  But when I run csound form a
console
it
still
reports:
Csound version 6.04 (double samples) Feb 26 2015

I tried uninstalling via homebrew, confirming my csound
command
was
gone, and rebuilding via the homebrew command, this time
it
didn't
require forcing the overwrite, but I still run csound
and it
reports:
Csound version 6.04 (double samples) Feb 26 2015

What am I doing wrong or forgetting to do to upgrade
this?

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
reports
to
https://github.com/csound/csound/issues Discussions of
bugs
and
features
can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
reports
to
https://github.com/csound/csound/issues Discussions of bugs
and
features
can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
reports to
https://github.com/csound/csound/issues Discussions of bugs and
features
can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
to
https://github.com/csound/csound/issues Discussions of bugs and
features can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
https://github.com/csound/csound/issues Discussions of bugs and
features can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
https://github.com/csound/csound/issues Discussions of bugs and features can
be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 10:52
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
If that's possible, that sounds like a great shortcut!  Where exactly
would I be pointing to (keeping in mind the only current installed
csound version came with cabbage in case it matters)?  And I assume
that's using: cmake -DCMAKE_LIBRARY_PATH=???

On Wed, Dec 9, 2015 at 5:48 AM, Rory Walsh  wrote:
> Why not just use all the libraries Victor has packaged in his installer.
> Just point cmake to those and you won't need to rebuild them all manually?
>
> On 9 December 2015 at 10:42, Guillermo Senna  wrote:
>>
>> I found some posts saying something about update_dyld_shared_cache.
>>
>>
>> On 09/12/15 07:37, Kevin Welsh wrote:
>>>
>>> libpng has been installed from a homebrew csound build in the past,
>>> but this current instance is a manual download of the source, and
>>> built by hand.
>>>
>>> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
>>>  wrote:
>>>>
>>>> The problem here seems to be that libpng has been detected by Cmake,
>>>> otherwise
>>>> it would not even try to build libvirtual. But then it fails because it
>>>> cannot find it.
>>>>
>>>> For what it’s worth, I have libpng installed in /usr/local/lib and never
>>>> had problems
>>>> with it:
>>>>
>>>> ligeti:src victor$ ls /usr/local/lib/libpng
>>>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
>>>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
>>>>
>>>> However, this could be a homebrew issue (I had the impression you are
>>>> using it). Did you try installing libpng from inside homebrew?
>>>>
>>>> Regards
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 9 Dec 2015, at 10:06, Kevin Welsh  wrote:
>>>>>
>>>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
>>>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
>>>>> failed on lpng.
>>>>>
>>>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
>>>>>>
>>>>>> I'm sorry if that was unclear, those were the commands I used for
>>>>>> installing libpng.  I don't recall passing any options to cmake when I
>>>>>> ran it here, probably because I didn't think I was doing it right to
>>>>>> begin with so I was just sort of messing around.
>>>>>>
>>>>>> I just ran "make clean ; cmake . ; make" and came up with the same
>>>>>> error.
>>>>>>
>>>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
>>>>>> guessing the important one I need out of all of that is
>>>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>>>>>> knowing the default location for my system, all of my other libs will
>>>>>> then be missing ;)
>>>>>>
>>>>>>
>>>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>>>>>  wrote:
>>>>>>>
>>>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to
>>>>>>> tell Cmake where your libraries are;
>>>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do
>>>>>>> a make clean and make again.
>>>>>>> ========================
>>>>>>> Dr Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>>
>>>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
>>>>>>>>
>>>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>>>>>> download, using their cmake instructions (cmake .
>>>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I
>>>>>>>> still
>>>>>>>> get the same error.
>>>>>>>>
>>>>>>>> Should libs be installed somewhere else in OSX?
>>>>>>>>
>>>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>>>
>>>>>>>>> You’re missing libpng in this case.
>>>>>>>>> ========================
>>>>>>>>> Dr Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>
>>>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>>>>>> (including any dev libs) since it has already been built via
>>>>>>>>>> homebrew
>>>>>>>>>> on this system, but perhaps not.
>>>>>>>>>>
>>>>>>>>>> It failed on:
>>>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>>>>>> ld: library not found for -lpng
>>>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to
>>>>>>>>>> see invocation)
>>>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>>>>>> make: *** [all] Error 2
>>>>>>>>>>
>>>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>>>>>> completely wasting time trying to figure it out from there.
>>>>>>>>>>
>>>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh 
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> You can just build using cmake as you would on any system. Only
>>>>>>>>>>> you will
>>>>>>>>>>> have to build any libraries you need too, like libsndfile,
>>>>>>>>>>> portaudio, etc.
>>>>>>>>>>>
>>>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I poked around in the source tree and the only build
>>>>>>>>>>>> documentation I
>>>>>>>>>>>> found is specifically for homebrew... is it still broken?  It
>>>>>>>>>>>> could be
>>>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>>>>>> instructions aren't needed assuming basic familiarity with the
>>>>>>>>>>>> system
>>>>>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>>>>>
>>>>>>>>>>>> Is there a doc or set of instructions I could refer to for help
>>>>>>>>>>>> getting
>>>>>>>>>>>> started?
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the
>>>>>>>>>>>>> newest
>>>>>>>>>>>>> csound version, however I still have no CLI version.  What
>>>>>>>>>>>>> would be
>>>>>>>>>>>>> the best/safest way to continue using the freshest versions
>>>>>>>>>>>>> with
>>>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi
>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That is correct.  If the linker path is relative, it will
>>>>>>>>>>>>>> check local
>>>>>>>>>>>>>> to the executable, then the local Framework folder, then the
>>>>>>>>>>>>>> system
>>>>>>>>>>>>>> Framework folder.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
>>>>>>>>>>>>>>> environment
>>>>>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
>>>>>>>>>>>>>>>> one.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly
>>>>>>>>>>>>>>>>> makes
>>>>>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
>>>>>>>>>>>>>>>>>> homebrew
>>>>>>>>>>>>>>>>>> build
>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>>>>>> now
>>>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using
>>>>>>>>>>>>>>>>>> it at
>>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed
>>>>>>>>>>>>>>>>>>> that the
>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule
>>>>>>>>>>>>>>>>>>> that out
>>>>>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file
>>>>>>>>>>>>>>>>>>> permission or
>>>>>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
>>>>>>>>>>>>>>>>>>>> last
>>>>>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not
>>>>>>>>>>>>>>>>>>>> sure where
>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
>>>>>>>>>>>>>>>>>>>> fetching
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake
>>>>>>>>>>>>>>>>>>>> and the
>>>>>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
>>>>>>>>>>>>>>>>>>>>> library
>>>>>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns
>>>>>>>>>>>>>>>>>>>>>> calls the
>>>>>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
>>>>>>>>>>>>>>>>>>>>>>> "csound"
>>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output
>>>>>>>>>>>>>>>>>>>>>>> window it
>>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says
>>>>>>>>>>>>>>>>>>>>>>> "command not
>>>>>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX
>>>>>>>>>>>>>>>>>>>>>>>> installer so
>>>>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build
>>>>>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release,
>>>>>>>>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form
>>>>>>>>>>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
>>>>>>>>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to
>>>>>>>>>>>>>>>>>>>>>>>>> upgrade
>>>>>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions
>>>>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>> bugs and
>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>> bugs and
>>>>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>> to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features can
>>>>>>>>>>> be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>          https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 10:58
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I think Victor's installer puts the libraries in all the places cmake looks? Install fresh from Victors package and then try running cmake again perhaps? 

On 9 December 2015 at 10:52, Kevin Welsh <tgrey1@gmail.com> wrote:
If that's possible, that sounds like a great shortcut!  Where exactly
would I be pointing to (keeping in mind the only current installed
csound version came with cabbage in case it matters)?  And I assume
that's using: cmake -DCMAKE_LIBRARY_PATH=???

On Wed, Dec 9, 2015 at 5:48 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> Why not just use all the libraries Victor has packaged in his installer.
> Just point cmake to those and you won't need to rebuild them all manually?
>
> On 9 December 2015 at 10:42, Guillermo Senna <gsenna@gmail.com> wrote:
>>
>> I found some posts saying something about update_dyld_shared_cache.
>>
>>
>> On 09/12/15 07:37, Kevin Welsh wrote:
>>>
>>> libpng has been installed from a homebrew csound build in the past,
>>> but this current instance is a manual download of the source, and
>>> built by hand.
>>>
>>> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
>>> <Victor.Lazzarini@nuim.ie> wrote:
>>>>
>>>> The problem here seems to be that libpng has been detected by Cmake,
>>>> otherwise
>>>> it would not even try to build libvirtual. But then it fails because it
>>>> cannot find it.
>>>>
>>>> For what it’s worth, I have libpng installed in /usr/local/lib and never
>>>> had problems
>>>> with it:
>>>>
>>>> ligeti:src victor$ ls /usr/local/lib/libpng
>>>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
>>>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
>>>>
>>>> However, this could be a homebrew issue (I had the impression you are
>>>> using it). Did you try installing libpng from inside homebrew?
>>>>
>>>> Regards
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 9 Dec 2015, at 10:06, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>
>>>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
>>>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
>>>>> failed on lpng.
>>>>>
>>>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>>
>>>>>> I'm sorry if that was unclear, those were the commands I used for
>>>>>> installing libpng.  I don't recall passing any options to cmake when I
>>>>>> ran it here, probably because I didn't think I was doing it right to
>>>>>> begin with so I was just sort of messing around.
>>>>>>
>>>>>> I just ran "make clean ; cmake . ; make" and came up with the same
>>>>>> error.
>>>>>>
>>>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
>>>>>> guessing the important one I need out of all of that is
>>>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
>>>>>> knowing the default location for my system, all of my other libs will
>>>>>> then be missing ;)
>>>>>>
>>>>>>
>>>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
>>>>>> <Victor.Lazzarini@nuim.ie> wrote:
>>>>>>>
>>>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to
>>>>>>> tell Cmake where your libraries are;
>>>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do
>>>>>>> a make clean and make again.
>>>>>>> ========================
>>>>>>> Dr Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>>
>>>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
>>>>>>>> download, using their cmake instructions (cmake .
>>>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I
>>>>>>>> still
>>>>>>>> get the same error.
>>>>>>>>
>>>>>>>> Should libs be installed somewhere else in OSX?
>>>>>>>>
>>>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
>>>>>>>> <Victor.Lazzarini@nuim.ie> wrote:
>>>>>>>>>
>>>>>>>>> You’re missing libpng in this case.
>>>>>>>>> ========================
>>>>>>>>> Dr Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>
>>>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh <tgrey1@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
>>>>>>>>>> failed, I assumed any needed libraries should already be installed
>>>>>>>>>> (including any dev libs) since it has already been built via
>>>>>>>>>> homebrew
>>>>>>>>>> on this system, but perhaps not.
>>>>>>>>>>
>>>>>>>>>> It failed on:
>>>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
>>>>>>>>>> ld: library not found for -lpng
>>>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to
>>>>>>>>>> see invocation)
>>>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
>>>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
>>>>>>>>>> make: *** [all] Error 2
>>>>>>>>>>
>>>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
>>>>>>>>>> completely wasting time trying to figure it out from there.
>>>>>>>>>>
>>>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh <rorywalsh@ear.ie>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> You can just build using cmake as you would on any system. Only
>>>>>>>>>>> you will
>>>>>>>>>>> have to build any libraries you need too, like libsndfile,
>>>>>>>>>>> portaudio, etc.
>>>>>>>>>>>
>>>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I poked around in the source tree and the only build
>>>>>>>>>>>> documentation I
>>>>>>>>>>>> found is specifically for homebrew... is it still broken?  It
>>>>>>>>>>>> could be
>>>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>>>>>> instructions aren't needed assuming basic familiarity with the
>>>>>>>>>>>> system
>>>>>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>>>>>
>>>>>>>>>>>> Is there a doc or set of instructions I could refer to for help
>>>>>>>>>>>> getting
>>>>>>>>>>>> started?
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the
>>>>>>>>>>>>> newest
>>>>>>>>>>>>> csound version, however I still have no CLI version.  What
>>>>>>>>>>>>> would be
>>>>>>>>>>>>> the best/safest way to continue using the freshest versions
>>>>>>>>>>>>> with
>>>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi
>>>>>>>>>>>>> <stevenyi@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That is correct.  If the linker path is relative, it will
>>>>>>>>>>>>>> check local
>>>>>>>>>>>>>> to the executable, then the local Framework folder, then the
>>>>>>>>>>>>>> system
>>>>>>>>>>>>>> Framework folder.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
>>>>>>>>>>>>>>> environment
>>>>>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
>>>>>>>>>>>>>>>> one.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly
>>>>>>>>>>>>>>>>> makes
>>>>>>>>>>>>>>>>> cabbage
>>>>>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
>>>>>>>>>>>>>>>>> <stevenyi@gmail.com>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
>>>>>>>>>>>>>>>>>> ~/Library/Frameworks
>>>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
>>>>>>>>>>>>>>>>>> homebrew
>>>>>>>>>>>>>>>>>> build
>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> won't
>>>>>>>>>>>>>>>>>> now
>>>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using
>>>>>>>>>>>>>>>>>> it at
>>>>>>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>> until I or someone else can look into it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh
>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed
>>>>>>>>>>>>>>>>>>> that the
>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule
>>>>>>>>>>>>>>>>>>> that out
>>>>>>>>>>>>>>>>>>> as the
>>>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>> comes with.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file
>>>>>>>>>>>>>>>>>>> permission or
>>>>>>>>>>>>>>>>>>> config
>>>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
>>>>>>>>>>>>>>>>>>> version...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
>>>>>>>>>>>>>>>>>>>> last
>>>>>>>>>>>>>>>>>>>> version of
>>>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not
>>>>>>>>>>>>>>>>>>>> sure where
>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
>>>>>>>>>>>>>>>>>>>> fetching
>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> wrong
>>>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake
>>>>>>>>>>>>>>>>>>>> and the
>>>>>>>>>>>>>>>>>>>> terminal.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
>>>>>>>>>>>>>>>>>>>>> library
>>>>>>>>>>>>>>>>>>>>> isn't
>>>>>>>>>>>>>>>>>>>>> getting upgraded?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns
>>>>>>>>>>>>>>>>>>>>>> calls the
>>>>>>>>>>>>>>>>>>>>>> Csound
>>>>>>>>>>>>>>>>>>>>>> library.
>>>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
>>>>>>>>>>>>>>>>>>>>>>> "csound"
>>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>>> no
>>>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
>>>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
>>>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output
>>>>>>>>>>>>>>>>>>>>>>> window it
>>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>>> 6.04
>>>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says
>>>>>>>>>>>>>>>>>>>>>>> "command not
>>>>>>>>>>>>>>>>>>>>>>> found",
>>>>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
>>>>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX
>>>>>>>>>>>>>>>>>>>>>>>> installer so
>>>>>>>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>> ships
>>>>>>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
>>>>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build
>>>>>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> over
>>>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release,
>>>>>>>>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>>>>>>>> that I
>>>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>>>> use
>>>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> When I do:
>>>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
>>>>>>>>>>>>>>>>>>>>>>>>> overwrite
>>>>>>>>>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form
>>>>>>>>>>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>>>>>>>>>> console
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> still
>>>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> command
>>>>>>>>>>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
>>>>>>>>>>>>>>>>>>>>>>>>> time
>>>>>>>>>>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>>>>>>>>> didn't
>>>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run
>>>>>>>>>>>>>>>>>>>>>>>>> csound
>>>>>>>>>>>>>>>>>>>>>>>>> and it
>>>>>>>>>>>>>>>>>>>>>>>>> reports:
>>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to
>>>>>>>>>>>>>>>>>>>>>>>>> upgrade
>>>>>>>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions
>>>>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
>>>>>>>>>>>>>>>>>>>> bugs
>>>>>>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>>>> bugs and
>>>>>>>>>>>>>>>>>>>> features
>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>>>>> reports
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
>>>>>>>>>>>>>>>>>> bugs and
>>>>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>>>> reports to
>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> features can
>>>>>>>>>>>>>>> be posted here
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>> to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> features can
>>>>>>>>>>> be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>          https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 13:00
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
No, we don’t do that anymore. It all goes into the framework, and they are not usable that way
for developers.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 9 Dec 2015, at 10:58, Rory Walsh  wrote:
> 
> I think Victor's installer puts the libraries in all the places cmake looks? Install fresh from Victors package and then try running cmake again perhaps? 
> 
> On 9 December 2015 at 10:52, Kevin Welsh  wrote:
> If that's possible, that sounds like a great shortcut!  Where exactly
> would I be pointing to (keeping in mind the only current installed
> csound version came with cabbage in case it matters)?  And I assume
> that's using: cmake -DCMAKE_LIBRARY_PATH=???
> 
> On Wed, Dec 9, 2015 at 5:48 AM, Rory Walsh  wrote:
> > Why not just use all the libraries Victor has packaged in his installer.
> > Just point cmake to those and you won't need to rebuild them all manually?
> >
> > On 9 December 2015 at 10:42, Guillermo Senna  wrote:
> >>
> >> I found some posts saying something about update_dyld_shared_cache.
> >>
> >>
> >> On 09/12/15 07:37, Kevin Welsh wrote:
> >>>
> >>> libpng has been installed from a homebrew csound build in the past,
> >>> but this current instance is a manual download of the source, and
> >>> built by hand.
> >>>
> >>> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
> >>>  wrote:
> >>>>
> >>>> The problem here seems to be that libpng has been detected by Cmake,
> >>>> otherwise
> >>>> it would not even try to build libvirtual. But then it fails because it
> >>>> cannot find it.
> >>>>
> >>>> For what it’s worth, I have libpng installed in /usr/local/lib and never
> >>>> had problems
> >>>> with it:
> >>>>
> >>>> ligeti:src victor$ ls /usr/local/lib/libpng
> >>>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
> >>>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
> >>>>
> >>>> However, this could be a homebrew issue (I had the impression you are
> >>>> using it). Did you try installing libpng from inside homebrew?
> >>>>
> >>>> Regards
> >>>> ========================
> >>>> Dr Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 9 Dec 2015, at 10:06, Kevin Welsh  wrote:
> >>>>>
> >>>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
> >>>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
> >>>>> failed on lpng.
> >>>>>
> >>>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh  wrote:
> >>>>>>
> >>>>>> I'm sorry if that was unclear, those were the commands I used for
> >>>>>> installing libpng.  I don't recall passing any options to cmake when I
> >>>>>> ran it here, probably because I didn't think I was doing it right to
> >>>>>> begin with so I was just sort of messing around.
> >>>>>>
> >>>>>> I just ran "make clean ; cmake . ; make" and came up with the same
> >>>>>> error.
> >>>>>>
> >>>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
> >>>>>> guessing the important one I need out of all of that is
> >>>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
> >>>>>> knowing the default location for my system, all of my other libs will
> >>>>>> then be missing ;)
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
> >>>>>>  wrote:
> >>>>>>>
> >>>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to
> >>>>>>> tell Cmake where your libraries are;
> >>>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do
> >>>>>>> a make clean and make again.
> >>>>>>> ========================
> >>>>>>> Dr Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>> Maynooth University,
> >>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>> Tel: 00 353 7086936
> >>>>>>> Fax: 00 353 1 7086952
> >>>>>>>
> >>>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh  wrote:
> >>>>>>>>
> >>>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
> >>>>>>>> download, using their cmake instructions (cmake .
> >>>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I
> >>>>>>>> still
> >>>>>>>> get the same error.
> >>>>>>>>
> >>>>>>>> Should libs be installed somewhere else in OSX?
> >>>>>>>>
> >>>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
> >>>>>>>>  wrote:
> >>>>>>>>>
> >>>>>>>>> You’re missing libpng in this case.
> >>>>>>>>> ========================
> >>>>>>>>> Dr Victor Lazzarini
> >>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>>>> Maynooth University,
> >>>>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>>>> Tel: 00 353 7086936
> >>>>>>>>> Fax: 00 353 1 7086952
> >>>>>>>>>
> >>>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh  wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
> >>>>>>>>>> failed, I assumed any needed libraries should already be installed
> >>>>>>>>>> (including any dev libs) since it has already been built via
> >>>>>>>>>> homebrew
> >>>>>>>>>> on this system, but perhaps not.
> >>>>>>>>>>
> >>>>>>>>>> It failed on:
> >>>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
> >>>>>>>>>> ld: library not found for -lpng
> >>>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to
> >>>>>>>>>> see invocation)
> >>>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
> >>>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
> >>>>>>>>>> make: *** [all] Error 2
> >>>>>>>>>>
> >>>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
> >>>>>>>>>> completely wasting time trying to figure it out from there.
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh 
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> You can just build using cmake as you would on any system. Only
> >>>>>>>>>>> you will
> >>>>>>>>>>> have to build any libraries you need too, like libsndfile,
> >>>>>>>>>>> portaudio, etc.
> >>>>>>>>>>>
> >>>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh"  wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I poked around in the source tree and the only build
> >>>>>>>>>>>> documentation I
> >>>>>>>>>>>> found is specifically for homebrew... is it still broken?  It
> >>>>>>>>>>>> could be
> >>>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
> >>>>>>>>>>>> instructions aren't needed assuming basic familiarity with the
> >>>>>>>>>>>> system
> >>>>>>>>>>>> tools, but I don't know anything about building software in OSX.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Is there a doc or set of instructions I could refer to for help
> >>>>>>>>>>>> getting
> >>>>>>>>>>>> started?
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh 
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the
> >>>>>>>>>>>>> newest
> >>>>>>>>>>>>> csound version, however I still have no CLI version.  What
> >>>>>>>>>>>>> would be
> >>>>>>>>>>>>> the best/safest way to continue using the freshest versions
> >>>>>>>>>>>>> with
> >>>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi
> >>>>>>>>>>>>>  wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> That is correct.  If the linker path is relative, it will
> >>>>>>>>>>>>>> check local
> >>>>>>>>>>>>>> to the executable, then the local Framework folder, then the
> >>>>>>>>>>>>>> system
> >>>>>>>>>>>>>> Framework folder.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh 
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
> >>>>>>>>>>>>>>> environment
> >>>>>>>>>>>>>>> variables set up when trying homebrew.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh 
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
> >>>>>>>>>>>>>>>> one.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh 
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly
> >>>>>>>>>>>>>>>>> makes
> >>>>>>>>>>>>>>>>> cabbage
> >>>>>>>>>>>>>>>>> report 6.06.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
> >>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
> >>>>>>>>>>>>>>>>>> ~/Library/Frameworks
> >>>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
> >>>>>>>>>>>>>>>>>> homebrew
> >>>>>>>>>>>>>>>>>> build
> >>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
> >>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>> won't
> >>>>>>>>>>>>>>>>>> now
> >>>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using
> >>>>>>>>>>>>>>>>>> it at
> >>>>>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>> until I or someone else can look into it.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh
> >>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed
> >>>>>>>>>>>>>>>>>>> that the
> >>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule
> >>>>>>>>>>>>>>>>>>> that out
> >>>>>>>>>>>>>>>>>>> as the
> >>>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
> >>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>> comes with.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file
> >>>>>>>>>>>>>>>>>>> permission or
> >>>>>>>>>>>>>>>>>>> config
> >>>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
> >>>>>>>>>>>>>>>>>>> version...
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
> >>>>>>>>>>>>>>>>>>>> last
> >>>>>>>>>>>>>>>>>>>> version of
> >>>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not
> >>>>>>>>>>>>>>>>>>>> sure where
> >>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>> is
> >>>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
> >>>>>>>>>>>>>>>>>>>> fetching
> >>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>> wrong
> >>>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake
> >>>>>>>>>>>>>>>>>>>> and the
> >>>>>>>>>>>>>>>>>>>> terminal.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
> >>>>>>>>>>>>>>>>>>>>> library
> >>>>>>>>>>>>>>>>>>>>> isn't
> >>>>>>>>>>>>>>>>>>>>> getting upgraded?
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
> >>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>> from
> >>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns
> >>>>>>>>>>>>>>>>>>>>>> calls the
> >>>>>>>>>>>>>>>>>>>>>> Csound
> >>>>>>>>>>>>>>>>>>>>>> library.
> >>>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
> >>>>>>>>>>>>>>>>>>>>>>> "csound"
> >>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>> no
> >>>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
> >>>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
> >>>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output
> >>>>>>>>>>>>>>>>>>>>>>> window it
> >>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says
> >>>>>>>>>>>>>>>>>>>>>>> "command not
> >>>>>>>>>>>>>>>>>>>>>>> found",
> >>>>>>>>>>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX
> >>>>>>>>>>>>>>>>>>>>>>>> installer so
> >>>>>>>>>>>>>>>>>>>>>>>> that
> >>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>> ships
> >>>>>>>>>>>>>>>>>>>>>>>> with
> >>>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>>>> 
> >>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build
> >>>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> over
> >>>>>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release,
> >>>>>>>>>>>>>>>>>>>>>>>>> so
> >>>>>>>>>>>>>>>>>>>>>>>>> that I
> >>>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>>> use
> >>>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> When I do:
> >>>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
> >>>>>>>>>>>>>>>>>>>>>>>>> overwrite
> >>>>>>>>>>>>>>>>>>>>>>>>> when
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form
> >>>>>>>>>>>>>>>>>>>>>>>>> a
> >>>>>>>>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> still
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>>>> was
> >>>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
> >>>>>>>>>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> didn't
> >>>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> and it
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to
> >>>>>>>>>>>>>>>>>>>>>>>>> upgrade
> >>>>>>>>>>>>>>>>>>>>>>>>> this?
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions
> >>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
> >>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>
> >>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>
> >>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
> >>>>>>>>>>> to
> >>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
> >>>>>>>>>>> features can
> >>>>>>>>>>> be posted here
> >>>>>>>>>>
> >>>>>>>>>> Csound mailing list
> >>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>> Send bugs reports to
> >>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>
> >>>>>>>>> Csound mailing list
> >>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>> Send bugs reports to
> >>>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>
> >>>>>>>> Csound mailing list
> >>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>> Send bugs reports to
> >>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>
> >>>>>>> Csound mailing list
> >>>>>>> Csound@listserv.heanet.ie
> >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>> Send bugs reports to
> >>>>>>>         https://github.com/csound/csound/issues
> >>>>>>> Discussions of bugs and features can be posted here
> >>>>>
> >>>>> Csound mailing list
> >>>>> Csound@listserv.heanet.ie
> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>> Send bugs reports to
> >>>>>         https://github.com/csound/csound/issues
> >>>>> Discussions of bugs and features can be posted here
> >>>>
> >>>> Csound mailing list
> >>>> Csound@listserv.heanet.ie
> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>> Send bugs reports to
> >>>>          https://github.com/csound/csound/issues
> >>>> Discussions of bugs and features can be posted here
> >>>
> >>> Csound mailing list
> >>> Csound@listserv.heanet.ie
> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>> Send bugs reports to
> >>>          https://github.com/csound/csound/issues
> >>> Discussions of bugs and features can be posted here
> >>
> >>
> >> Csound mailing list
> >> Csound@listserv.heanet.ie
> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >> Send bugs reports to
> >>        https://github.com/csound/csound/issues
> >> Discussions of bugs and features can be posted here
> >
> >
> > Csound mailing list Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> > https://github.com/csound/csound/issues Discussions of bugs and features can
> > be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> 
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 16:13
FromRory Walsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Too bad, but when did you stop doing that? I'm sure the libraries haven't changed that much over the releases, so perhaps an early version of Csound6 would work? 

On 9 December 2015 at 13:00, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
No, we don’t do that anymore. It all goes into the framework, and they are not usable that way
for developers.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 9 Dec 2015, at 10:58, Rory Walsh <rorywalsh@EAR.IE> wrote:
>
> I think Victor's installer puts the libraries in all the places cmake looks? Install fresh from Victors package and then try running cmake again perhaps?
>
> On 9 December 2015 at 10:52, Kevin Welsh <tgrey1@gmail.com> wrote:
> If that's possible, that sounds like a great shortcut!  Where exactly
> would I be pointing to (keeping in mind the only current installed
> csound version came with cabbage in case it matters)?  And I assume
> that's using: cmake -DCMAKE_LIBRARY_PATH=???
>
> On Wed, Dec 9, 2015 at 5:48 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> > Why not just use all the libraries Victor has packaged in his installer.
> > Just point cmake to those and you won't need to rebuild them all manually?
> >
> > On 9 December 2015 at 10:42, Guillermo Senna <gsenna@gmail.com> wrote:
> >>
> >> I found some posts saying something about update_dyld_shared_cache.
> >>
> >>
> >> On 09/12/15 07:37, Kevin Welsh wrote:
> >>>
> >>> libpng has been installed from a homebrew csound build in the past,
> >>> but this current instance is a manual download of the source, and
> >>> built by hand.
> >>>
> >>> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
> >>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>
> >>>> The problem here seems to be that libpng has been detected by Cmake,
> >>>> otherwise
> >>>> it would not even try to build libvirtual. But then it fails because it
> >>>> cannot find it.
> >>>>
> >>>> For what it’s worth, I have libpng installed in /usr/local/lib and never
> >>>> had problems
> >>>> with it:
> >>>>
> >>>> ligeti:src victor$ ls /usr/local/lib/libpng
> >>>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
> >>>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
> >>>>
> >>>> However, this could be a homebrew issue (I had the impression you are
> >>>> using it). Did you try installing libpng from inside homebrew?
> >>>>
> >>>> Regards
> >>>> ========================
> >>>> Dr Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 9 Dec 2015, at 10:06, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>
> >>>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
> >>>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
> >>>>> failed on lpng.
> >>>>>
> >>>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>
> >>>>>> I'm sorry if that was unclear, those were the commands I used for
> >>>>>> installing libpng.  I don't recall passing any options to cmake when I
> >>>>>> ran it here, probably because I didn't think I was doing it right to
> >>>>>> begin with so I was just sort of messing around.
> >>>>>>
> >>>>>> I just ran "make clean ; cmake . ; make" and came up with the same
> >>>>>> error.
> >>>>>>
> >>>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
> >>>>>> guessing the important one I need out of all of that is
> >>>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
> >>>>>> knowing the default location for my system, all of my other libs will
> >>>>>> then be missing ;)
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
> >>>>>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>>>>
> >>>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to
> >>>>>>> tell Cmake where your libraries are;
> >>>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do
> >>>>>>> a make clean and make again.
> >>>>>>> ========================
> >>>>>>> Dr Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>> Maynooth University,
> >>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>> Tel: 00 353 7086936
> >>>>>>> Fax: 00 353 1 7086952
> >>>>>>>
> >>>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
> >>>>>>>> download, using their cmake instructions (cmake .
> >>>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I
> >>>>>>>> still
> >>>>>>>> get the same error.
> >>>>>>>>
> >>>>>>>> Should libs be installed somewhere else in OSX?
> >>>>>>>>
> >>>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
> >>>>>>>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>>>>>>
> >>>>>>>>> You’re missing libpng in this case.
> >>>>>>>>> ========================
> >>>>>>>>> Dr Victor Lazzarini
> >>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>>>> Maynooth University,
> >>>>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>>>> Tel: 00 353 7086936
> >>>>>>>>> Fax: 00 353 1 7086952
> >>>>>>>>>
> >>>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
> >>>>>>>>>> failed, I assumed any needed libraries should already be installed
> >>>>>>>>>> (including any dev libs) since it has already been built via
> >>>>>>>>>> homebrew
> >>>>>>>>>> on this system, but perhaps not.
> >>>>>>>>>>
> >>>>>>>>>> It failed on:
> >>>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
> >>>>>>>>>> ld: library not found for -lpng
> >>>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to
> >>>>>>>>>> see invocation)
> >>>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
> >>>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
> >>>>>>>>>> make: *** [all] Error 2
> >>>>>>>>>>
> >>>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
> >>>>>>>>>> completely wasting time trying to figure it out from there.
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> You can just build using cmake as you would on any system. Only
> >>>>>>>>>>> you will
> >>>>>>>>>>> have to build any libraries you need too, like libsndfile,
> >>>>>>>>>>> portaudio, etc.
> >>>>>>>>>>>
> >>>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I poked around in the source tree and the only build
> >>>>>>>>>>>> documentation I
> >>>>>>>>>>>> found is specifically for homebrew... is it still broken?  It
> >>>>>>>>>>>> could be
> >>>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
> >>>>>>>>>>>> instructions aren't needed assuming basic familiarity with the
> >>>>>>>>>>>> system
> >>>>>>>>>>>> tools, but I don't know anything about building software in OSX.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Is there a doc or set of instructions I could refer to for help
> >>>>>>>>>>>> getting
> >>>>>>>>>>>> started?
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the
> >>>>>>>>>>>>> newest
> >>>>>>>>>>>>> csound version, however I still have no CLI version.  What
> >>>>>>>>>>>>> would be
> >>>>>>>>>>>>> the best/safest way to continue using the freshest versions
> >>>>>>>>>>>>> with
> >>>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi
> >>>>>>>>>>>>> <stevenyi@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> That is correct.  If the linker path is relative, it will
> >>>>>>>>>>>>>> check local
> >>>>>>>>>>>>>> to the executable, then the local Framework folder, then the
> >>>>>>>>>>>>>> system
> >>>>>>>>>>>>>> Framework folder.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
> >>>>>>>>>>>>>>> environment
> >>>>>>>>>>>>>>> variables set up when trying homebrew.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
> >>>>>>>>>>>>>>>> one.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly
> >>>>>>>>>>>>>>>>> makes
> >>>>>>>>>>>>>>>>> cabbage
> >>>>>>>>>>>>>>>>> report 6.06.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
> >>>>>>>>>>>>>>>>> <stevenyi@gmail.com>
> >>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
> >>>>>>>>>>>>>>>>>> ~/Library/Frameworks
> >>>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
> >>>>>>>>>>>>>>>>>> homebrew
> >>>>>>>>>>>>>>>>>> build
> >>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
> >>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>> won't
> >>>>>>>>>>>>>>>>>> now
> >>>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using
> >>>>>>>>>>>>>>>>>> it at
> >>>>>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>> until I or someone else can look into it.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh
> >>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed
> >>>>>>>>>>>>>>>>>>> that the
> >>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule
> >>>>>>>>>>>>>>>>>>> that out
> >>>>>>>>>>>>>>>>>>> as the
> >>>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
> >>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>> comes with.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file
> >>>>>>>>>>>>>>>>>>> permission or
> >>>>>>>>>>>>>>>>>>> config
> >>>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
> >>>>>>>>>>>>>>>>>>> version...
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
> >>>>>>>>>>>>>>>>>>>> last
> >>>>>>>>>>>>>>>>>>>> version of
> >>>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not
> >>>>>>>>>>>>>>>>>>>> sure where
> >>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>> is
> >>>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
> >>>>>>>>>>>>>>>>>>>> fetching
> >>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>> wrong
> >>>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake
> >>>>>>>>>>>>>>>>>>>> and the
> >>>>>>>>>>>>>>>>>>>> terminal.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
> >>>>>>>>>>>>>>>>>>>>> library
> >>>>>>>>>>>>>>>>>>>>> isn't
> >>>>>>>>>>>>>>>>>>>>> getting upgraded?
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
> >>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>> from
> >>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns
> >>>>>>>>>>>>>>>>>>>>>> calls the
> >>>>>>>>>>>>>>>>>>>>>> Csound
> >>>>>>>>>>>>>>>>>>>>>> library.
> >>>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
> >>>>>>>>>>>>>>>>>>>>>>> "csound"
> >>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>> no
> >>>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
> >>>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
> >>>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output
> >>>>>>>>>>>>>>>>>>>>>>> window it
> >>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says
> >>>>>>>>>>>>>>>>>>>>>>> "command not
> >>>>>>>>>>>>>>>>>>>>>>> found",
> >>>>>>>>>>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX
> >>>>>>>>>>>>>>>>>>>>>>>> installer so
> >>>>>>>>>>>>>>>>>>>>>>>> that
> >>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>> ships
> >>>>>>>>>>>>>>>>>>>>>>>> with
> >>>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build
> >>>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> over
> >>>>>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release,
> >>>>>>>>>>>>>>>>>>>>>>>>> so
> >>>>>>>>>>>>>>>>>>>>>>>>> that I
> >>>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>>> use
> >>>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> When I do:
> >>>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
> >>>>>>>>>>>>>>>>>>>>>>>>> overwrite
> >>>>>>>>>>>>>>>>>>>>>>>>> when
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form
> >>>>>>>>>>>>>>>>>>>>>>>>> a
> >>>>>>>>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> still
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>>>> was
> >>>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
> >>>>>>>>>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> didn't
> >>>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> and it
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to
> >>>>>>>>>>>>>>>>>>>>>>>>> upgrade
> >>>>>>>>>>>>>>>>>>>>>>>>> this?
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions
> >>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
> >>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>
> >>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>
> >>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
> >>>>>>>>>>> to
> >>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
> >>>>>>>>>>> features can
> >>>>>>>>>>> be posted here
> >>>>>>>>>>
> >>>>>>>>>> Csound mailing list
> >>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>> Send bugs reports to
> >>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>
> >>>>>>>>> Csound mailing list
> >>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>> Send bugs reports to
> >>>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>
> >>>>>>>> Csound mailing list
> >>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>> Send bugs reports to
> >>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>
> >>>>>>> Csound mailing list
> >>>>>>> Csound@listserv.heanet.ie
> >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>> Send bugs reports to
> >>>>>>>         https://github.com/csound/csound/issues
> >>>>>>> Discussions of bugs and features can be posted here
> >>>>>
> >>>>> Csound mailing list
> >>>>> Csound@listserv.heanet.ie
> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>> Send bugs reports to
> >>>>>         https://github.com/csound/csound/issues
> >>>>> Discussions of bugs and features can be posted here
> >>>>
> >>>> Csound mailing list
> >>>> Csound@listserv.heanet.ie
> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>> Send bugs reports to
> >>>>          https://github.com/csound/csound/issues
> >>>> Discussions of bugs and features can be posted here
> >>>
> >>> Csound mailing list
> >>> Csound@listserv.heanet.ie
> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>> Send bugs reports to
> >>>          https://github.com/csound/csound/issues
> >>> Discussions of bugs and features can be posted here
> >>
> >>
> >> Csound mailing list
> >> Csound@listserv.heanet.ie
> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >> Send bugs reports to
> >>        https://github.com/csound/csound/issues
> >> Discussions of bugs and features can be posted here
> >
> >
> > Csound mailing list Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> > https://github.com/csound/csound/issues Discussions of bugs and features can
> > be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 16:35
FromVictor Lazzarini
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Sometime ago, maybe for 6.04 or .03

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 9 Dec 2015, at 16:13, Rory Walsh <rorywalsh@EAR.IE> wrote:imr

Too bad, but when did you stop doing that? I'm sure the libraries haven't changed that much over the releases, so perhaps an early version of Csound6 would work? 

On 9 December 2015 at 13:00, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
No, we don’t do that anymore. It all goes into the framework, and they are not usable that way
for developers.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 9 Dec 2015, at 10:58, Rory Walsh <rorywalsh@EAR.IE> wrote:
>
> I think Victor's installer puts the libraries in all the places cmake looks? Install fresh from Victors package and then try running cmake again perhaps?
>
> On 9 December 2015 at 10:52, Kevin Welsh <tgrey1@gmail.com> wrote:
> If that's possible, that sounds like a great shortcut!  Where exactly
> would I be pointing to (keeping in mind the only current installed
> csound version came with cabbage in case it matters)?  And I assume
> that's using: cmake -DCMAKE_LIBRARY_PATH=???
>
> On Wed, Dec 9, 2015 at 5:48 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> > Why not just use all the libraries Victor has packaged in his installer.
> > Just point cmake to those and you won't need to rebuild them all manually?
> >
> > On 9 December 2015 at 10:42, Guillermo Senna <gsenna@gmail.com> wrote:
> >>
> >> I found some posts saying something about update_dyld_shared_cache.
> >>
> >>
> >> On 09/12/15 07:37, Kevin Welsh wrote:
> >>>
> >>> libpng has been installed from a homebrew csound build in the past,
> >>> but this current instance is a manual download of the source, and
> >>> built by hand.
> >>>
> >>> On Wed, Dec 9, 2015 at 5:32 AM, Victor Lazzarini
> >>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>
> >>>> The problem here seems to be that libpng has been detected by Cmake,
> >>>> otherwise
> >>>> it would not even try to build libvirtual. But then it fails because it
> >>>> cannot find it.
> >>>>
> >>>> For what it’s worth, I have libpng installed in /usr/local/lib and never
> >>>> had problems
> >>>> with it:
> >>>>
> >>>> ligeti:src victor$ ls /usr/local/lib/libpng
> >>>> libpng.a           libpng.la          libpng16.16.dylib  libpng16.dylib
> >>>> libpng.dylib       libpng15.15.dylib  libpng16.a         libpng16.la
> >>>>
> >>>> However, this could be a homebrew issue (I had the impression you are
> >>>> using it). Did you try installing libpng from inside homebrew?
> >>>>
> >>>> Regards
> >>>> ========================
> >>>> Dr Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 9 Dec 2015, at 10:06, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>
> >>>>> Ok, correction... neither "cmake -DCMAKE_LIBRARY_PATH=/usr/local" nor
> >>>>> "cmake -DCMAKE_LIBRARY_PATH=/usr/local/lib" did the trick, it still
> >>>>> failed on lpng.
> >>>>>
> >>>>> On Wed, Dec 9, 2015 at 5:02 AM, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>
> >>>>>> I'm sorry if that was unclear, those were the commands I used for
> >>>>>> installing libpng.  I don't recall passing any options to cmake when I
> >>>>>> ran it here, probably because I didn't think I was doing it right to
> >>>>>> begin with so I was just sort of messing around.
> >>>>>>
> >>>>>> I just ran "make clean ; cmake . ; make" and came up with the same
> >>>>>> error.
> >>>>>>
> >>>>>> I'll take a look at the cmake variables doc you just sent too.  I'm
> >>>>>> guessing the important one I need out of all of that is
> >>>>>> "CMAKE_LIBRARY_PATH", however I still think if I override that without
> >>>>>> knowing the default location for my system, all of my other libs will
> >>>>>> then be missing ;)
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Dec 9, 2015 at 4:53 AM, Victor Lazzarini
> >>>>>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>>>>
> >>>>>>> CMAKE_INSTALL_PREFIX only affects Csound installation. You need to
> >>>>>>> tell Cmake where your libraries are;
> >>>>>>> I am not quite sure why Cmake is not picking it correctly. Try to do
> >>>>>>> a make clean and make again.
> >>>>>>> ========================
> >>>>>>> Dr Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>> Maynooth University,
> >>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>> Tel: 00 353 7086936
> >>>>>>> Fax: 00 353 1 7086952
> >>>>>>>
> >>>>>>>> On 9 Dec 2015, at 09:42, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Thanks Victor!  I have just installed libpng from a fresh source
> >>>>>>>> download, using their cmake instructions (cmake .
> >>>>>>>> -DCMAKE_INSTALL_PREFIX=/usr/local ; make ; make install), but I
> >>>>>>>> still
> >>>>>>>> get the same error.
> >>>>>>>>
> >>>>>>>> Should libs be installed somewhere else in OSX?
> >>>>>>>>
> >>>>>>>> On Wed, Dec 9, 2015 at 4:10 AM, Victor Lazzarini
> >>>>>>>> <Victor.Lazzarini@nuim.ie> wrote:
> >>>>>>>>>
> >>>>>>>>> You’re missing libpng in this case.
> >>>>>>>>> ========================
> >>>>>>>>> Dr Victor Lazzarini
> >>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>>>> Maynooth University,
> >>>>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>>>> Tel: 00 353 7086936
> >>>>>>>>> Fax: 00 353 1 7086952
> >>>>>>>>>
> >>>>>>>>>> On 9 Dec 2015, at 08:19, Kevin Welsh <tgrey1@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thanks Rory!  Well, that does sound easy.  I had tried that and it
> >>>>>>>>>> failed, I assumed any needed libraries should already be installed
> >>>>>>>>>> (including any dev libs) since it has already been built via
> >>>>>>>>>> homebrew
> >>>>>>>>>> on this system, but perhaps not.
> >>>>>>>>>>
> >>>>>>>>>> It failed on:
> >>>>>>>>>> [ 66%] Linking CXX shared library ../libvirtual.dylib
> >>>>>>>>>> ld: library not found for -lpng
> >>>>>>>>>> clang: error: linker command failed with exit code 1 (use -v to
> >>>>>>>>>> see invocation)
> >>>>>>>>>> make[2]: *** [libvirtual.dylib] Error 1
> >>>>>>>>>> make[1]: *** [InOut/CMakeFiles/virtual.dir/all] Error 2
> >>>>>>>>>> make: *** [all] Error 2
> >>>>>>>>>>
> >>>>>>>>>> At least now that I know this *SHOULD* work I won't feel like I'm
> >>>>>>>>>> completely wasting time trying to figure it out from there.
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Dec 9, 2015 at 3:10 AM, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> You can just build using cmake as you would on any system. Only
> >>>>>>>>>>> you will
> >>>>>>>>>>> have to build any libraries you need too, like libsndfile,
> >>>>>>>>>>> portaudio, etc.
> >>>>>>>>>>>
> >>>>>>>>>>> On 9 Dec 2015 02:33, "Kevin Welsh" <tgrey1@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I poked around in the source tree and the only build
> >>>>>>>>>>>> documentation I
> >>>>>>>>>>>> found is specifically for homebrew... is it still broken?  It
> >>>>>>>>>>>> could be
> >>>>>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
> >>>>>>>>>>>> instructions aren't needed assuming basic familiarity with the
> >>>>>>>>>>>> system
> >>>>>>>>>>>> tools, but I don't know anything about building software in OSX.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Is there a doc or set of instructions I could refer to for help
> >>>>>>>>>>>> getting
> >>>>>>>>>>>> started?
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh <tgrey1@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks everyone, this did get my cabbage working with the
> >>>>>>>>>>>>> newest
> >>>>>>>>>>>>> csound version, however I still have no CLI version.  What
> >>>>>>>>>>>>> would be
> >>>>>>>>>>>>> the best/safest way to continue using the freshest versions
> >>>>>>>>>>>>> with
> >>>>>>>>>>>>> cabbage, but maintaining CLI functionality too?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi
> >>>>>>>>>>>>> <stevenyi@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> That is correct.  If the linker path is relative, it will
> >>>>>>>>>>>>>> check local
> >>>>>>>>>>>>>> to the executable, then the local Framework folder, then the
> >>>>>>>>>>>>>> system
> >>>>>>>>>>>>>> Framework folder.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> That doesn't seem write though. Perhaps there were some
> >>>>>>>>>>>>>>> environment
> >>>>>>>>>>>>>>> variables set up when trying homebrew.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I guess OSX checks the user Library folder before the system
> >>>>>>>>>>>>>>>> one.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly
> >>>>>>>>>>>>>>>>> makes
> >>>>>>>>>>>>>>>>> cabbage
> >>>>>>>>>>>>>>>>> report 6.06.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi
> >>>>>>>>>>>>>>>>> <stevenyi@gmail.com>
> >>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Check that there isn't a CsoundLib64.framework in
> >>>>>>>>>>>>>>>>>> ~/Library/Frameworks
> >>>>>>>>>>>>>>>>>> folder. If so, try moving or deleting that. The current
> >>>>>>>>>>>>>>>>>> homebrew
> >>>>>>>>>>>>>>>>>> build
> >>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>> Csound has problems. I have not found time to look into it
> >>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>> won't
> >>>>>>>>>>>>>>>>>> now
> >>>>>>>>>>>>>>>>>> until I get back home in December.  I recommend not using
> >>>>>>>>>>>>>>>>>> it at
> >>>>>>>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>> until I or someone else can look into it.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh
> >>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> But I uninstalled the homebrew version, and confirmed
> >>>>>>>>>>>>>>>>>>> that the
> >>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>> version of csound was gone too... I was trying to rule
> >>>>>>>>>>>>>>>>>>> that out
> >>>>>>>>>>>>>>>>>>> as the
> >>>>>>>>>>>>>>>>>>> problem, just running the newest cabbage release and the
> >>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>> comes with.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> My thought is homebrew somehow messed up a file
> >>>>>>>>>>>>>>>>>>> permission or
> >>>>>>>>>>>>>>>>>>> config
> >>>>>>>>>>>>>>>>>>> for loading the library that has left it running a stale
> >>>>>>>>>>>>>>>>>>> version...
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> I'm not sure what's going on because I'm pretty sure the
> >>>>>>>>>>>>>>>>>>>> last
> >>>>>>>>>>>>>>>>>>>> version of
> >>>>>>>>>>>>>>>>>>>> Cabbage you installed on OSX installed 6.05, I'm not
> >>>>>>>>>>>>>>>>>>>> sure where
> >>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>> is
> >>>>>>>>>>>>>>>>>>>> coming from? I have no idea how homebrew works, is it
> >>>>>>>>>>>>>>>>>>>> fetching
> >>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>> wrong
> >>>>>>>>>>>>>>>>>>>> package? I've only ever built Csound on OSX using cmake
> >>>>>>>>>>>>>>>>>>>> and the
> >>>>>>>>>>>>>>>>>>>> terminal.
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 14:29, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> So I'm guessing this means for some reason my csound
> >>>>>>>>>>>>>>>>>>>>> library
> >>>>>>>>>>>>>>>>>>>>> isn't
> >>>>>>>>>>>>>>>>>>>>> getting upgraded?
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Cabbage links to the Csound library whereas running
> >>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>> from
> >>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>> line calls the csound application, which in turns
> >>>>>>>>>>>>>>>>>>>>>> calls the
> >>>>>>>>>>>>>>>>>>>>>> Csound
> >>>>>>>>>>>>>>>>>>>>>> library.
> >>>>>>>>>>>>>>>>>>>>>> Cabbage only needs to underlying libraries.
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 12:38, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Well, then now I'm really confused.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> I uninstalled the homebrew version, confirmed that
> >>>>>>>>>>>>>>>>>>>>>>> "csound"
> >>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>> no
> >>>>>>>>>>>>>>>>>>>>>>> longer worked at the command line.
> >>>>>>>>>>>>>>>>>>>>>>> I installed a fresh download from
> >>>>>>>>>>>>>>>>>>>>>>> http://www.cabbageaudio.com/download/
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Cabbage appears to work fine, but in the output
> >>>>>>>>>>>>>>>>>>>>>>> window it
> >>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>> 6.04
> >>>>>>>>>>>>>>>>>>>>>>> still... and from a command line it still says
> >>>>>>>>>>>>>>>>>>>>>>> "command not
> >>>>>>>>>>>>>>>>>>>>>>> found",
> >>>>>>>>>>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>>>>>>>>> if I have no csound at all.
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh
> >>>>>>>>>>>>>>>>>>>>>>> <rorywalsh@ear.ie>
> >>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> For what it's worth, I just updated the OSX
> >>>>>>>>>>>>>>>>>>>>>>>> installer so
> >>>>>>>>>>>>>>>>>>>>>>>> that
> >>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>> ships
> >>>>>>>>>>>>>>>>>>>>>>>> with
> >>>>>>>>>>>>>>>>>>>>>>>> the latest version of Csound, i.e., 6.06.
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> On 17 November 2015 at 03:08, Kevin Welsh
> >>>>>>>>>>>>>>>>>>>>>>>> <tgrey1@gmail.com>
> >>>>>>>>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> My goal is to use homebrew to install a fresh build
> >>>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> over
> >>>>>>>>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>>>>>>>> one packaged with the most recent cabbage release,
> >>>>>>>>>>>>>>>>>>>>>>>>> so
> >>>>>>>>>>>>>>>>>>>>>>>>> that I
> >>>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>>> use
> >>>>>>>>>>>>>>>>>>>>>>>>> the new csound features from within cabbage.
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> When I do:
> >>>>>>>>>>>>>>>>>>>>>>>>> brew install -HEAD csound
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> it appears to fetch and build 6.05, and I forced an
> >>>>>>>>>>>>>>>>>>>>>>>>> overwrite
> >>>>>>>>>>>>>>>>>>>>>>>>> when
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> linked the first time.  But when I run csound form
> >>>>>>>>>>>>>>>>>>>>>>>>> a
> >>>>>>>>>>>>>>>>>>>>>>>>> console
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> still
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> I tried uninstalling via homebrew, confirming my
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> command
> >>>>>>>>>>>>>>>>>>>>>>>>> was
> >>>>>>>>>>>>>>>>>>>>>>>>> gone, and rebuilding via the homebrew command, this
> >>>>>>>>>>>>>>>>>>>>>>>>> time
> >>>>>>>>>>>>>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>>>>>>>>>>> didn't
> >>>>>>>>>>>>>>>>>>>>>>>>> require forcing the overwrite, but I still run
> >>>>>>>>>>>>>>>>>>>>>>>>> csound
> >>>>>>>>>>>>>>>>>>>>>>>>> and it
> >>>>>>>>>>>>>>>>>>>>>>>>> reports:
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound version 6.04 (double samples) Feb 26 2015
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> What am I doing wrong or forgetting to do to
> >>>>>>>>>>>>>>>>>>>>>>>>> upgrade
> >>>>>>>>>>>>>>>>>>>>>>>>> this?
> >>>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions
> >>>>>>>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send
> >>>>>>>>>>>>>>>>>>>> bugs
> >>>>>>>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>>>> features
> >>>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>>>>> reports
> >>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of
> >>>>>>>>>>>>>>>>>> bugs and
> >>>>>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
> >>>>>>>>>>>>>>> reports to
> >>>>>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs
> >>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>> features can
> >>>>>>>>>>>>>>> be posted here
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>>
> >>>>>>>>>>>> Csound mailing list
> >>>>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>>>> Send bugs reports to
> >>>>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>>>
> >>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
> >>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
> >>>>>>>>>>> to
> >>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and
> >>>>>>>>>>> features can
> >>>>>>>>>>> be posted here
> >>>>>>>>>>
> >>>>>>>>>> Csound mailing list
> >>>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>>> Send bugs reports to
> >>>>>>>>>>       https://github.com/csound/csound/issues
> >>>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>>
> >>>>>>>>> Csound mailing list
> >>>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>>> Send bugs reports to
> >>>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>>
> >>>>>>>> Csound mailing list
> >>>>>>>> Csound@listserv.heanet.ie
> >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>>> Send bugs reports to
> >>>>>>>>        https://github.com/csound/csound/issues
> >>>>>>>> Discussions of bugs and features can be posted here
> >>>>>>>
> >>>>>>> Csound mailing list
> >>>>>>> Csound@listserv.heanet.ie
> >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>>>> Send bugs reports to
> >>>>>>>         https://github.com/csound/csound/issues
> >>>>>>> Discussions of bugs and features can be posted here
> >>>>>
> >>>>> Csound mailing list
> >>>>> Csound@listserv.heanet.ie
> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>>> Send bugs reports to
> >>>>>         https://github.com/csound/csound/issues
> >>>>> Discussions of bugs and features can be posted here
> >>>>
> >>>> Csound mailing list
> >>>> Csound@listserv.heanet.ie
> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>> Send bugs reports to
> >>>>          https://github.com/csound/csound/issues
> >>>> Discussions of bugs and features can be posted here
> >>>
> >>> Csound mailing list
> >>> Csound@listserv.heanet.ie
> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>> Send bugs reports to
> >>>          https://github.com/csound/csound/issues
> >>> Discussions of bugs and features can be posted here
> >>
> >>
> >> Csound mailing list
> >> Csound@listserv.heanet.ie
> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >> Send bugs reports to
> >>        https://github.com/csound/csound/issues
> >> Discussions of bugs and features can be posted here
> >
> >
> > Csound mailing list Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> > https://github.com/csound/csound/issues Discussions of bugs and features can
> > be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-09 21:22
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I have not had time to look into the homebrew issue and no one else
has contributed time to look into it. It is still broken. For my own
timeline, I was planning to look at it as soon as I have an
opportunity to wipe out and redo my Mac, which may take a while
unfortunately.

On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
> I poked around in the source tree and the only build documentation I
> found is specifically for homebrew... is it still broken?  It could be
> I'm looking in the wrong place, or maybe it's so easy that
> instructions aren't needed assuming basic familiarity with the system
> tools, but I don't know anything about building software in OSX.
>
> Is there a doc or set of instructions I could refer to for help getting started?
>
> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>> Thanks everyone, this did get my cabbage working with the newest
>> csound version, however I still have no CLI version.  What would be
>> the best/safest way to continue using the freshest versions with
>> cabbage, but maintaining CLI functionality too?
>>
>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>> That is correct.  If the linker path is relative, it will check local
>>> to the executable, then the local Framework folder, then the system
>>> Framework folder.
>>>
>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>> That doesn't seem write though. Perhaps there were some environment
>>>> variables set up when trying homebrew.
>>>>
>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>
>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>
>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>
>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>> report 6.06.
>>>>>>
>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>> > of
>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>> > now
>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>> > time
>>>>>> > until I or someone else can look into it.
>>>>>> >
>>>>>> >
>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>> >>
>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>> >> comes with.
>>>>>> >>
>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>> >> for loading the library that has left it running a stale version...
>>>>>> >>
>>>>>> >>
>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>> >> > version of
>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>> >> > is
>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>> >> > wrong
>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>> >> > terminal.
>>>>>> >> >
>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>> >> >>
>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>> >> >> getting upgraded?
>>>>>> >> >>
>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>> >> >> wrote:
>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>> >> >> > the
>>>>>> >> >> > command
>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>> >> >> > Csound
>>>>>> >> >> > library.
>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>> >> >> >
>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>> >> >> > wrote:
>>>>>> >> >> >>
>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>> >> >> >>
>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>> >> >> >> command
>>>>>> >> >> >> no
>>>>>> >> >> >> longer worked at the command line.
>>>>>> >> >> >> I installed a fresh download from
>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>> >> >> >>
>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>> >> >> >> reports
>>>>>> >> >> >> 6.04
>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>> >> >> >> found",
>>>>>> >> >> >> as
>>>>>> >> >> >> if I have no csound at all.
>>>>>> >> >> >>
>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>> >> >> >> wrote:
>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>> >> >> >> > it
>>>>>> >> >> >> > ships
>>>>>> >> >> >> > with
>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>> >> >> >> >
>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>> >> >> >> > wrote:
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>> >> >> >> >> over
>>>>>> >> >> >> >> the
>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>> >> >> >> >> can
>>>>>> >> >> >> >> use
>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> When I do:
>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>> >> >> >> >> when
>>>>>> >> >> >> >> it
>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>> >> >> >> >> it
>>>>>> >> >> >> >> still
>>>>>> >> >> >> >> reports:
>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>> >> >> >> >> command
>>>>>> >> >> >> >> was
>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>> >> >> >> >> didn't
>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>> >> >> >> >> reports:
>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>> >> >> >> >>
>>>>>> >> >> >> >> Csound mailing list
>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> >> >> >> >> Send bugs reports to
>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>> >> >> >> >
>>>>>> >> >> >> >
>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>> >> >> >> > reports
>>>>>> >> >> >> > to
>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>> >> >> >> > and
>>>>>> >> >> >> > features
>>>>>> >> >> >> > can
>>>>>> >> >> >> > be posted here
>>>>>> >> >> >>
>>>>>> >> >> >> Csound mailing list
>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> >> >> >> Send bugs reports to
>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>> >> >> >
>>>>>> >> >> >
>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>> >> >> > to
>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>> >> >> > features
>>>>>> >> >> > can
>>>>>> >> >> > be posted here
>>>>>> >> >>
>>>>>> >> >> Csound mailing list
>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> >> >> Send bugs reports to
>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>> >> >
>>>>>> >> >
>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>> >> > features
>>>>>> >> > can
>>>>>> >> > be posted here
>>>>>> >>
>>>>>> >> Csound mailing list
>>>>>> >> Csound@listserv.heanet.ie
>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> >> Send bugs reports to
>>>>>> >>         https://github.com/csound/csound/issues
>>>>>> >> Discussions of bugs and features can be posted here
>>>>>> >
>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>> > features can
>>>>>> > be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>>
>>>>
>>>> Csound mailing list Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>> be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-09 22:43
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks Guillermo, that looks like what I was looking for... but
unfortunately it still didn't do the trick.

I ran update_dyld_shared_cache and rebooted just to be safe, still
fails in the same spot, looking for lpng.

On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
> I have not had time to look into the homebrew issue and no one else
> has contributed time to look into it. It is still broken. For my own
> timeline, I was planning to look at it as soon as I have an
> opportunity to wipe out and redo my Mac, which may take a while
> unfortunately.
>
> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>> I poked around in the source tree and the only build documentation I
>> found is specifically for homebrew... is it still broken?  It could be
>> I'm looking in the wrong place, or maybe it's so easy that
>> instructions aren't needed assuming basic familiarity with the system
>> tools, but I don't know anything about building software in OSX.
>>
>> Is there a doc or set of instructions I could refer to for help getting started?
>>
>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>> Thanks everyone, this did get my cabbage working with the newest
>>> csound version, however I still have no CLI version.  What would be
>>> the best/safest way to continue using the freshest versions with
>>> cabbage, but maintaining CLI functionality too?
>>>
>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>> That is correct.  If the linker path is relative, it will check local
>>>> to the executable, then the local Framework folder, then the system
>>>> Framework folder.
>>>>
>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>> variables set up when trying homebrew.
>>>>>
>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>
>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>
>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>
>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>> report 6.06.
>>>>>>>
>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>> > of
>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>> > now
>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>> > time
>>>>>>> > until I or someone else can look into it.
>>>>>>> >
>>>>>>> >
>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>> >>
>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>> >> comes with.
>>>>>>> >>
>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>> >> > version of
>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>> >> > is
>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>> >> > wrong
>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>> >> > terminal.
>>>>>>> >> >
>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>> >> >>
>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>> >> >> getting upgraded?
>>>>>>> >> >>
>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>> >> >> wrote:
>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>> >> >> > the
>>>>>>> >> >> > command
>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>> >> >> > Csound
>>>>>>> >> >> > library.
>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>> >> >> >
>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>> >> >> > wrote:
>>>>>>> >> >> >>
>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>> >> >> >>
>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>> >> >> >> command
>>>>>>> >> >> >> no
>>>>>>> >> >> >> longer worked at the command line.
>>>>>>> >> >> >> I installed a fresh download from
>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>> >> >> >>
>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>> >> >> >> reports
>>>>>>> >> >> >> 6.04
>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>> >> >> >> found",
>>>>>>> >> >> >> as
>>>>>>> >> >> >> if I have no csound at all.
>>>>>>> >> >> >>
>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>> >> >> >> wrote:
>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>> >> >> >> > it
>>>>>>> >> >> >> > ships
>>>>>>> >> >> >> > with
>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>> >> >> >> >
>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>> >> >> >> > wrote:
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>> >> >> >> >> over
>>>>>>> >> >> >> >> the
>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>> >> >> >> >> can
>>>>>>> >> >> >> >> use
>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> When I do:
>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>> >> >> >> >> when
>>>>>>> >> >> >> >> it
>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>> >> >> >> >> it
>>>>>>> >> >> >> >> still
>>>>>>> >> >> >> >> reports:
>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>> >> >> >> >> command
>>>>>>> >> >> >> >> was
>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>> >> >> >> >> didn't
>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>> >> >> >> >> reports:
>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>> >> >> >> >>
>>>>>>> >> >> >> >> Csound mailing list
>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>> >> >> >> >
>>>>>>> >> >> >> >
>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>> >> >> >> > reports
>>>>>>> >> >> >> > to
>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>> >> >> >> > and
>>>>>>> >> >> >> > features
>>>>>>> >> >> >> > can
>>>>>>> >> >> >> > be posted here
>>>>>>> >> >> >>
>>>>>>> >> >> >> Csound mailing list
>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> >> >> >> Send bugs reports to
>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>> >> >> >
>>>>>>> >> >> >
>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>> >> >> > to
>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>> >> >> > features
>>>>>>> >> >> > can
>>>>>>> >> >> > be posted here
>>>>>>> >> >>
>>>>>>> >> >> Csound mailing list
>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> >> >> Send bugs reports to
>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>> >> > features
>>>>>>> >> > can
>>>>>>> >> > be posted here
>>>>>>> >>
>>>>>>> >> Csound mailing list
>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> >> Send bugs reports to
>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>> >
>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>> > features can
>>>>>>> > be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>>
>>>>>
>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>> be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-10 00:22
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Some things to try:

1. In my Custom.cmake, I have:

list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")

Maybe adding something like this or setting via commandline my help.

2. In your build directory, you can modify CMakeCache.txt and try
either deleting the PNG related entries or setting them manually.  I
have these:

//Path to a library.
PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib

//Path to a file.
PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include



On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
> Thanks Guillermo, that looks like what I was looking for... but
> unfortunately it still didn't do the trick.
>
> I ran update_dyld_shared_cache and rebooted just to be safe, still
> fails in the same spot, looking for lpng.
>
> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>> I have not had time to look into the homebrew issue and no one else
>> has contributed time to look into it. It is still broken. For my own
>> timeline, I was planning to look at it as soon as I have an
>> opportunity to wipe out and redo my Mac, which may take a while
>> unfortunately.
>>
>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>> I poked around in the source tree and the only build documentation I
>>> found is specifically for homebrew... is it still broken?  It could be
>>> I'm looking in the wrong place, or maybe it's so easy that
>>> instructions aren't needed assuming basic familiarity with the system
>>> tools, but I don't know anything about building software in OSX.
>>>
>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>
>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>> Thanks everyone, this did get my cabbage working with the newest
>>>> csound version, however I still have no CLI version.  What would be
>>>> the best/safest way to continue using the freshest versions with
>>>> cabbage, but maintaining CLI functionality too?
>>>>
>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>> That is correct.  If the linker path is relative, it will check local
>>>>> to the executable, then the local Framework folder, then the system
>>>>> Framework folder.
>>>>>
>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>> variables set up when trying homebrew.
>>>>>>
>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>
>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>
>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>
>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>> report 6.06.
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>> > of
>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>> > now
>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>> > time
>>>>>>>> > until I or someone else can look into it.
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>> >>
>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>> >> comes with.
>>>>>>>> >>
>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>> >> > version of
>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>> >> > is
>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>> >> > wrong
>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>> >> > terminal.
>>>>>>>> >> >
>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>> >> >>
>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>> >> >> getting upgraded?
>>>>>>>> >> >>
>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>> >> >> wrote:
>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>> >> >> > the
>>>>>>>> >> >> > command
>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>> >> >> > Csound
>>>>>>>> >> >> > library.
>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>> >> >> >
>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>> >> >> > wrote:
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>> >> >> >> command
>>>>>>>> >> >> >> no
>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>> >> >> >> reports
>>>>>>>> >> >> >> 6.04
>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>> >> >> >> found",
>>>>>>>> >> >> >> as
>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>> >> >> >> wrote:
>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>> >> >> >> > it
>>>>>>>> >> >> >> > ships
>>>>>>>> >> >> >> > with
>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>> >> >> >> >
>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>> >> >> >> > wrote:
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>> >> >> >> >> over
>>>>>>>> >> >> >> >> the
>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>> >> >> >> >> can
>>>>>>>> >> >> >> >> use
>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> When I do:
>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>> >> >> >> >> when
>>>>>>>> >> >> >> >> it
>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>> >> >> >> >> it
>>>>>>>> >> >> >> >> still
>>>>>>>> >> >> >> >> reports:
>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>> >> >> >> >> command
>>>>>>>> >> >> >> >> was
>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>> >> >> >> >> didn't
>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>> >> >> >> >> reports:
>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>> >> >> >> >>
>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>> >> >> >> >
>>>>>>>> >> >> >> >
>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>> >> >> >> > reports
>>>>>>>> >> >> >> > to
>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>> >> >> >> > and
>>>>>>>> >> >> >> > features
>>>>>>>> >> >> >> > can
>>>>>>>> >> >> >> > be posted here
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> Csound mailing list
>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>> >> >> >
>>>>>>>> >> >> >
>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>> >> >> > to
>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>> >> >> > features
>>>>>>>> >> >> > can
>>>>>>>> >> >> > be posted here
>>>>>>>> >> >>
>>>>>>>> >> >> Csound mailing list
>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> >> >> Send bugs reports to
>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>> >> >
>>>>>>>> >> >
>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>> >> > features
>>>>>>>> >> > can
>>>>>>>> >> > be posted here
>>>>>>>> >>
>>>>>>>> >> Csound mailing list
>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> >> Send bugs reports to
>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>> >
>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>> > features can
>>>>>>>> > be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>> be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-10 00:59
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks for the Suggestions Steven, but still no luck.

Just to make sure I didn't do the first suggestion wrong, Custom.cmake
was an empty file, I presume Custom.cmake.ex was an example and not to
be used here.  Those 3 lines are now the *ONLY* lines in the
Custom.cmake file.  I tried building this way first, it still failed.

Then I edited CMakeCache.txt, changing these lines to read:
PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
and
PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include

I did another "make clean", followed by a "cmake .", checked to make
sure my changes were still in the file, and then ran make.  Still no
luck, still failing with the same error message.

On Wed, Dec 9, 2015 at 7:22 PM, Steven Yi  wrote:
> Some things to try:
>
> 1. In my Custom.cmake, I have:
>
> list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")
>
> Maybe adding something like this or setting via commandline my help.
>
> 2. In your build directory, you can modify CMakeCache.txt and try
> either deleting the PNG related entries or setting them manually.  I
> have these:
>
> //Path to a library.
> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>
> //Path to a file.
> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>
>
>
> On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
>> Thanks Guillermo, that looks like what I was looking for... but
>> unfortunately it still didn't do the trick.
>>
>> I ran update_dyld_shared_cache and rebooted just to be safe, still
>> fails in the same spot, looking for lpng.
>>
>> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>>> I have not had time to look into the homebrew issue and no one else
>>> has contributed time to look into it. It is still broken. For my own
>>> timeline, I was planning to look at it as soon as I have an
>>> opportunity to wipe out and redo my Mac, which may take a while
>>> unfortunately.
>>>
>>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>>> I poked around in the source tree and the only build documentation I
>>>> found is specifically for homebrew... is it still broken?  It could be
>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>> instructions aren't needed assuming basic familiarity with the system
>>>> tools, but I don't know anything about building software in OSX.
>>>>
>>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>>
>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>> csound version, however I still have no CLI version.  What would be
>>>>> the best/safest way to continue using the freshest versions with
>>>>> cabbage, but maintaining CLI functionality too?
>>>>>
>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>> to the executable, then the local Framework folder, then the system
>>>>>> Framework folder.
>>>>>>
>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>> variables set up when trying homebrew.
>>>>>>>
>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>
>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>
>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>
>>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>>> report 6.06.
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>>> > of
>>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>>> > now
>>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>>> > time
>>>>>>>>> > until I or someone else can look into it.
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>>> >>
>>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>>> >> comes with.
>>>>>>>>> >>
>>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>> >> > version of
>>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>>> >> > is
>>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>>> >> > wrong
>>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>> >> > terminal.
>>>>>>>>> >> >
>>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>>> >> >>
>>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>>> >> >> getting upgraded?
>>>>>>>>> >> >>
>>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>> >> >> wrote:
>>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>>> >> >> > the
>>>>>>>>> >> >> > command
>>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>>> >> >> > Csound
>>>>>>>>> >> >> > library.
>>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>> >> >> > wrote:
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>> >> >> >> command
>>>>>>>>> >> >> >> no
>>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>>> >> >> >> reports
>>>>>>>>> >> >> >> 6.04
>>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>>> >> >> >> found",
>>>>>>>>> >> >> >> as
>>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>>> >> >> >> wrote:
>>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>>> >> >> >> > it
>>>>>>>>> >> >> >> > ships
>>>>>>>>> >> >> >> > with
>>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>>> >> >> >> >
>>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>>> >> >> >> > wrote:
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>>> >> >> >> >> over
>>>>>>>>> >> >> >> >> the
>>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>>> >> >> >> >> can
>>>>>>>>> >> >> >> >> use
>>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> When I do:
>>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>>> >> >> >> >> when
>>>>>>>>> >> >> >> >> it
>>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>>> >> >> >> >> it
>>>>>>>>> >> >> >> >> still
>>>>>>>>> >> >> >> >> reports:
>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>> >> >> >> >> command
>>>>>>>>> >> >> >> >> was
>>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>>> >> >> >> >> didn't
>>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>>> >> >> >> >> reports:
>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>>> >> >> >> >>
>>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>> >> >> >> >
>>>>>>>>> >> >> >> >
>>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>> >> >> >> > reports
>>>>>>>>> >> >> >> > to
>>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>> >> >> >> > and
>>>>>>>>> >> >> >> > features
>>>>>>>>> >> >> >> > can
>>>>>>>>> >> >> >> > be posted here
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> Csound mailing list
>>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>> >> >> >
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>> >> >> > to
>>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> >> >> > features
>>>>>>>>> >> >> > can
>>>>>>>>> >> >> > be posted here
>>>>>>>>> >> >>
>>>>>>>>> >> >> Csound mailing list
>>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> >> >> Send bugs reports to
>>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>>> >> >
>>>>>>>>> >> >
>>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> >> > features
>>>>>>>>> >> > can
>>>>>>>>> >> > be posted here
>>>>>>>>> >>
>>>>>>>>> >> Csound mailing list
>>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> >> Send bugs reports to
>>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>>> >
>>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>> > features can
>>>>>>>>> > be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>> be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-10 03:55
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Did you put the Custom.cmake file in the same folder as the
Custom.cmake.ex (i.e. the csound source folder, not the build folder)?
 Other than that, it might be that something is adding -lpng directly
and not using the PNG variables, so it might be the lib dir is not
being set for /usr/local/include.

On Wed, Dec 9, 2015 at 7:59 PM, Kevin Welsh  wrote:
> Thanks for the Suggestions Steven, but still no luck.
>
> Just to make sure I didn't do the first suggestion wrong, Custom.cmake
> was an empty file, I presume Custom.cmake.ex was an example and not to
> be used here.  Those 3 lines are now the *ONLY* lines in the
> Custom.cmake file.  I tried building this way first, it still failed.
>
> Then I edited CMakeCache.txt, changing these lines to read:
> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
> and
> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>
> I did another "make clean", followed by a "cmake .", checked to make
> sure my changes were still in the file, and then ran make.  Still no
> luck, still failing with the same error message.
>
> On Wed, Dec 9, 2015 at 7:22 PM, Steven Yi  wrote:
>> Some things to try:
>>
>> 1. In my Custom.cmake, I have:
>>
>> list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")
>>
>> Maybe adding something like this or setting via commandline my help.
>>
>> 2. In your build directory, you can modify CMakeCache.txt and try
>> either deleting the PNG related entries or setting them manually.  I
>> have these:
>>
>> //Path to a library.
>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>
>> //Path to a file.
>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>
>>
>>
>> On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
>>> Thanks Guillermo, that looks like what I was looking for... but
>>> unfortunately it still didn't do the trick.
>>>
>>> I ran update_dyld_shared_cache and rebooted just to be safe, still
>>> fails in the same spot, looking for lpng.
>>>
>>> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>>>> I have not had time to look into the homebrew issue and no one else
>>>> has contributed time to look into it. It is still broken. For my own
>>>> timeline, I was planning to look at it as soon as I have an
>>>> opportunity to wipe out and redo my Mac, which may take a while
>>>> unfortunately.
>>>>
>>>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>>>> I poked around in the source tree and the only build documentation I
>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>> tools, but I don't know anything about building software in OSX.
>>>>>
>>>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>>>
>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>> the best/safest way to continue using the freshest versions with
>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>
>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>> Framework folder.
>>>>>>>
>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>> variables set up when trying homebrew.
>>>>>>>>
>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>
>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>
>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>
>>>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>>>> report 6.06.
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>>>> > of
>>>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>>>> > now
>>>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>>>> > time
>>>>>>>>>> > until I or someone else can look into it.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>>>> >>
>>>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>>>> >> comes with.
>>>>>>>>>> >>
>>>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>> >> > version of
>>>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>>>> >> > is
>>>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>>>> >> > wrong
>>>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>> >> > terminal.
>>>>>>>>>> >> >
>>>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>>>> >> >> getting upgraded?
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>> >> >> wrote:
>>>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>>>> >> >> > the
>>>>>>>>>> >> >> > command
>>>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>>>> >> >> > Csound
>>>>>>>>>> >> >> > library.
>>>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>>>> >> >> >
>>>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>> >> >> > wrote:
>>>>>>>>>> >> >> >>
>>>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>>>> >> >> >>
>>>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>> >> >> >> command
>>>>>>>>>> >> >> >> no
>>>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>>>> >> >> >>
>>>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>>>> >> >> >> reports
>>>>>>>>>> >> >> >> 6.04
>>>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>>>> >> >> >> found",
>>>>>>>>>> >> >> >> as
>>>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>>>> >> >> >>
>>>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>>>> >> >> >> wrote:
>>>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>>>> >> >> >> > it
>>>>>>>>>> >> >> >> > ships
>>>>>>>>>> >> >> >> > with
>>>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>>>> >> >> >> >
>>>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>>>> >> >> >> > wrote:
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>>>> >> >> >> >> over
>>>>>>>>>> >> >> >> >> the
>>>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>>>> >> >> >> >> can
>>>>>>>>>> >> >> >> >> use
>>>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> When I do:
>>>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>>>> >> >> >> >> when
>>>>>>>>>> >> >> >> >> it
>>>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>>>> >> >> >> >> it
>>>>>>>>>> >> >> >> >> still
>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>> >> >> >> >> command
>>>>>>>>>> >> >> >> >> was
>>>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>>>> >> >> >> >> didn't
>>>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>>>> >> >> >> >>
>>>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>> >> >> >> >
>>>>>>>>>> >> >> >> >
>>>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>> >> >> >> > reports
>>>>>>>>>> >> >> >> > to
>>>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>> >> >> >> > and
>>>>>>>>>> >> >> >> > features
>>>>>>>>>> >> >> >> > can
>>>>>>>>>> >> >> >> > be posted here
>>>>>>>>>> >> >> >>
>>>>>>>>>> >> >> >> Csound mailing list
>>>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>> >> >> >
>>>>>>>>>> >> >> >
>>>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>> >> >> > to
>>>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>> >> >> > features
>>>>>>>>>> >> >> > can
>>>>>>>>>> >> >> > be posted here
>>>>>>>>>> >> >>
>>>>>>>>>> >> >> Csound mailing list
>>>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> >> >> Send bugs reports to
>>>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>> >> >
>>>>>>>>>> >> >
>>>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>> >> > features
>>>>>>>>>> >> > can
>>>>>>>>>> >> > be posted here
>>>>>>>>>> >>
>>>>>>>>>> >> Csound mailing list
>>>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> >> Send bugs reports to
>>>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>>>> >
>>>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>> > features can
>>>>>>>>>> > be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>> be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-10 05:42
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Am I attempting to build from the wrong folder?

Yes, Custom.cmake is in the same folder as the .ex file, which is
where I attempting all build commands from.

On Wed, Dec 9, 2015 at 10:55 PM, Steven Yi  wrote:
> Did you put the Custom.cmake file in the same folder as the
> Custom.cmake.ex (i.e. the csound source folder, not the build folder)?
>  Other than that, it might be that something is adding -lpng directly
> and not using the PNG variables, so it might be the lib dir is not
> being set for /usr/local/include.
>
> On Wed, Dec 9, 2015 at 7:59 PM, Kevin Welsh  wrote:
>> Thanks for the Suggestions Steven, but still no luck.
>>
>> Just to make sure I didn't do the first suggestion wrong, Custom.cmake
>> was an empty file, I presume Custom.cmake.ex was an example and not to
>> be used here.  Those 3 lines are now the *ONLY* lines in the
>> Custom.cmake file.  I tried building this way first, it still failed.
>>
>> Then I edited CMakeCache.txt, changing these lines to read:
>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>> and
>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>
>> I did another "make clean", followed by a "cmake .", checked to make
>> sure my changes were still in the file, and then ran make.  Still no
>> luck, still failing with the same error message.
>>
>> On Wed, Dec 9, 2015 at 7:22 PM, Steven Yi  wrote:
>>> Some things to try:
>>>
>>> 1. In my Custom.cmake, I have:
>>>
>>> list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")
>>>
>>> Maybe adding something like this or setting via commandline my help.
>>>
>>> 2. In your build directory, you can modify CMakeCache.txt and try
>>> either deleting the PNG related entries or setting them manually.  I
>>> have these:
>>>
>>> //Path to a library.
>>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>>
>>> //Path to a file.
>>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>>
>>>
>>>
>>> On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
>>>> Thanks Guillermo, that looks like what I was looking for... but
>>>> unfortunately it still didn't do the trick.
>>>>
>>>> I ran update_dyld_shared_cache and rebooted just to be safe, still
>>>> fails in the same spot, looking for lpng.
>>>>
>>>> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>>>>> I have not had time to look into the homebrew issue and no one else
>>>>> has contributed time to look into it. It is still broken. For my own
>>>>> timeline, I was planning to look at it as soon as I have an
>>>>> opportunity to wipe out and redo my Mac, which may take a while
>>>>> unfortunately.
>>>>>
>>>>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>>>>> I poked around in the source tree and the only build documentation I
>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>
>>>>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>>>>
>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>
>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>> Framework folder.
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>
>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>
>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>
>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>
>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>>>>> report 6.06.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>>>>> > of
>>>>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>>>>> > now
>>>>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>>>>> > time
>>>>>>>>>>> > until I or someone else can look into it.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>>>>> >> comes with.
>>>>>>>>>>> >>
>>>>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>> >> > version of
>>>>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>>>>> >> > is
>>>>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>>>>> >> > wrong
>>>>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>> >> > terminal.
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>>>>> >> >> getting upgraded?
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>>>>> >> >> > the
>>>>>>>>>>> >> >> > command
>>>>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>>>>> >> >> > Csound
>>>>>>>>>>> >> >> > library.
>>>>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>>>>> >> >> >
>>>>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>> >> >> > wrote:
>>>>>>>>>>> >> >> >>
>>>>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>>>>> >> >> >>
>>>>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>> >> >> >> command
>>>>>>>>>>> >> >> >> no
>>>>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>>>>> >> >> >>
>>>>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>> >> >> >> reports
>>>>>>>>>>> >> >> >> 6.04
>>>>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>>>>> >> >> >> found",
>>>>>>>>>>> >> >> >> as
>>>>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>>>>> >> >> >>
>>>>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>>>>> >> >> >> wrote:
>>>>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>>>>> >> >> >> > it
>>>>>>>>>>> >> >> >> > ships
>>>>>>>>>>> >> >> >> > with
>>>>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>>>>> >> >> >> >
>>>>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>>>>> >> >> >> > wrote:
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>>>>> >> >> >> >> over
>>>>>>>>>>> >> >> >> >> the
>>>>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>>>>> >> >> >> >> can
>>>>>>>>>>> >> >> >> >> use
>>>>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> When I do:
>>>>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>>>>> >> >> >> >> when
>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>> >> >> >> >> still
>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>> >> >> >> >> command
>>>>>>>>>>> >> >> >> >> was
>>>>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>>>>> >> >> >> >> didn't
>>>>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>> >> >> >> >
>>>>>>>>>>> >> >> >> >
>>>>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>> >> >> >> > reports
>>>>>>>>>>> >> >> >> > to
>>>>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>> >> >> >> > and
>>>>>>>>>>> >> >> >> > features
>>>>>>>>>>> >> >> >> > can
>>>>>>>>>>> >> >> >> > be posted here
>>>>>>>>>>> >> >> >>
>>>>>>>>>>> >> >> >> Csound mailing list
>>>>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>> >> >> >
>>>>>>>>>>> >> >> >
>>>>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>> >> >> > to
>>>>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> >> >> > features
>>>>>>>>>>> >> >> > can
>>>>>>>>>>> >> >> > be posted here
>>>>>>>>>>> >> >>
>>>>>>>>>>> >> >> Csound mailing list
>>>>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> >> >> Send bugs reports to
>>>>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>> >> >
>>>>>>>>>>> >> >
>>>>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> >> > features
>>>>>>>>>>> >> > can
>>>>>>>>>>> >> > be posted here
>>>>>>>>>>> >>
>>>>>>>>>>> >> Csound mailing list
>>>>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> >> Send bugs reports to
>>>>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>>>>> >
>>>>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>> > features can
>>>>>>>>>>> > be posted here
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>>> be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-15 21:03
FromSteven Yi
SubjectRe: help building fresh with homebrew *over* existing cabbage install
I tend to build in a directory outside of the source folder. So if I
have the source in somefolder/csound, I might make a directory and
build either in somefolder/csbuild or somefolder/csound/build.

One other thing to try is to just delete your whole CMakeCache.txt and
restart the process.  I think sometimes a setting might get cached
that should be rechecked but doesn't.

On Thu, Dec 10, 2015 at 12:42 AM, Kevin Welsh  wrote:
> Am I attempting to build from the wrong folder?
>
> Yes, Custom.cmake is in the same folder as the .ex file, which is
> where I attempting all build commands from.
>
> On Wed, Dec 9, 2015 at 10:55 PM, Steven Yi  wrote:
>> Did you put the Custom.cmake file in the same folder as the
>> Custom.cmake.ex (i.e. the csound source folder, not the build folder)?
>>  Other than that, it might be that something is adding -lpng directly
>> and not using the PNG variables, so it might be the lib dir is not
>> being set for /usr/local/include.
>>
>> On Wed, Dec 9, 2015 at 7:59 PM, Kevin Welsh  wrote:
>>> Thanks for the Suggestions Steven, but still no luck.
>>>
>>> Just to make sure I didn't do the first suggestion wrong, Custom.cmake
>>> was an empty file, I presume Custom.cmake.ex was an example and not to
>>> be used here.  Those 3 lines are now the *ONLY* lines in the
>>> Custom.cmake file.  I tried building this way first, it still failed.
>>>
>>> Then I edited CMakeCache.txt, changing these lines to read:
>>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>> and
>>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>>
>>> I did another "make clean", followed by a "cmake .", checked to make
>>> sure my changes were still in the file, and then ran make.  Still no
>>> luck, still failing with the same error message.
>>>
>>> On Wed, Dec 9, 2015 at 7:22 PM, Steven Yi  wrote:
>>>> Some things to try:
>>>>
>>>> 1. In my Custom.cmake, I have:
>>>>
>>>> list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
>>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
>>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")
>>>>
>>>> Maybe adding something like this or setting via commandline my help.
>>>>
>>>> 2. In your build directory, you can modify CMakeCache.txt and try
>>>> either deleting the PNG related entries or setting them manually.  I
>>>> have these:
>>>>
>>>> //Path to a library.
>>>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>>>
>>>> //Path to a file.
>>>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>>>
>>>>
>>>>
>>>> On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
>>>>> Thanks Guillermo, that looks like what I was looking for... but
>>>>> unfortunately it still didn't do the trick.
>>>>>
>>>>> I ran update_dyld_shared_cache and rebooted just to be safe, still
>>>>> fails in the same spot, looking for lpng.
>>>>>
>>>>> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>>>>>> I have not had time to look into the homebrew issue and no one else
>>>>>> has contributed time to look into it. It is still broken. For my own
>>>>>> timeline, I was planning to look at it as soon as I have an
>>>>>> opportunity to wipe out and redo my Mac, which may take a while
>>>>>> unfortunately.
>>>>>>
>>>>>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>
>>>>>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>>>>>
>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>> Framework folder.
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>
>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>
>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>
>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>>>>>> > of
>>>>>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>>>>>> > now
>>>>>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>>>>>> > time
>>>>>>>>>>>> > until I or someone else can look into it.
>>>>>>>>>>>> >
>>>>>>>>>>>> >
>>>>>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>>>>>> >> comes with.
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>>>>>> >>
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>> >> > version of
>>>>>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>>>>>> >> > is
>>>>>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>>>>>> >> > wrong
>>>>>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>> >> > terminal.
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>>>>>> >> >> getting upgraded?
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>>>>>> >> >> > the
>>>>>>>>>>>> >> >> > command
>>>>>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>>>>>> >> >> > Csound
>>>>>>>>>>>> >> >> > library.
>>>>>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>>>>>> >> >> >
>>>>>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>> >> >> > wrote:
>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>> >> >> >> command
>>>>>>>>>>>> >> >> >> no
>>>>>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>> >> >> >> reports
>>>>>>>>>>>> >> >> >> 6.04
>>>>>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>>>>>> >> >> >> found",
>>>>>>>>>>>> >> >> >> as
>>>>>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>>>>>> >> >> >> wrote:
>>>>>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>>>>>> >> >> >> > it
>>>>>>>>>>>> >> >> >> > ships
>>>>>>>>>>>> >> >> >> > with
>>>>>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>>>>>> >> >> >> > wrote:
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>>>>>> >> >> >> >> over
>>>>>>>>>>>> >> >> >> >> the
>>>>>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>>>>>> >> >> >> >> can
>>>>>>>>>>>> >> >> >> >> use
>>>>>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> When I do:
>>>>>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>>>>>> >> >> >> >> when
>>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>>> >> >> >> >> still
>>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>> >> >> >> >> command
>>>>>>>>>>>> >> >> >> >> was
>>>>>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>>>>>> >> >> >> >> didn't
>>>>>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>> >> >> >> > reports
>>>>>>>>>>>> >> >> >> > to
>>>>>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>> >> >> >> > and
>>>>>>>>>>>> >> >> >> > features
>>>>>>>>>>>> >> >> >> > can
>>>>>>>>>>>> >> >> >> > be posted here
>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>> >> >> >> Csound mailing list
>>>>>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>> >> >> >
>>>>>>>>>>>> >> >> >
>>>>>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>> >> >> > to
>>>>>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> >> >> > features
>>>>>>>>>>>> >> >> > can
>>>>>>>>>>>> >> >> > be posted here
>>>>>>>>>>>> >> >>
>>>>>>>>>>>> >> >> Csound mailing list
>>>>>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> >> >> Send bugs reports to
>>>>>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> >
>>>>>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> >> > features
>>>>>>>>>>>> >> > can
>>>>>>>>>>>> >> > be posted here
>>>>>>>>>>>> >>
>>>>>>>>>>>> >> Csound mailing list
>>>>>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> >> Send bugs reports to
>>>>>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>> >
>>>>>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>> > features can
>>>>>>>>>>>> > be posted here
>>>>>>>>>>>>
>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>>>> be posted here
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-22 23:54
FromKevin Welsh
SubjectRe: help building fresh with homebrew *over* existing cabbage install
Thanks, but still no luck.  I tried removing my CMakeCache.txt, and
also building it from a fresh directory, still fails on lpng.  I have
started fresh again, with a new unpacking of the source in case I've
mucked anything up...

I noticed this output when running cmake:
-- Found PNG: /usr/local/lib/libpng.dylib (found version "1.6.19")

Curious that cmake sees it but it still fails on the build.

On Tue, Dec 15, 2015 at 4:03 PM, Steven Yi  wrote:
> I tend to build in a directory outside of the source folder. So if I
> have the source in somefolder/csound, I might make a directory and
> build either in somefolder/csbuild or somefolder/csound/build.
>
> One other thing to try is to just delete your whole CMakeCache.txt and
> restart the process.  I think sometimes a setting might get cached
> that should be rechecked but doesn't.
>
> On Thu, Dec 10, 2015 at 12:42 AM, Kevin Welsh  wrote:
>> Am I attempting to build from the wrong folder?
>>
>> Yes, Custom.cmake is in the same folder as the .ex file, which is
>> where I attempting all build commands from.
>>
>> On Wed, Dec 9, 2015 at 10:55 PM, Steven Yi  wrote:
>>> Did you put the Custom.cmake file in the same folder as the
>>> Custom.cmake.ex (i.e. the csound source folder, not the build folder)?
>>>  Other than that, it might be that something is adding -lpng directly
>>> and not using the PNG variables, so it might be the lib dir is not
>>> being set for /usr/local/include.
>>>
>>> On Wed, Dec 9, 2015 at 7:59 PM, Kevin Welsh  wrote:
>>>> Thanks for the Suggestions Steven, but still no luck.
>>>>
>>>> Just to make sure I didn't do the first suggestion wrong, Custom.cmake
>>>> was an empty file, I presume Custom.cmake.ex was an example and not to
>>>> be used here.  Those 3 lines are now the *ONLY* lines in the
>>>> Custom.cmake file.  I tried building this way first, it still failed.
>>>>
>>>> Then I edited CMakeCache.txt, changing these lines to read:
>>>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>>> and
>>>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>>>
>>>> I did another "make clean", followed by a "cmake .", checked to make
>>>> sure my changes were still in the file, and then ran make.  Still no
>>>> luck, still failing with the same error message.
>>>>
>>>> On Wed, Dec 9, 2015 at 7:22 PM, Steven Yi  wrote:
>>>>> Some things to try:
>>>>>
>>>>> 1. In my Custom.cmake, I have:
>>>>>
>>>>> list(APPEND CMAKE_SYSTEM_LIBRARY_PATH "/usr/local/lib")
>>>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/local/include")
>>>>> list(APPEND CMAKE_SYSTEM_INCLUDE_PATH "/usr/include")
>>>>>
>>>>> Maybe adding something like this or setting via commandline my help.
>>>>>
>>>>> 2. In your build directory, you can modify CMakeCache.txt and try
>>>>> either deleting the PNG related entries or setting them manually.  I
>>>>> have these:
>>>>>
>>>>> //Path to a library.
>>>>> PNG_LIBRARY_RELEASE:FILEPATH=/usr/local/lib/libpng.dylib
>>>>>
>>>>> //Path to a file.
>>>>> PNG_PNG_INCLUDE_DIR:PATH=/usr/local/include
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Dec 9, 2015 at 5:43 PM, Kevin Welsh  wrote:
>>>>>> Thanks Guillermo, that looks like what I was looking for... but
>>>>>> unfortunately it still didn't do the trick.
>>>>>>
>>>>>> I ran update_dyld_shared_cache and rebooted just to be safe, still
>>>>>> fails in the same spot, looking for lpng.
>>>>>>
>>>>>> On Wed, Dec 9, 2015 at 4:22 PM, Steven Yi  wrote:
>>>>>>> I have not had time to look into the homebrew issue and no one else
>>>>>>> has contributed time to look into it. It is still broken. For my own
>>>>>>> timeline, I was planning to look at it as soon as I have an
>>>>>>> opportunity to wipe out and redo my Mac, which may take a while
>>>>>>> unfortunately.
>>>>>>>
>>>>>>> On Tue, Dec 8, 2015 at 9:33 PM, Kevin Welsh  wrote:
>>>>>>>> I poked around in the source tree and the only build documentation I
>>>>>>>> found is specifically for homebrew... is it still broken?  It could be
>>>>>>>> I'm looking in the wrong place, or maybe it's so easy that
>>>>>>>> instructions aren't needed assuming basic familiarity with the system
>>>>>>>> tools, but I don't know anything about building software in OSX.
>>>>>>>>
>>>>>>>> Is there a doc or set of instructions I could refer to for help getting started?
>>>>>>>>
>>>>>>>> On Tue, Dec 1, 2015 at 12:59 AM, Kevin Welsh  wrote:
>>>>>>>>> Thanks everyone, this did get my cabbage working with the newest
>>>>>>>>> csound version, however I still have no CLI version.  What would be
>>>>>>>>> the best/safest way to continue using the freshest versions with
>>>>>>>>> cabbage, but maintaining CLI functionality too?
>>>>>>>>>
>>>>>>>>> On Tue, Nov 17, 2015 at 11:40 AM, Steven Yi  wrote:
>>>>>>>>>> That is correct.  If the linker path is relative, it will check local
>>>>>>>>>> to the executable, then the local Framework folder, then the system
>>>>>>>>>> Framework folder.
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 17, 2015 at 3:42 PM, Rory Walsh  wrote:
>>>>>>>>>>> That doesn't seem write though. Perhaps there were some environment
>>>>>>>>>>> variables set up when trying homebrew.
>>>>>>>>>>>
>>>>>>>>>>> On 17 November 2015 at 15:41, Rory Walsh  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I guess OSX checks the user Library folder before the system one.
>>>>>>>>>>>>
>>>>>>>>>>>> On 17 November 2015 at 15:14, Kevin Welsh  wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> That was it!  Removing that framework directory suddenly makes cabbage
>>>>>>>>>>>>> report 6.06.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Nov 17, 2015 at 9:59 AM, Steven Yi  wrote:
>>>>>>>>>>>>> > Check that there isn't a CsoundLib64.framework in ~/Library/Frameworks
>>>>>>>>>>>>> > folder. If so, try moving or deleting that. The current homebrew build
>>>>>>>>>>>>> > of
>>>>>>>>>>>>> > Csound has problems. I have not found time to look into it and won't
>>>>>>>>>>>>> > now
>>>>>>>>>>>>> > until I get back home in December.  I recommend not using it at this
>>>>>>>>>>>>> > time
>>>>>>>>>>>>> > until I or someone else can look into it.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > On Tue, Nov 17, 2015, 2:49 PM Kevin Welsh  wrote:
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> But I uninstalled the homebrew version, and confirmed that the console
>>>>>>>>>>>>> >> version of csound was gone too... I was trying to rule that out as the
>>>>>>>>>>>>> >> problem, just running the newest cabbage release and the csound it
>>>>>>>>>>>>> >> comes with.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> My thought is homebrew somehow messed up a file permission or config
>>>>>>>>>>>>> >> for loading the library that has left it running a stale version...
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> On Tue, Nov 17, 2015 at 9:44 AM, Rory Walsh  wrote:
>>>>>>>>>>>>> >> > I'm not sure what's going on because I'm pretty sure the last
>>>>>>>>>>>>> >> > version of
>>>>>>>>>>>>> >> > Cabbage you installed on OSX installed 6.05, I'm not sure where 6.04
>>>>>>>>>>>>> >> > is
>>>>>>>>>>>>> >> > coming from? I have no idea how homebrew works, is it fetching the
>>>>>>>>>>>>> >> > wrong
>>>>>>>>>>>>> >> > package? I've only ever built Csound on OSX using cmake and the
>>>>>>>>>>>>> >> > terminal.
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > On 17 November 2015 at 14:29, Kevin Welsh  wrote:
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> So I'm guessing this means for some reason my csound library isn't
>>>>>>>>>>>>> >> >> getting upgraded?
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> On Tue, Nov 17, 2015 at 8:55 AM, Rory Walsh 
>>>>>>>>>>>>> >> >> wrote:
>>>>>>>>>>>>> >> >> > Cabbage links to the Csound library whereas running csound from
>>>>>>>>>>>>> >> >> > the
>>>>>>>>>>>>> >> >> > command
>>>>>>>>>>>>> >> >> > line calls the csound application, which in turns calls the
>>>>>>>>>>>>> >> >> > Csound
>>>>>>>>>>>>> >> >> > library.
>>>>>>>>>>>>> >> >> > Cabbage only needs to underlying libraries.
>>>>>>>>>>>>> >> >> >
>>>>>>>>>>>>> >> >> > On 17 November 2015 at 12:38, Kevin Welsh 
>>>>>>>>>>>>> >> >> > wrote:
>>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>>> >> >> >> Well, then now I'm really confused.
>>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>>> >> >> >> I uninstalled the homebrew version, confirmed that "csound"
>>>>>>>>>>>>> >> >> >> command
>>>>>>>>>>>>> >> >> >> no
>>>>>>>>>>>>> >> >> >> longer worked at the command line.
>>>>>>>>>>>>> >> >> >> I installed a fresh download from
>>>>>>>>>>>>> >> >> >> http://www.cabbageaudio.com/download/
>>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>>> >> >> >> Cabbage appears to work fine, but in the output window it
>>>>>>>>>>>>> >> >> >> reports
>>>>>>>>>>>>> >> >> >> 6.04
>>>>>>>>>>>>> >> >> >> still... and from a command line it still says "command not
>>>>>>>>>>>>> >> >> >> found",
>>>>>>>>>>>>> >> >> >> as
>>>>>>>>>>>>> >> >> >> if I have no csound at all.
>>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>>> >> >> >> On Tue, Nov 17, 2015 at 6:29 AM, Rory Walsh 
>>>>>>>>>>>>> >> >> >> wrote:
>>>>>>>>>>>>> >> >> >> > For what it's worth, I just updated the OSX installer so that
>>>>>>>>>>>>> >> >> >> > it
>>>>>>>>>>>>> >> >> >> > ships
>>>>>>>>>>>>> >> >> >> > with
>>>>>>>>>>>>> >> >> >> > the latest version of Csound, i.e., 6.06.
>>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>>> >> >> >> > On 17 November 2015 at 03:08, Kevin Welsh 
>>>>>>>>>>>>> >> >> >> > wrote:
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> My goal is to use homebrew to install a fresh build of csound
>>>>>>>>>>>>> >> >> >> >> over
>>>>>>>>>>>>> >> >> >> >> the
>>>>>>>>>>>>> >> >> >> >> one packaged with the most recent cabbage release, so that I
>>>>>>>>>>>>> >> >> >> >> can
>>>>>>>>>>>>> >> >> >> >> use
>>>>>>>>>>>>> >> >> >> >> the new csound features from within cabbage.
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> When I do:
>>>>>>>>>>>>> >> >> >> >> brew install -HEAD csound
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> it appears to fetch and build 6.05, and I forced an overwrite
>>>>>>>>>>>>> >> >> >> >> when
>>>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>>>> >> >> >> >> linked the first time.  But when I run csound form a console
>>>>>>>>>>>>> >> >> >> >> it
>>>>>>>>>>>>> >> >> >> >> still
>>>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> I tried uninstalling via homebrew, confirming my csound
>>>>>>>>>>>>> >> >> >> >> command
>>>>>>>>>>>>> >> >> >> >> was
>>>>>>>>>>>>> >> >> >> >> gone, and rebuilding via the homebrew command, this time it
>>>>>>>>>>>>> >> >> >> >> didn't
>>>>>>>>>>>>> >> >> >> >> require forcing the overwrite, but I still run csound and it
>>>>>>>>>>>>> >> >> >> >> reports:
>>>>>>>>>>>>> >> >> >> >> Csound version 6.04 (double samples) Feb 26 2015
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> What am I doing wrong or forgetting to do to upgrade this?
>>>>>>>>>>>>> >> >> >> >>
>>>>>>>>>>>>> >> >> >> >> Csound mailing list
>>>>>>>>>>>>> >> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> >> >> >> >> Send bugs reports to
>>>>>>>>>>>>> >> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>>> >> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>>> >> >> >> >
>>>>>>>>>>>>> >> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>>>>>>>>>>>>> >> >> >> > reports
>>>>>>>>>>>>> >> >> >> > to
>>>>>>>>>>>>> >> >> >> > https://github.com/csound/csound/issues Discussions of bugs
>>>>>>>>>>>>> >> >> >> > and
>>>>>>>>>>>>> >> >> >> > features
>>>>>>>>>>>>> >> >> >> > can
>>>>>>>>>>>>> >> >> >> > be posted here
>>>>>>>>>>>>> >> >> >>
>>>>>>>>>>>>> >> >> >> Csound mailing list
>>>>>>>>>>>>> >> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> >> >> >> Send bugs reports to
>>>>>>>>>>>>> >> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>>> >> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> >> >> >
>>>>>>>>>>>>> >> >> >
>>>>>>>>>>>>> >> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>>>>>>>>>> >> >> > to
>>>>>>>>>>>>> >> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> >> >> > features
>>>>>>>>>>>>> >> >> > can
>>>>>>>>>>>>> >> >> > be posted here
>>>>>>>>>>>>> >> >>
>>>>>>>>>>>>> >> >> Csound mailing list
>>>>>>>>>>>>> >> >> Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> >> >> Send bugs reports to
>>>>>>>>>>>>> >> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>>> >> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> >
>>>>>>>>>>>>> >> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> >> > features
>>>>>>>>>>>>> >> > can
>>>>>>>>>>>>> >> > be posted here
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Csound mailing list
>>>>>>>>>>>>> >> Csound@listserv.heanet.ie
>>>>>>>>>>>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> >> Send bugs reports to
>>>>>>>>>>>>> >>         https://github.com/csound/csound/issues
>>>>>>>>>>>>> >> Discussions of bugs and features can be posted here
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>>>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>>>> > https://github.com/csound/csound/issues Discussions of bugs and
>>>>>>>>>>>>> > features can
>>>>>>>>>>>>> > be posted here
>>>>>>>>>>>>>
>>>>>>>>>>>>> Csound mailing list
>>>>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Csound mailing list Csound@listserv.heanet.ie
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>>>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can
>>>>>>>>>>> be posted here
>>>>>>>>>>
>>>>>>>>>> Csound mailing list
>>>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> Csound@listserv.heanet.ie
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>         https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> Csound@listserv.heanet.ie
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>         https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here