[Csnd] Advice for Developing/Debugging Csound on Mac

Date	2018-02-01 17:23
From	Ben McAllister
Subject	[Csnd] Advice for Developing/Debugging Csound on Mac
	Hi All - this question was buried in a previous message, but pulling it out separately hoping to get a response from csound developers: If you're working on a Mac, I'm curious what you're using for a development/debugging environment. Did you create an xcodeproj for Mac Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in the minority, and are more devs on Linux using.. gdb and ddd maybe? As an old csounder and experienced developer (been at both since 96 or so), I'd like to get more familiar with this tool I love and maybe contribute. Thanks in advance, b Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 17:42
From	Edward Costello
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Using CMake you can create an Xcode project from the Csound sources which you can use to develop/debug Csound using Xcode. git clone https://github.com/csound/csound.git cd csound mkdir Xcode cd Xcode cmake -G Xcode .. Best, Ed On 1 Feb 2018, at 09:23, Ben McAllister <benmca@GMAIL.COM> wrote: Hi All - this question was buried in a previous message, but pulling it out separately hoping to get a response from csound developers: If you're working on a Mac, I'm curious what you're using for a development/debugging environment. Did you create an xcodeproj for Mac Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in the minority, and are more devs on Linux using.. gdb and ddd maybe? As an old csounder and experienced developer (been at both since 96 or so), I'd like to get more familiar with this tool I love and maybe contribute. Thanks in advance, b Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 17:53
From	Steven Yi
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I don't use OSX much these days, but I when I do, I usually work on Csound via XCode. I pretty much do the same steps as Ed mentioned to create an XCode project. Within XCode, I would use the built-in debugger and profile with Instruments. One can use cmd-shift-, and setup a number of different command-line args to run with different settings, different, csds, and switch between them pretty easily. I would also maintain a separate command-line build via make or ninja and would typically use that one for general building/running unit tests/installing. I probably used gdb for quick debug sessions and vim for quick edits, and used XCode for trickier debugging/profiling. On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: > Using CMake you can create an Xcode project from the Csound sources which > you can use to develop/debug Csound using Xcode. > > git clone https://github.com/csound/csound.git > cd csound > mkdir Xcode > cd Xcode > cmake -G Xcode .. > > > Best, > Ed > > On 1 Feb 2018, at 09:23, Ben McAllister wrote: > > Hi All - this question was buried in a previous message, but pulling it out > separately hoping to get a response from csound developers: > > If you're working on a Mac, I'm curious what you're using for a > development/debugging environment. Did you create an xcodeproj for Mac > Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in > the minority, and are more devs on Linux using.. gdb and ddd maybe? > > As an old csounder and experienced developer (been at both since 96 or so), > I'd like to get more familiar with this tool I love and maybe contribute. > > Thanks in advance, > b > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 18:33
From	Victor Lazzarini
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when it worked. ======================== Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: > > I don't use OSX much these days, but I when I do, I usually work on > Csound via XCode. I pretty much do the same steps as Ed mentioned to > create an XCode project. > > Within XCode, I would use the built-in debugger and profile with > Instruments. One can use cmd-shift-, and setup a number of different > command-line args to run with different settings, different, csds, and > switch between them pretty easily. I would also maintain a separate > command-line build via make or ninja and would typically use that one > for general building/running unit tests/installing. I probably used > gdb for quick debug sessions and vim for quick edits, and used XCode > for trickier debugging/profiling. > > On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >> Using CMake you can create an Xcode project from the Csound sources which >> you can use to develop/debug Csound using Xcode. >> >> git clone https://github.com/csound/csound.git >> cd csound >> mkdir Xcode >> cd Xcode >> cmake -G Xcode .. >> >> >> Best, >> Ed >> >> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >> >> Hi All - this question was buried in a previous message, but pulling it out >> separately hoping to get a response from csound developers: >> >> If you're working on a Mac, I'm curious what you're using for a >> development/debugging environment. Did you create an xcodeproj for Mac >> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >> the minority, and are more devs on Linux using.. gdb and ddd maybe? >> >> As an old csounder and experienced developer (been at both since 96 or so), >> I'd like to get more familiar with this tool I love and maybe contribute. >> >> Thanks in advance, >> b >> Csound mailing list Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> https://github.com/csound/csound/issues Discussions of bugs and features can >> be posted here >> >> >> Csound mailing list Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> https://github.com/csound/csound/issues Discussions of bugs and features can >> be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 18:48
From	Anders Genell
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? Regards, Anders > 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : > > I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when > it worked. > ======================== > Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >> >> I don't use OSX much these days, but I when I do, I usually work on >> Csound via XCode. I pretty much do the same steps as Ed mentioned to >> create an XCode project. >> >> Within XCode, I would use the built-in debugger and profile with >> Instruments. One can use cmd-shift-, and setup a number of different >> command-line args to run with different settings, different, csds, and >> switch between them pretty easily. I would also maintain a separate >> command-line build via make or ninja and would typically use that one >> for general building/running unit tests/installing. I probably used >> gdb for quick debug sessions and vim for quick edits, and used XCode >> for trickier debugging/profiling. >> >>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >>> Using CMake you can create an Xcode project from the Csound sources which >>> you can use to develop/debug Csound using Xcode. >>> >>> git clone https://github.com/csound/csound.git >>> cd csound >>> mkdir Xcode >>> cd Xcode >>> cmake -G Xcode .. >>> >>> >>> Best, >>> Ed >>> >>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >>> >>> Hi All - this question was buried in a previous message, but pulling it out >>> separately hoping to get a response from csound developers: >>> >>> If you're working on a Mac, I'm curious what you're using for a >>> development/debugging environment. Did you create an xcodeproj for Mac >>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >>> >>> As an old csounder and experienced developer (been at both since 96 or so), >>> I'd like to get more familiar with this tool I love and maybe contribute. >>> >>> Thanks in advance, >>> b >>> Csound mailing list Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>> https://github.com/csound/csound/issues Discussions of bugs and features can >>> be posted here >>> >>> >>> Csound mailing list Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>> https://github.com/csound/csound/issues Discussions of bugs and features can >>> be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 18:58
From	Victor Lazzarini
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 1 Feb 2018, at 18:48, Anders Genell wrote: > > I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? > > Regards, > Anders > >> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : >> >> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >> it worked. >> ======================== >> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >>> >>> I don't use OSX much these days, but I when I do, I usually work on >>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >>> create an XCode project. >>> >>> Within XCode, I would use the built-in debugger and profile with >>> Instruments. One can use cmd-shift-, and setup a number of different >>> command-line args to run with different settings, different, csds, and >>> switch between them pretty easily. I would also maintain a separate >>> command-line build via make or ninja and would typically use that one >>> for general building/running unit tests/installing. I probably used >>> gdb for quick debug sessions and vim for quick edits, and used XCode >>> for trickier debugging/profiling. >>> >>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >>>> Using CMake you can create an Xcode project from the Csound sources which >>>> you can use to develop/debug Csound using Xcode. >>>> >>>> git clone https://github.com/csound/csound.git >>>> cd csound >>>> mkdir Xcode >>>> cd Xcode >>>> cmake -G Xcode .. >>>> >>>> >>>> Best, >>>> Ed >>>> >>>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >>>> >>>> Hi All - this question was buried in a previous message, but pulling it out >>>> separately hoping to get a response from csound developers: >>>> >>>> If you're working on a Mac, I'm curious what you're using for a >>>> development/debugging environment. Did you create an xcodeproj for Mac >>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >>>> >>>> As an old csounder and experienced developer (been at both since 96 or so), >>>> I'd like to get more familiar with this tool I love and maybe contribute. >>>> >>>> Thanks in advance, >>>> b >>>> Csound mailing list Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>> be posted here >>>> >>>> >>>> Csound mailing list Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>> be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 19:21
From	Anders Genell
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. Thanks! > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini : > > I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 1 Feb 2018, at 18:48, Anders Genell wrote: >> >> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? >> >> Regards, >> Anders >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : >>> >>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >>> it worked. >>> ======================== >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >>>> >>>> I don't use OSX much these days, but I when I do, I usually work on >>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >>>> create an XCode project. >>>> >>>> Within XCode, I would use the built-in debugger and profile with >>>> Instruments. One can use cmd-shift-, and setup a number of different >>>> command-line args to run with different settings, different, csds, and >>>> switch between them pretty easily. I would also maintain a separate >>>> command-line build via make or ninja and would typically use that one >>>> for general building/running unit tests/installing. I probably used >>>> gdb for quick debug sessions and vim for quick edits, and used XCode >>>> for trickier debugging/profiling. >>>> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >>>>> Using CMake you can create an Xcode project from the Csound sources which >>>>> you can use to develop/debug Csound using Xcode. >>>>> >>>>> git clone https://github.com/csound/csound.git >>>>> cd csound >>>>> mkdir Xcode >>>>> cd Xcode >>>>> cmake -G Xcode .. >>>>> >>>>> >>>>> Best, >>>>> Ed >>>>> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >>>>> >>>>> Hi All - this question was buried in a previous message, but pulling it out >>>>> separately hoping to get a response from csound developers: >>>>> >>>>> If you're working on a Mac, I'm curious what you're using for a >>>>> development/debugging environment. Did you create an xcodeproj for Mac >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >>>>> >>>>> As an old csounder and experienced developer (been at both since 96 or so), >>>>> I'd like to get more familiar with this tool I love and maybe contribute. >>>>> >>>>> Thanks in advance, >>>>> b >>>>> Csound mailing list Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>> be posted here >>>>> >>>>> >>>>> Csound mailing list Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>> be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 20:05
From	Ben McAllister
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Didn't know about cmake -G xcode - thanks you two! On Thu, Feb 1, 2018 at 9:53 AM, Steven Yi <stevenyi@gmail.com> wrote: I don't use OSX much these days, but I when I do, I usually work on Csound via XCode. I pretty much do the same steps as Ed mentioned to create an XCode project. Within XCode, I would use the built-in debugger and profile with Instruments. One can use cmd-shift-, and setup a number of different command-line args to run with different settings, different, csds, and switch between them pretty easily. I would also maintain a separate command-line build via make or ninja and would typically use that one for general building/running unit tests/installing. I probably used gdb for quick debug sessions and vim for quick edits, and used XCode for trickier debugging/profiling. On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello <phasereset@gmail.com> wrote: > Using CMake you can create an Xcode project from the Csound sources which > you can use to develop/debug Csound using Xcode. > > git clone https://github.com/csound/csound.git > cd csound > mkdir Xcode > cd Xcode > cmake -G Xcode .. > > > Best, > Ed > > On 1 Feb 2018, at 09:23, Ben McAllister <benmca@GMAIL.COM> wrote: > > Hi All - this question was buried in a previous message, but pulling it out > separately hoping to get a response from csound developers: > > If you're working on a Mac, I'm curious what you're using for a > development/debugging environment. Did you create an xcodeproj for Mac > Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in > the minority, and are more devs on Linux using.. gdb and ddd maybe? > > As an old csounder and experienced developer (been at both since 96 or so), > I'd like to get more familiar with this tool I love and maybe contribute. > > Thanks in advance, > b > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here > > > Csound mailing list Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > https://github.com/csound/csound/issues Discussions of bugs and features can > be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 20:24
From	Ben McAllister
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I would use brew in favor of macports too. Would it be useful for me to write up my mac build steps and add them to build.md, since right now the build instructions point to a brew tap - not the git repo - for pulling source. Steven - straighten me out if I'm wrong on my understanding here. Also - is there still a csound dev list separate from this one? On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell <anders.genell@gmail.com> wrote: Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. Thanks! > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini <Victor.Lazzarini@MU.IE>: > > I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. > > Victor Lazzarini > Dean of Arts, Celtic Studies, and Philosophy > Maynooth University > Ireland > >> On 1 Feb 2018, at 18:48, Anders Genell <anders.genell@GMAIL.COM> wrote: >> >> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? >> >> Regards, >> Anders >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini <Victor.Lazzarini@MU.IE>: >>> >>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >>> it worked. >>> ======================== >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi <stevenyi@gmail.com> wrote: >>>> >>>> I don't use OSX much these days, but I when I do, I usually work on >>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >>>> create an XCode project. >>>> >>>> Within XCode, I would use the built-in debugger and profile with >>>> Instruments. One can use cmd-shift-, and setup a number of different >>>> command-line args to run with different settings, different, csds, and >>>> switch between them pretty easily. I would also maintain a separate >>>> command-line build via make or ninja and would typically use that one >>>> for general building/running unit tests/installing. I probably used >>>> gdb for quick debug sessions and vim for quick edits, and used XCode >>>> for trickier debugging/profiling. >>>> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello <phasereset@gmail.com> wrote: >>>>> Using CMake you can create an Xcode project from the Csound sources which >>>>> you can use to develop/debug Csound using Xcode. >>>>> >>>>> git clone https://github.com/csound/csound.git >>>>> cd csound >>>>> mkdir Xcode >>>>> cd Xcode >>>>> cmake -G Xcode .. >>>>> >>>>> >>>>> Best, >>>>> Ed >>>>> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister <benmca@GMAIL.COM> wrote: >>>>> >>>>> Hi All - this question was buried in a previous message, but pulling it out >>>>> separately hoping to get a response from csound developers: >>>>> >>>>> If you're working on a Mac, I'm curious what you're using for a >>>>> development/debugging environment. Did you create an xcodeproj for Mac >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >>>>> >>>>> As an old csounder and experienced developer (been at both since 96 or so), >>>>> I'd like to get more familiar with this tool I love and maybe contribute. >>>>> >>>>> Thanks in advance, >>>>> b >>>>> Csound mailing list Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>> be posted here >>>>> >>>>> >>>>> Csound mailing list Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>> be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 20:32
From	Victor Lazzarini
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	The scripts in dependencies are designed to install things directly without having to use brew, if you want to try. ======================== Prof. 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 1 Feb 2018, at 20:24, Ben McAllister wrote: > > I would use brew in favor of macports too. Would it be useful for me to write up my mac build steps and add them to build.md, since right now the build instructions point to a brew tap - not the git repo - for pulling source. Steven - straighten me out if I'm wrong on my understanding here. > > Also - is there still a csound dev list separate from this one? > > On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell wrote: > Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. > Thanks! > > > > > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini : > > > > I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. > > > > Victor Lazzarini > > Dean of Arts, Celtic Studies, and Philosophy > > Maynooth University > > Ireland > > > >> On 1 Feb 2018, at 18:48, Anders Genell wrote: > >> > >> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? > >> > >> Regards, > >> Anders > >> > >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : > >>> > >>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when > >>> it worked. > >>> ======================== > >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: > >>>> > >>>> I don't use OSX much these days, but I when I do, I usually work on > >>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to > >>>> create an XCode project. > >>>> > >>>> Within XCode, I would use the built-in debugger and profile with > >>>> Instruments. One can use cmd-shift-, and setup a number of different > >>>> command-line args to run with different settings, different, csds, and > >>>> switch between them pretty easily. I would also maintain a separate > >>>> command-line build via make or ninja and would typically use that one > >>>> for general building/running unit tests/installing. I probably used > >>>> gdb for quick debug sessions and vim for quick edits, and used XCode > >>>> for trickier debugging/profiling. > >>>> > >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: > >>>>> Using CMake you can create an Xcode project from the Csound sources which > >>>>> you can use to develop/debug Csound using Xcode. > >>>>> > >>>>> git clone https://github.com/csound/csound.git > >>>>> cd csound > >>>>> mkdir Xcode > >>>>> cd Xcode > >>>>> cmake -G Xcode .. > >>>>> > >>>>> > >>>>> Best, > >>>>> Ed > >>>>> > >>>>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: > >>>>> > >>>>> Hi All - this question was buried in a previous message, but pulling it out > >>>>> separately hoping to get a response from csound developers: > >>>>> > >>>>> If you're working on a Mac, I'm curious what you're using for a > >>>>> development/debugging environment. Did you create an xcodeproj for Mac > >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in > >>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? > >>>>> > >>>>> As an old csounder and experienced developer (been at both since 96 or so), > >>>>> I'd like to get more familiar with this tool I love and maybe contribute. > >>>>> > >>>>> Thanks in advance, > >>>>> b > >>>>> Csound mailing list Csound@listserv.heanet.ie > >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can > >>>>> be posted here > >>>>> > >>>>> > >>>>> Csound mailing list Csound@listserv.heanet.ie > >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to > >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can > >>>>> be posted here > >>>> > >>>> Csound mailing list > >>>> Csound@listserv.heanet.ie > >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > >>>> Send bugs reports to > >>>> https://github.com/csound/csound/issues > >>>> Discussions of bugs and features can be posted here > >>> > >>> Csound mailing list > >>> Csound@listserv.heanet.ie > >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > >>> Send bugs reports to > >>> https://github.com/csound/csound/issues > >>> Discussions of bugs and features can be posted here > >> > >> Csound mailing list > >> Csound@listserv.heanet.ie > >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > >> Send bugs reports to > >> https://github.com/csound/csound/issues > >> Discussions of bugs and features can be posted here > > > > Csound mailing list > > Csound@listserv.heanet.ie > > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > > Send bugs reports to > > https://github.com/csound/csound/issues > > Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > > > > -- > Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 20:44
From	Steven Yi
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Yeah the build.md needs to be changed. Homebrew still works for a complete build last I checked. For a more manual local build, you could use Homebrew, macports, or install manually a few tools like cmake, flex, bison. Afterwards, you could run the dependency download and build scripts in the csound/dependencies folder. (Will need to run the building script with sudo to install the deps to /usr/local). Then use cmake to build with XCode or command-line. That's a sort of quick version of it. It's been a long while since I re-setup a build from scratch though and I've largely been relying on my old Macbook's pre-existing setup for years now. On Thu, Feb 1, 2018 at 3:32 PM, Victor Lazzarini wrote: > The scripts in dependencies are designed to install things directly without having to use brew, if you want to try. > ======================== > Prof. 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 1 Feb 2018, at 20:24, Ben McAllister wrote: >> >> I would use brew in favor of macports too. Would it be useful for me to write up my mac build steps and add them to build.md, since right now the build instructions point to a brew tap - not the git repo - for pulling source. Steven - straighten me out if I'm wrong on my understanding here. >> >> Also - is there still a csound dev list separate from this one? >> >> On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell wrote: >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. >> Thanks! >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini : >> > >> > I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. >> > >> > Victor Lazzarini >> > Dean of Arts, Celtic Studies, and Philosophy >> > Maynooth University >> > Ireland >> > >> >> On 1 Feb 2018, at 18:48, Anders Genell wrote: >> >> >> >> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? >> >> >> >> Regards, >> >> Anders >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : >> >>> >> >>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >> >>> it worked. >> >>> ======================== >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >> >>>> >> >>>> I don't use OSX much these days, but I when I do, I usually work on >> >>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >> >>>> create an XCode project. >> >>>> >> >>>> Within XCode, I would use the built-in debugger and profile with >> >>>> Instruments. One can use cmd-shift-, and setup a number of different >> >>>> command-line args to run with different settings, different, csds, and >> >>>> switch between them pretty easily. I would also maintain a separate >> >>>> command-line build via make or ninja and would typically use that one >> >>>> for general building/running unit tests/installing. I probably used >> >>>> gdb for quick debug sessions and vim for quick edits, and used XCode >> >>>> for trickier debugging/profiling. >> >>>> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >> >>>>> Using CMake you can create an Xcode project from the Csound sources which >> >>>>> you can use to develop/debug Csound using Xcode. >> >>>>> >> >>>>> git clone https://github.com/csound/csound.git >> >>>>> cd csound >> >>>>> mkdir Xcode >> >>>>> cd Xcode >> >>>>> cmake -G Xcode .. >> >>>>> >> >>>>> >> >>>>> Best, >> >>>>> Ed >> >>>>> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >> >>>>> >> >>>>> Hi All - this question was buried in a previous message, but pulling it out >> >>>>> separately hoping to get a response from csound developers: >> >>>>> >> >>>>> If you're working on a Mac, I'm curious what you're using for a >> >>>>> development/debugging environment. Did you create an xcodeproj for Mac >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >> >>>>> >> >>>>> As an old csounder and experienced developer (been at both since 96 or so), >> >>>>> I'd like to get more familiar with this tool I love and maybe contribute. >> >>>>> >> >>>>> Thanks in advance, >> >>>>> b >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >> >>>>> be posted here >> >>>>> >> >>>>> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >> >>>>> be posted here >> >>>> >> >>>> Csound mailing list >> >>>> Csound@listserv.heanet.ie >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>>> Send bugs reports to >> >>>> https://github.com/csound/csound/issues >> >>>> Discussions of bugs and features can be posted here >> >>> >> >>> Csound mailing list >> >>> Csound@listserv.heanet.ie >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>> Send bugs reports to >> >>> https://github.com/csound/csound/issues >> >>> Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> >> >> >> -- >> Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 >> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here > > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 21:50
From	John ff
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Try csound-devel@listserv.heanet.ie ⁣Sent from TypeApp On Feb 1, 2018, 20:25, at 20:25, Ben McAllister wrote: >I would use brew in favor of macports too. Would it be useful for me to >write up my mac build steps and add them to build.md, since right now >the >build instructions point to a brew tap - not the git repo - for pulling >source. Steven - straighten me out if I'm wrong on my understanding >here. > >Also - is there still a csound dev list separate from this one? > >On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell > >wrote: > >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get a >chance. >> Thanks! >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini >: >> > >> > I’d say no. The toolchain is given by xcode. Csound has scripts to >> download and build the key dependencies. >> > >> > Victor Lazzarini >> > Dean of Arts, Celtic Studies, and Philosophy >> > Maynooth University >> > Ireland >> > >> >> On 1 Feb 2018, at 18:48, Anders Genell >wrote: >> >> >> >> I would like to be able to build on OS X occasionally, using >command >> line only. But I don’t know how to install a proper tool chain. Is >macports >> the way to go? >> >> >> >> Regards, >> >> Anders >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini >: >> >>> >> >>> I work on OSX, but strictly command line and emacs. Debugging >from the >> command-line. I used to use valgrind when >> >>> it worked. >> >>> ======================== >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >> >>>> >> >>>> I don't use OSX much these days, but I when I do, I usually work >on >> >>>> Csound via XCode. I pretty much do the same steps as Ed >mentioned to >> >>>> create an XCode project. >> >>>> >> >>>> Within XCode, I would use the built-in debugger and profile with >> >>>> Instruments. One can use cmd-shift-, and setup a number of >different >> >>>> command-line args to run with different settings, different, >csds, and >> >>>> switch between them pretty easily. I would also maintain a >separate >> >>>> command-line build via make or ninja and would typically use >that one >> >>>> for general building/running unit tests/installing. I probably >used >> >>>> gdb for quick debug sessions and vim for quick edits, and used >XCode >> >>>> for trickier debugging/profiling. >> >>>> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello < >> phasereset@gmail.com> wrote: >> >>>>> Using CMake you can create an Xcode project from the Csound >sources >> which >> >>>>> you can use to develop/debug Csound using Xcode. >> >>>>> >> >>>>> git clone https://github.com/csound/csound.git >> >>>>> cd csound >> >>>>> mkdir Xcode >> >>>>> cd Xcode >> >>>>> cmake -G Xcode .. >> >>>>> >> >>>>> >> >>>>> Best, >> >>>>> Ed >> >>>>> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister >wrote: >> >>>>> >> >>>>> Hi All - this question was buried in a previous message, but >pulling >> it out >> >>>>> separately hoping to get a response from csound developers: >> >>>>> >> >>>>> If you're working on a Mac, I'm curious what you're using for a >> >>>>> development/debugging environment. Did you create an xcodeproj >for >> Mac >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? >Is >> Mac in >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd >maybe? >> >>>>> >> >>>>> As an old csounder and experienced developer (been at both >since 96 >> or so), >> >>>>> I'd like to get more familiar with this tool I love and maybe >> contribute. >> >>>>> >> >>>>> Thanks in advance, >> >>>>> b >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and >> features can >> >>>>> be posted here >> >>>>> >> >>>>> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and >> features can >> >>>>> be posted here >> >>>> >> >>>> Csound mailing list >> >>>> Csound@listserv.heanet.ie >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>>> Send bugs reports to >> >>>> https://github.com/csound/csound/issues >> >>>> Discussions of bugs and features can be posted here >> >>> >> >>> Csound mailing list >> >>> Csound@listserv.heanet.ie >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>> Send bugs reports to >> >>> https://github.com/csound/csound/issues >> >>> Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > > >-- >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: >206.849.3183 > >Csound mailing list >Csound@listserv.heanet.ie >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >Send bugs reports to > https://github.com/csound/csound/issues >Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 22:04
From	Victor Lazzarini
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	I have changed the dependencies script to default to installing locally ($HOME) instead of /usr/local so that it can be built without sudo. CMAKE_INSTALL_PREFIX can also be used to install Csound locally so that no sudo should be needed if one wants it. The script can also be used to install in /usr/local by changing the PREFIX variable in it. But then sudo is needed. ======================== Prof. 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 1 Feb 2018, at 20:44, Steven Yi wrote: > > Yeah the build.md needs to be changed. Homebrew still works for a > complete build last I checked. > > For a more manual local build, you could use Homebrew, macports, or > install manually a few tools like cmake, flex, bison. Afterwards, you > could run the dependency download and build scripts in the > csound/dependencies folder. (Will need to run the building script > with sudo to install the deps to /usr/local). Then use cmake to build > with XCode or command-line. > > That's a sort of quick version of it. It's been a long while since I > re-setup a build from scratch though and I've largely been relying on > my old Macbook's pre-existing setup for years now. > > On Thu, Feb 1, 2018 at 3:32 PM, Victor Lazzarini wrote: >> The scripts in dependencies are designed to install things directly without having to use brew, if you want to try. >> ======================== >> Prof. 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 1 Feb 2018, at 20:24, Ben McAllister wrote: >>> >>> I would use brew in favor of macports too. Would it be useful for me to write up my mac build steps and add them to build.md, since right now the build instructions point to a brew tap - not the git repo - for pulling source. Steven - straighten me out if I'm wrong on my understanding here. >>> >>> Also - is there still a csound dev list separate from this one? >>> >>> On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell wrote: >>> Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. >>> Thanks! >>> >>> >>> >>>> 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini : >>>> >>>> I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. >>>> >>>> Victor Lazzarini >>>> Dean of Arts, Celtic Studies, and Philosophy >>>> Maynooth University >>>> Ireland >>>> >>>>> On 1 Feb 2018, at 18:48, Anders Genell wrote: >>>>> >>>>> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? >>>>> >>>>> Regards, >>>>> Anders >>>>> >>>>>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini : >>>>>> >>>>>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >>>>>> it worked. >>>>>> ======================== >>>>>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi wrote: >>>>>>> >>>>>>> I don't use OSX much these days, but I when I do, I usually work on >>>>>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >>>>>>> create an XCode project. >>>>>>> >>>>>>> Within XCode, I would use the built-in debugger and profile with >>>>>>> Instruments. One can use cmd-shift-, and setup a number of different >>>>>>> command-line args to run with different settings, different, csds, and >>>>>>> switch between them pretty easily. I would also maintain a separate >>>>>>> command-line build via make or ninja and would typically use that one >>>>>>> for general building/running unit tests/installing. I probably used >>>>>>> gdb for quick debug sessions and vim for quick edits, and used XCode >>>>>>> for trickier debugging/profiling. >>>>>>> >>>>>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello wrote: >>>>>>>> Using CMake you can create an Xcode project from the Csound sources which >>>>>>>> you can use to develop/debug Csound using Xcode. >>>>>>>> >>>>>>>> git clone https://github.com/csound/csound.git >>>>>>>> cd csound >>>>>>>> mkdir Xcode >>>>>>>> cd Xcode >>>>>>>> cmake -G Xcode .. >>>>>>>> >>>>>>>> >>>>>>>> Best, >>>>>>>> Ed >>>>>>>> >>>>>>>> On 1 Feb 2018, at 09:23, Ben McAllister wrote: >>>>>>>> >>>>>>>> Hi All - this question was buried in a previous message, but pulling it out >>>>>>>> separately hoping to get a response from csound developers: >>>>>>>> >>>>>>>> If you're working on a Mac, I'm curious what you're using for a >>>>>>>> development/debugging environment. Did you create an xcodeproj for Mac >>>>>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >>>>>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >>>>>>>> >>>>>>>> As an old csounder and experienced developer (been at both since 96 or so), >>>>>>>> I'd like to get more familiar with this tool I love and maybe contribute. >>>>>>>> >>>>>>>> Thanks in advance, >>>>>>>> b >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>>>>> be posted here >>>>>>>> >>>>>>>> >>>>>>>> Csound mailing list Csound@listserv.heanet.ie >>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >>>>>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >>>>>>>> be posted here >>>>>>> >>>>>>> Csound mailing list >>>>>>> Csound@listserv.heanet.ie >>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>>> Send bugs reports to >>>>>>> https://github.com/csound/csound/issues >>>>>>> Discussions of bugs and features can be posted here >>>>>> >>>>>> Csound mailing list >>>>>> Csound@listserv.heanet.ie >>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>>> Send bugs reports to >>>>>> https://github.com/csound/csound/issues >>>>>> Discussions of bugs and features can be posted here >>>>> >>>>> Csound mailing list >>>>> Csound@listserv.heanet.ie >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>>> Send bugs reports to >>>>> https://github.com/csound/csound/issues >>>>> Discussions of bugs and features can be posted here >>>> >>>> Csound mailing list >>>> Csound@listserv.heanet.ie >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>>> Send bugs reports to >>>> https://github.com/csound/csound/issues >>>> Discussions of bugs and features can be posted here >>> >>> Csound mailing list >>> Csound@listserv.heanet.ie >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> >>> >>> >>> -- >>> Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 >>> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here >> >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date

2018-02-01 23:32

From

Ben McAllister

Subject

Re: [Csnd] Advice for Developing/Debugging Csound on Mac

Thanks - I got a 550 back from the mail server, though:

The response was:

550 unknown user

Final-Recipient: rfc822; csound-devel@listserv.heanet.ie
Action: failed
Status: 5.0.0
Remote-MTA: dns; listserv.heanet.ie. (2001:770:18:2::c101:db34, the server for
the domain listserv.heanet.ie.)
Diagnostic-Code: smtp; 550 unknown user
Last-Attempt-Date: Thu, 01 Feb 2018 15:28:02 -0800 (PST)

---------- Forwarded message ----------
From: Ben McAllister <benmca@gmail.com>
To: csound-devel@listserv.heanet.ie
Cc:
Bcc:
Date: Thu, 1 Feb 2018 15:28:00 -0800
Subject: subscribe

On Thu, Feb 1, 2018 at 1:50 PM, John ff <jpff@codemist.co.uk> wrote:

Try csound-devel@listserv.heanet.ie

⁣Sent from TypeApp

On Feb 1, 2018, 20:25, at 20:25, Ben McAllister <benmca@GMAIL.COM> wrote:
>I would use brew in favor of macports too. Would it be useful for me to
>write up my mac build steps and add them to build.md, since right now
>the
>build instructions point to a brew tap - not the git repo - for pulling
>source. Steven - straighten me out if I'm wrong on my understanding
>here.
>
>Also - is there still a csound dev list separate from this one?
>
>On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell
><anders.genell@gmail.com>
>wrote:
>
>> Ah, ok! I haven’t tried those, but I’ll give that a go when I get a
>chance.
>> Thanks!
>>
>>
>>
>> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini
><Victor.Lazzarini@MU.IE>:
>> >
>> > I’d say no. The toolchain is given by xcode. Csound has scripts to
>> download and build the key dependencies.
>> >
>> > Victor Lazzarini
>> > Dean of Arts, Celtic Studies, and Philosophy
>> > Maynooth University
>> > Ireland
>> >
>> >> On 1 Feb 2018, at 18:48, Anders Genell <anders.genell@GMAIL.COM>
>wrote:
>> >>
>> >> I would like to be able to build on OS X occasionally, using
>command
>> line only. But I don’t know how to install a proper tool chain. Is
>macports
>> the way to go?
>> >>
>> >> Regards,
>> >> Anders
>> >>
>> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini
><Victor.Lazzarini@MU.IE>:
>> >>>
>> >>> I work on OSX, but strictly command line and emacs. Debugging
>from the
>> command-line. I used to use valgrind when
>> >>> it worked.
>> >>> ========================
>> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi <stevenyi@gmail.com> wrote:
>> >>>>
>> >>>> I don't use OSX much these days, but I when I do, I usually work
>on
>> >>>> Csound via XCode. I pretty much do the same steps as Ed
>mentioned to
>> >>>> create an XCode project.
>> >>>>
>> >>>> Within XCode, I would use the built-in debugger and profile with
>> >>>> Instruments. One can use cmd-shift-, and setup a number of
>different
>> >>>> command-line args to run with different settings, different,
>csds, and
>> >>>> switch between them pretty easily. I would also maintain a
>separate
>> >>>> command-line build via make or ninja and would typically use
>that one
>> >>>> for general building/running unit tests/installing. I probably
>used
>> >>>> gdb for quick debug sessions and vim for quick edits, and used
>XCode
>> >>>> for trickier debugging/profiling.
>> >>>>
>> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello <
>> phasereset@gmail.com> wrote:
>> >>>>> Using CMake you can create an Xcode project from the Csound
>sources
>> which
>> >>>>> you can use to develop/debug Csound using Xcode.
>> >>>>>
>> >>>>> git clone https://github.com/csound/csound.git
>> >>>>> cd csound
>> >>>>> mkdir Xcode
>> >>>>> cd Xcode
>> >>>>> cmake -G Xcode ..
>> >>>>>
>> >>>>>
>> >>>>> Best,
>> >>>>> Ed
>> >>>>>
>> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister <benmca@GMAIL.COM>
>wrote:
>> >>>>>
>> >>>>> Hi All - this question was buried in a previous message, but
>pulling
>> it out
>> >>>>> separately hoping to get a response from csound developers:
>> >>>>>
>> >>>>> If you're working on a Mac, I'm curious what you're using for a
>> >>>>> development/debugging environment. Did you create an xcodeproj
>for
>> Mac
>> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains?
>Is
>> Mac in
>> >>>>> the minority, and are more devs on Linux using.. gdb and ddd
>maybe?
>> >>>>>
>> >>>>> As an old csounder and experienced developer (been at both
>since 96
>> or so),
>> >>>>> I'd like to get more familiar with this tool I love and maybe
>> contribute.
>> >>>>>
>> >>>>> Thanks in advance,
>> >>>>> b
>> >>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>reports to
>> >>>>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can
>> >>>>> be posted here
>> >>>>>
>> >>>>>
>> >>>>> Csound mailing list Csound@listserv.heanet.ie
>> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs
>reports to
>> >>>>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can
>> >>>>> be posted here
>> >>>>
>> >>>> Csound mailing list
>> >>>> Csound@listserv.heanet.ie
>> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>>> Send bugs reports to
>> >>>> https://github.com/csound/csound/issues
>> >>>> Discussions of bugs and features can be posted here
>> >>>
>> >>> Csound mailing list
>> >>> Csound@listserv.heanet.ie
>> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >>> Send bugs reports to
>> >>> https://github.com/csound/csound/issues
>> >>> Discussions of bugs and features can be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >> https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> > Csound mailing list
>> > Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> > Send bugs reports to
>> > https://github.com/csound/csound/issues
>> > Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>> https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>
>
>
>--
>Ben McAllister | listenfaster.com | @listenfaster | tuktuband.com | c:
>206.849.3183
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
> https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here

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

Ben McAllister | listenfaster.com | @listenfaster | tuktuband.com | c: 206.849.3183

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

Date	2018-02-01 23:38
From	John ff
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Sorry try csound-dev@listserv.heanet.ie ⁣Sent from TypeApp On Feb 1, 2018, 23:33, at 23:33, Ben McAllister wrote: >Thanks - I got a 550 back from the mail server, though: > >The response was: > >550 unknown user > >Final-Recipient: rfc822; csound-devel@listserv.heanet.ie >Action: failed >Status: 5.0.0 >Remote-MTA: dns; listserv.heanet.ie. (2001:770:18:2::c101:db34, the >server >for > the domain listserv.heanet.ie.) >Diagnostic-Code: smtp; 550 unknown user >Last-Attempt-Date: Thu, 01 Feb 2018 15:28:02 -0800 (PST) > > >---------- Forwarded message ---------- >From: Ben McAllister >To: csound-devel@listserv.heanet.ie >Cc: >Bcc: >Date: Thu, 1 Feb 2018 15:28:00 -0800 >Subject: subscribe >subscribe > > >On Thu, Feb 1, 2018 at 1:50 PM, John ff wrote: > >> Try csound-devel@listserv.heanet.ie >> >> ⁣Sent from TypeApp >> >> On Feb 1, 2018, 20:25, at 20:25, Ben McAllister >wrote: >> >I would use brew in favor of macports too. Would it be useful for me >to >> >write up my mac build steps and add them to build.md, since right >now >> >the >> >build instructions point to a brew tap - not the git repo - for >pulling >> >source. Steven - straighten me out if I'm wrong on my understanding >> >here. >> > >> >Also - is there still a csound dev list separate from this one? >> > >> >On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell >> > >> >wrote: >> > >> >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get >a >> >chance. >> >> Thanks! >> >> >> >> >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini >> >: >> >> > >> >> > I’d say no. The toolchain is given by xcode. Csound has scripts >to >> >> download and build the key dependencies. >> >> > >> >> > Victor Lazzarini >> >> > Dean of Arts, Celtic Studies, and Philosophy >> >> > Maynooth University >> >> > Ireland >> >> > >> >> >> On 1 Feb 2018, at 18:48, Anders Genell > >> >wrote: >> >> >> >> >> >> I would like to be able to build on OS X occasionally, using >> >command >> >> line only. But I don’t know how to install a proper tool chain. Is >> >macports >> >> the way to go? >> >> >> >> >> >> Regards, >> >> >> Anders >> >> >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini >> >: >> >> >>> >> >> >>> I work on OSX, but strictly command line and emacs. Debugging >> >from the >> >> command-line. I used to use valgrind when >> >> >>> it worked. >> >> >>> ======================== >> >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi >wrote: >> >> >>>> >> >> >>>> I don't use OSX much these days, but I when I do, I usually >work >> >on >> >> >>>> Csound via XCode. I pretty much do the same steps as Ed >> >mentioned to >> >> >>>> create an XCode project. >> >> >>>> >> >> >>>> Within XCode, I would use the built-in debugger and profile >with >> >> >>>> Instruments. One can use cmd-shift-, and setup a number of >> >different >> >> >>>> command-line args to run with different settings, different, >> >csds, and >> >> >>>> switch between them pretty easily. I would also maintain a >> >separate >> >> >>>> command-line build via make or ninja and would typically use >> >that one >> >> >>>> for general building/running unit tests/installing. I >probably >> >used >> >> >>>> gdb for quick debug sessions and vim for quick edits, and >used >> >XCode >> >> >>>> for trickier debugging/profiling. >> >> >>>> >> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello < >> >> phasereset@gmail.com> wrote: >> >> >>>>> Using CMake you can create an Xcode project from the Csound >> >sources >> >> which >> >> >>>>> you can use to develop/debug Csound using Xcode. >> >> >>>>> >> >> >>>>> git clone https://github.com/csound/csound.git >> >> >>>>> cd csound >> >> >>>>> mkdir Xcode >> >> >>>>> cd Xcode >> >> >>>>> cmake -G Xcode .. >> >> >>>>> >> >> >>>>> >> >> >>>>> Best, >> >> >>>>> Ed >> >> >>>>> >> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister >> >wrote: >> >> >>>>> >> >> >>>>> Hi All - this question was buried in a previous message, but >> >pulling >> >> it out >> >> >>>>> separately hoping to get a response from csound developers: >> >> >>>>> >> >> >>>>> If you're working on a Mac, I'm curious what you're using >for a >> >> >>>>> development/debugging environment. Did you create an >xcodeproj >> >for >> >> Mac >> >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from >JetBrains? >> >Is >> >> Mac in >> >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd >> >maybe? >> >> >>>>> >> >> >>>>> As an old csounder and experienced developer (been at both >> >since 96 >> >> or so), >> >> >>>>> I'd like to get more familiar with this tool I love and >maybe >> >> contribute. >> >> >>>>> >> >> >>>>> Thanks in advance, >> >> >>>>> b >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> >reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> >> features can >> >> >>>>> be posted here >> >> >>>>> >> >> >>>>> >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> >reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> >> features can >> >> >>>>> be posted here >> >> >>>> >> >> >>>> Csound mailing list >> >> >>>> Csound@listserv.heanet.ie >> >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>>> Send bugs reports to >> >> >>>> https://github.com/csound/csound/issues >> >> >>>> Discussions of bugs and features can be posted here >> >> >>> >> >> >>> Csound mailing list >> >> >>> Csound@listserv.heanet.ie >> >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>> Send bugs reports to >> >> >>> https://github.com/csound/csound/issues >> >> >>> Discussions of bugs and features can be posted here >> >> >> >> >> >> Csound mailing list >> >> >> Csound@listserv.heanet.ie >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> Send bugs reports to >> >> >> https://github.com/csound/csound/issues >> >> >> Discussions of bugs and features can be posted here >> >> > >> >> > Csound mailing list >> >> > Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> > Send bugs reports to >> >> > https://github.com/csound/csound/issues >> >> > Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> >> >> > >> > >> > >> >-- >> >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| >c: >> >206.849.3183 >> > >> >Csound mailing list >> >Csound@listserv.heanet.ie >> >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >Send bugs reports to >> > https://github.com/csound/csound/issues >> >Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > > >-- >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: >206.849.3183 > >Csound mailing list >Csound@listserv.heanet.ie >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >Send bugs reports to > https://github.com/csound/csound/issues >Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-01 23:38
From	John ff
Subject	Re: [Csnd-dev] [Csnd] Advice for Developing/Debugging Csound on Mac
	Sorry try csound-dev@listserv.heanet.ie ⁣Sent from TypeApp On Feb 1, 2018, 23:33, at 23:33, Ben McAllister wrote: >Thanks - I got a 550 back from the mail server, though: > >The response was: > >550 unknown user > >Final-Recipient: rfc822; csound-devel@listserv.heanet.ie >Action: failed >Status: 5.0.0 >Remote-MTA: dns; listserv.heanet.ie. (2001:770:18:2::c101:db34, the >server >for > the domain listserv.heanet.ie.) >Diagnostic-Code: smtp; 550 unknown user >Last-Attempt-Date: Thu, 01 Feb 2018 15:28:02 -0800 (PST) > > >---------- Forwarded message ---------- >From: Ben McAllister >To: csound-devel@listserv.heanet.ie >Cc: >Bcc: >Date: Thu, 1 Feb 2018 15:28:00 -0800 >Subject: subscribe >subscribe > > >On Thu, Feb 1, 2018 at 1:50 PM, John ff wrote: > >> Try csound-devel@listserv.heanet.ie >> >> ⁣Sent from TypeApp >> >> On Feb 1, 2018, 20:25, at 20:25, Ben McAllister >wrote: >> >I would use brew in favor of macports too. Would it be useful for me >to >> >write up my mac build steps and add them to build.md, since right >now >> >the >> >build instructions point to a brew tap - not the git repo - for >pulling >> >source. Steven - straighten me out if I'm wrong on my understanding >> >here. >> > >> >Also - is there still a csound dev list separate from this one? >> > >> >On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell >> > >> >wrote: >> > >> >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get >a >> >chance. >> >> Thanks! >> >> >> >> >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini >> >: >> >> > >> >> > I’d say no. The toolchain is given by xcode. Csound has scripts >to >> >> download and build the key dependencies. >> >> > >> >> > Victor Lazzarini >> >> > Dean of Arts, Celtic Studies, and Philosophy >> >> > Maynooth University >> >> > Ireland >> >> > >> >> >> On 1 Feb 2018, at 18:48, Anders Genell > >> >wrote: >> >> >> >> >> >> I would like to be able to build on OS X occasionally, using >> >command >> >> line only. But I don’t know how to install a proper tool chain. Is >> >macports >> >> the way to go? >> >> >> >> >> >> Regards, >> >> >> Anders >> >> >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini >> >: >> >> >>> >> >> >>> I work on OSX, but strictly command line and emacs. Debugging >> >from the >> >> command-line. I used to use valgrind when >> >> >>> it worked. >> >> >>> ======================== >> >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi >wrote: >> >> >>>> >> >> >>>> I don't use OSX much these days, but I when I do, I usually >work >> >on >> >> >>>> Csound via XCode. I pretty much do the same steps as Ed >> >mentioned to >> >> >>>> create an XCode project. >> >> >>>> >> >> >>>> Within XCode, I would use the built-in debugger and profile >with >> >> >>>> Instruments. One can use cmd-shift-, and setup a number of >> >different >> >> >>>> command-line args to run with different settings, different, >> >csds, and >> >> >>>> switch between them pretty easily. I would also maintain a >> >separate >> >> >>>> command-line build via make or ninja and would typically use >> >that one >> >> >>>> for general building/running unit tests/installing. I >probably >> >used >> >> >>>> gdb for quick debug sessions and vim for quick edits, and >used >> >XCode >> >> >>>> for trickier debugging/profiling. >> >> >>>> >> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello < >> >> phasereset@gmail.com> wrote: >> >> >>>>> Using CMake you can create an Xcode project from the Csound >> >sources >> >> which >> >> >>>>> you can use to develop/debug Csound using Xcode. >> >> >>>>> >> >> >>>>> git clone https://github.com/csound/csound.git >> >> >>>>> cd csound >> >> >>>>> mkdir Xcode >> >> >>>>> cd Xcode >> >> >>>>> cmake -G Xcode .. >> >> >>>>> >> >> >>>>> >> >> >>>>> Best, >> >> >>>>> Ed >> >> >>>>> >> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister >> >wrote: >> >> >>>>> >> >> >>>>> Hi All - this question was buried in a previous message, but >> >pulling >> >> it out >> >> >>>>> separately hoping to get a response from csound developers: >> >> >>>>> >> >> >>>>> If you're working on a Mac, I'm curious what you're using >for a >> >> >>>>> development/debugging environment. Did you create an >xcodeproj >> >for >> >> Mac >> >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from >JetBrains? >> >Is >> >> Mac in >> >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd >> >maybe? >> >> >>>>> >> >> >>>>> As an old csounder and experienced developer (been at both >> >since 96 >> >> or so), >> >> >>>>> I'd like to get more familiar with this tool I love and >maybe >> >> contribute. >> >> >>>>> >> >> >>>>> Thanks in advance, >> >> >>>>> b >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> >reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> >> features can >> >> >>>>> be posted here >> >> >>>>> >> >> >>>>> >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> >reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> >> features can >> >> >>>>> be posted here >> >> >>>> >> >> >>>> Csound mailing list >> >> >>>> Csound@listserv.heanet.ie >> >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>>> Send bugs reports to >> >> >>>> https://github.com/csound/csound/issues >> >> >>>> Discussions of bugs and features can be posted here >> >> >>> >> >> >>> Csound mailing list >> >> >>> Csound@listserv.heanet.ie >> >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>> Send bugs reports to >> >> >>> https://github.com/csound/csound/issues >> >> >>> Discussions of bugs and features can be posted here >> >> >> >> >> >> Csound mailing list >> >> >> Csound@listserv.heanet.ie >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> Send bugs reports to >> >> >> https://github.com/csound/csound/issues >> >> >> Discussions of bugs and features can be posted here >> >> > >> >> > Csound mailing list >> >> > Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> > Send bugs reports to >> >> > https://github.com/csound/csound/issues >> >> > Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> >> >> > >> > >> > >> >-- >> >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| >c: >> >206.849.3183 >> > >> >Csound mailing list >> >Csound@listserv.heanet.ie >> >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >Send bugs reports to >> > https://github.com/csound/csound/issues >> >Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > > >-- >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: >206.849.3183 > >Csound mailing list >Csound@listserv.heanet.ie >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >Send bugs reports to > https://github.com/csound/csound/issues >Discussions of bugs and feat

Date	2018-02-02 00:11
From	Ben McAllister
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	Thanks again for all the help - I'm up and running. The catch for me, running OSX 10.13 and the latest xcode, was an issue in the generated xcodeproj - I'll detail it in my first PR :) I just joined the dev list (thanks jpff) - is there a best practices guide or anything to lay out expectations for PRs? Looks like the contribute page is still a WIP: http://csound.com/contribute.html Thanks! b On Thu, Feb 1, 2018 at 12:44 PM, Steven Yi <stevenyi@gmail.com> wrote: Yeah the build.md needs to be changed. Homebrew still works for a complete build last I checked. For a more manual local build, you could use Homebrew, macports, or install manually a few tools like cmake, flex, bison. Afterwards, you could run the dependency download and build scripts in the csound/dependencies folder. (Will need to run the building script with sudo to install the deps to /usr/local). Then use cmake to build with XCode or command-line. That's a sort of quick version of it. It's been a long while since I re-setup a build from scratch though and I've largely been relying on my old Macbook's pre-existing setup for years now. On Thu, Feb 1, 2018 at 3:32 PM, Victor Lazzarini <Victor.Lazzarini@mu.ie> wrote: > The scripts in dependencies are designed to install things directly without having to use brew, if you want to try. > ======================== > Prof. 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 1 Feb 2018, at 20:24, Ben McAllister <benmca@GMAIL.COM> wrote: >> >> I would use brew in favor of macports too. Would it be useful for me to write up my mac build steps and add them to build.md, since right now the build instructions point to a brew tap - not the git repo - for pulling source. Steven - straighten me out if I'm wrong on my understanding here. >> >> Also - is there still a csound dev list separate from this one? >> >> On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell <anders.genell@gmail.com> wrote: >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get a chance. >> Thanks! >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini <Victor.Lazzarini@MU.IE>: >> > >> > I’d say no. The toolchain is given by xcode. Csound has scripts to download and build the key dependencies. >> > >> > Victor Lazzarini >> > Dean of Arts, Celtic Studies, and Philosophy >> > Maynooth University >> > Ireland >> > >> >> On 1 Feb 2018, at 18:48, Anders Genell <anders.genell@GMAIL.COM> wrote: >> >> >> >> I would like to be able to build on OS X occasionally, using command line only. But I don’t know how to install a proper tool chain. Is macports the way to go? >> >> >> >> Regards, >> >> Anders >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini <Victor.Lazzarini@MU.IE>: >> >>> >> >>> I work on OSX, but strictly command line and emacs. Debugging from the command-line. I used to use valgrind when >> >>> it worked. >> >>> ======================== >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi <stevenyi@gmail.com> wrote: >> >>>> >> >>>> I don't use OSX much these days, but I when I do, I usually work on >> >>>> Csound via XCode. I pretty much do the same steps as Ed mentioned to >> >>>> create an XCode project. >> >>>> >> >>>> Within XCode, I would use the built-in debugger and profile with >> >>>> Instruments. One can use cmd-shift-, and setup a number of different >> >>>> command-line args to run with different settings, different, csds, and >> >>>> switch between them pretty easily. I would also maintain a separate >> >>>> command-line build via make or ninja and would typically use that one >> >>>> for general building/running unit tests/installing. I probably used >> >>>> gdb for quick debug sessions and vim for quick edits, and used XCode >> >>>> for trickier debugging/profiling. >> >>>> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello <phasereset@gmail.com> wrote: >> >>>>> Using CMake you can create an Xcode project from the Csound sources which >> >>>>> you can use to develop/debug Csound using Xcode. >> >>>>> >> >>>>> git clone https://github.com/csound/csound.git >> >>>>> cd csound >> >>>>> mkdir Xcode >> >>>>> cd Xcode >> >>>>> cmake -G Xcode .. >> >>>>> >> >>>>> >> >>>>> Best, >> >>>>> Ed >> >>>>> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister <benmca@GMAIL.COM> wrote: >> >>>>> >> >>>>> Hi All - this question was buried in a previous message, but pulling it out >> >>>>> separately hoping to get a response from csound developers: >> >>>>> >> >>>>> If you're working on a Mac, I'm curious what you're using for a >> >>>>> development/debugging environment. Did you create an xcodeproj for Mac >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from JetBrains? Is Mac in >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd maybe? >> >>>>> >> >>>>> As an old csounder and experienced developer (been at both since 96 or so), >> >>>>> I'd like to get more familiar with this tool I love and maybe contribute. >> >>>>> >> >>>>> Thanks in advance, >> >>>>> b >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >> >>>>> be posted here >> >>>>> >> >>>>> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> >>>>> https://github.com/csound/csound/issues Discussions of bugs and features can >> >>>>> be posted here >> >>>> >> >>>> Csound mailing list >> >>>> Csound@listserv.heanet.ie >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>>> Send bugs reports to >> >>>> https://github.com/csound/csound/issues >> >>>> Discussions of bugs and features can be posted here >> >>> >> >>> Csound mailing list >> >>> Csound@listserv.heanet.ie >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >>> Send bugs reports to >> >>> https://github.com/csound/csound/issues >> >>> Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> >> >> >> -- >> Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 >> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here > > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here -- Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: 206.849.3183 Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-02-02 00:44
From	John ff
Subject	Re: [Csnd] Advice for Developing/Debugging Csound on Mac
	There is a file on github repository with a name like Submitting. On a tablet at present and the computers are turned off. More tomorrow. ⁣Sent from TypeApp On Feb 2, 2018, 00:12, at 00:12, Ben McAllister wrote: >Thanks again for all the help - I'm up and running. > >The catch for me, running OSX 10.13 and the latest xcode, was an issue >in >the generated xcodeproj - I'll detail it in my first PR :) > >I just joined the dev list (thanks jpff) - is there a best practices >guide >or anything to lay out expectations for PRs? Looks like the contribute >page >is still a WIP: http://csound.com/contribute.html > >Thanks! >b > >On Thu, Feb 1, 2018 at 12:44 PM, Steven Yi wrote: > >> Yeah the build.md needs to be changed. Homebrew still works for a >> complete build last I checked. >> >> For a more manual local build, you could use Homebrew, macports, or >> install manually a few tools like cmake, flex, bison. Afterwards, you >> could run the dependency download and build scripts in the >> csound/dependencies folder. (Will need to run the building script >> with sudo to install the deps to /usr/local). Then use cmake to build >> with XCode or command-line. >> >> That's a sort of quick version of it. It's been a long while since I >> re-setup a build from scratch though and I've largely been relying on >> my old Macbook's pre-existing setup for years now. >> >> On Thu, Feb 1, 2018 at 3:32 PM, Victor Lazzarini > >> wrote: >> > The scripts in dependencies are designed to install things directly >> without having to use brew, if you want to try. >> > ======================== >> > Prof. 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 1 Feb 2018, at 20:24, Ben McAllister wrote: >> >> >> >> I would use brew in favor of macports too. Would it be useful for >me to >> write up my mac build steps and add them to build.md, since right now >the >> build instructions point to a brew tap - not the git repo - for >pulling >> source. Steven - straighten me out if I'm wrong on my understanding >here. >> >> >> >> Also - is there still a csound dev list separate from this one? >> >> >> >> On Thu, Feb 1, 2018 at 11:21 AM, Anders Genell > >> wrote: >> >> Ah, ok! I haven’t tried those, but I’ll give that a go when I get >a >> chance. >> >> Thanks! >> >> >> >> >> >> >> >> > 1 feb. 2018 kl. 19:58 skrev Victor Lazzarini >> >: >> >> > >> >> > I’d say no. The toolchain is given by xcode. Csound has scripts >to >> download and build the key dependencies. >> >> > >> >> > Victor Lazzarini >> >> > Dean of Arts, Celtic Studies, and Philosophy >> >> > Maynooth University >> >> > Ireland >> >> > >> >> >> On 1 Feb 2018, at 18:48, Anders Genell > >> wrote: >> >> >> >> >> >> I would like to be able to build on OS X occasionally, using >command >> line only. But I don’t know how to install a proper tool chain. Is >macports >> the way to go? >> >> >> >> >> >> Regards, >> >> >> Anders >> >> >> >> >> >>> 1 feb. 2018 kl. 19:33 skrev Victor Lazzarini < >> Victor.Lazzarini@MU.IE>: >> >> >>> >> >> >>> I work on OSX, but strictly command line and emacs. Debugging >from >> the command-line. I used to use valgrind when >> >> >>> it worked. >> >> >>> ======================== >> >> >>> Prof. 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 1 Feb 2018, at 17:53, Steven Yi >wrote: >> >> >>>> >> >> >>>> I don't use OSX much these days, but I when I do, I usually >work on >> >> >>>> Csound via XCode. I pretty much do the same steps as Ed >mentioned >> to >> >> >>>> create an XCode project. >> >> >>>> >> >> >>>> Within XCode, I would use the built-in debugger and profile >with >> >> >>>> Instruments. One can use cmd-shift-, and setup a number of >> different >> >> >>>> command-line args to run with different settings, different, >csds, >> and >> >> >>>> switch between them pretty easily. I would also maintain a >separate >> >> >>>> command-line build via make or ninja and would typically use >that >> one >> >> >>>> for general building/running unit tests/installing. I >probably >> used >> >> >>>> gdb for quick debug sessions and vim for quick edits, and >used >> XCode >> >> >>>> for trickier debugging/profiling. >> >> >>>> >> >> >>>>> On Thu, Feb 1, 2018 at 12:42 PM, Edward Costello < >> phasereset@gmail.com> wrote: >> >> >>>>> Using CMake you can create an Xcode project from the Csound >> sources which >> >> >>>>> you can use to develop/debug Csound using Xcode. >> >> >>>>> >> >> >>>>> git clone https://github.com/csound/csound.git >> >> >>>>> cd csound >> >> >>>>> mkdir Xcode >> >> >>>>> cd Xcode >> >> >>>>> cmake -G Xcode .. >> >> >>>>> >> >> >>>>> >> >> >>>>> Best, >> >> >>>>> Ed >> >> >>>>> >> >> >>>>> On 1 Feb 2018, at 09:23, Ben McAllister >wrote: >> >> >>>>> >> >> >>>>> Hi All - this question was buried in a previous message, but >> pulling it out >> >> >>>>> separately hoping to get a response from csound developers: >> >> >>>>> >> >> >>>>> If you're working on a Mac, I'm curious what you're using >for a >> >> >>>>> development/debugging environment. Did you create an >xcodeproj >> for Mac >> >> >>>>> Desktop in Xcode? Anyone using AppCode or CLion from >JetBrains? >> Is Mac in >> >> >>>>> the minority, and are more devs on Linux using.. gdb and ddd >> maybe? >> >> >>>>> >> >> >>>>> As an old csounder and experienced developer (been at both >since >> 96 or so), >> >> >>>>> I'd like to get more familiar with this tool I love and >maybe >> contribute. >> >> >>>>> >> >> >>>>> Thanks in advance, >> >> >>>>> b >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> features can >> >> >>>>> be posted here >> >> >>>>> >> >> >>>>> >> >> >>>>> Csound mailing list Csound@listserv.heanet.ie >> >> >>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs >> reports to >> >> >>>>> https://github.com/csound/csound/issues Discussions of bugs >and >> features can >> >> >>>>> be posted here >> >> >>>> >> >> >>>> Csound mailing list >> >> >>>> Csound@listserv.heanet.ie >> >> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>>> Send bugs reports to >> >> >>>> https://github.com/csound/csound/issues >> >> >>>> Discussions of bugs and features can be posted here >> >> >>> >> >> >>> Csound mailing list >> >> >>> Csound@listserv.heanet.ie >> >> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >>> Send bugs reports to >> >> >>> https://github.com/csound/csound/issues >> >> >>> Discussions of bugs and features can be posted here >> >> >> >> >> >> Csound mailing list >> >> >> Csound@listserv.heanet.ie >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> >> Send bugs reports to >> >> >> https://github.com/csound/csound/issues >> >> >> Discussions of bugs and features can be posted here >> >> > >> >> > Csound mailing list >> >> > Csound@listserv.heanet.ie >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> > Send bugs reports to >> >> > https://github.com/csound/csound/issues >> >> > Discussions of bugs and features can be posted here >> >> >> >> Csound mailing list >> >> Csound@listserv.heanet.ie >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> >> Send bugs reports to >> >> https://github.com/csound/csound/issues >> >> Discussions of bugs and features can be posted here >> >> >> >> >> >> >> >> -- >> >> Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com >\| >> c: 206.849.3183 >> >> Csound mailing list Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to >> https://github.com/csound/csound/issues Discussions of bugs and >features >> can be posted here >> > >> > >> > Csound mailing list >> > Csound@listserv.heanet.ie >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> > Send bugs reports to >> > https://github.com/csound/csound/issues >> > Discussions of bugs and features can be posted here >> >> Csound mailing list >> Csound@listserv.heanet.ie >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> > > > >-- >Ben McAllister \| listenfaster.com \| @listenfaster \| tuktuband.com \| c: >206.849.3183 > >Csound mailing list >Csound@listserv.heanet.ie >https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND >Send bugs reports to > https://github.com/csound/csound/issues >Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here