[Csnd] "odd" csound6 build on OSX

Date	2013-11-08 10:56
From	David Worrall
Subject	[Csnd] "odd" csound6 build on OSX
	I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-08 11:06
From	Victor Lazzarini
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall wrote: > I'm trying to do something conceptually very simple but haven't succeeded. > I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): > > a) Install the dependencies using MacPorts, and > b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) > > What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt > I can provide output from cmake if that helps. > > Perhaps it is documented somewhere - but I haven't found it. > > > Can anyone help? > > Thanks, > > David > > > ______________________________________ > Prof. Dr. David Worrall > Emerging Audio Research (EAR) > Audio Department > International Audio Laboratories Erlangen > Fraunhofer-Institut für Integrierte Schaltungen IIS > Am Wolfsmantel 33 > 91058 Erlangen > Telefon +49 (0) 91 31 / 7 76-62 44 > Fax +49 (0) 91 31 / 7 76-20 99 > E-Mail: david.worrall@iis.fraunhofer.de > Internet: www.iis.fraunhofer.de > > > >

Date	2013-11-08 16:48
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-11 16:12
From	Victor Lazzarini
Subject	Re: [Csnd] "odd" csound6 build on OSX
	I just saw this now. I am not quite sure, but I would suggest that you should try to make any changes in Custom.cmake, because things can get entangled by changing CMakeLists.txt. However, it is my impression that things get set in CMakelists.txt later than Custom.cmake, so they might override them. So in this case, my suggestion might not be possible. Maybe Steven can help more with this, since he wrote most of the CMakeLists.txt script. Victor On 8 Nov 2013, at 16:48, David Worrall wrote: > Thanks for your help! > > I have some opcode questions as well, but firstly, the python interface... > > In Custom.cmake, I've altered > set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") > (the Python I'm using) > > In CMakeLists.txt, do I need to change > if(APPLE) > if(BUILD_INSTALLER) > …. > else() > get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) > > or do I copy the change to Custom.cmake? > i.e. does Custom.cmake override settings in CMakeLists.txt? > > Is there anything else required to get the libraries build for the python on question? > > thanks, > David > > On 08.11.2013, at 12:06, Victor Lazzarini wrote: > >> Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? >> You can put your custom cmake configuration there. >> >> On 8 Nov 2013, at 10:56, David Worrall wrote: >> >>> I'm trying to do something conceptually very simple but haven't succeeded. >>> I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): >>> >>> a) Install the dependencies using MacPorts, and >>> b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) >>> >>> What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt >>> I can provide output from cmake if that helps. >>> >>> Perhaps it is documented somewhere - but I haven't found it. >>> >>> >>> Can anyone help? >>> >>> Thanks, >>> >>> David >>> >>> >>> ______________________________________ >>> Prof. Dr. David Worrall >>> Emerging Audio Research (EAR) >>> Audio Department >>> International Audio Laboratories Erlangen >>> Fraunhofer-Institut für Integrierte Schaltungen IIS >>> Am Wolfsmantel 33 >>> 91058 Erlangen >>> Telefon +49 (0) 91 31 / 7 76-62 44 >>> Fax +49 (0) 91 31 / 7 76-20 99 >>> E-Mail: david.worrall@iis.fraunhofer.de >>> Internet: www.iis.fraunhofer.de > >

Date	2013-11-11 16:38
From	Steven Yi
Subject	Re: [Csnd] "odd" csound6 build on OSX
	I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python or use set(PYTHON_MODULE_INSTALL_DIR /my/location) etc. and those values should override what might be done later in code. Those values may also get cached, so you might need to double-check and maybe hand edit the CMakeCache.txt in your build folder (you could edit there directly or clear it and allow the setting from commandline or Custom.cmake to take effect). On Mon, Nov 11, 2013 at 11:12 AM, Victor Lazzarini wrote: > I just saw this now. I am not quite sure, but I would suggest that you should try to make any changes in > Custom.cmake, because things can get entangled by changing CMakeLists.txt. > > However, it is my impression that things get set in CMakelists.txt later than Custom.cmake, so > they might override them. So in this case, my suggestion might not be possible. > > Maybe Steven can help more with this, since he wrote most of the CMakeLists.txt script. > > Victor > > On 8 Nov 2013, at 16:48, David Worrall wrote: > >> Thanks for your help! >> >> I have some opcode questions as well, but firstly, the python interface... >> >> In Custom.cmake, I've altered >> set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") >> (the Python I'm using) >> >> In CMakeLists.txt, do I need to change >> if(APPLE) >> if(BUILD_INSTALLER) >> …. >> else() >> get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) >> >> or do I copy the change to Custom.cmake? >> i.e. does Custom.cmake override settings in CMakeLists.txt? >> >> Is there anything else required to get the libraries build for the python on question? >> >> thanks, >> David >> >> On 08.11.2013, at 12:06, Victor Lazzarini wrote: >> >>> Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? >>> You can put your custom cmake configuration there. >>> >>> On 8 Nov 2013, at 10:56, David Worrall wrote: >>> >>>> I'm trying to do something conceptually very simple but haven't succeeded. >>>> I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): >>>> >>>> a) Install the dependencies using MacPorts, and >>>> b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) >>>> >>>> What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt >>>> I can provide output from cmake if that helps. >>>> >>>> Perhaps it is documented somewhere - but I haven't found it. >>>> >>>> >>>> Can anyone help? >>>> >>>> Thanks, >>>> >>>> David >>>> >>>> >>>> ______________________________________ >>>> Prof. Dr. David Worrall >>>> Emerging Audio Research (EAR) >>>> Audio Department >>>> International Audio Laboratories Erlangen >>>> Fraunhofer-Institut für Integrierte Schaltungen IIS >>>> Am Wolfsmantel 33 >>>> 91058 Erlangen >>>> Telefon +49 (0) 91 31 / 7 76-62 44 >>>> Fax +49 (0) 91 31 / 7 76-20 99 >>>> E-Mail: david.worrall@iis.fraunhofer.de >>>> Internet: www.iis.fraunhofer.de >> >> > > > > Send bugs reports to the Sourceforge bug trackers > csound6: > https://sourceforge.net/p/csound/tickets/ > csound5: > https://sourceforge.net/p/csound/bugs/ > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" > >

Date	2013-11-11 16:41
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Thanks to both of you for this. my mods in Custom.cmake didn't get picked up so I'll unpick then and try you suggestions. David On 11.11.2013, at 17:38, Steven Yi <stevenyi@gmail.com> wrote: I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python or use set(PYTHON_MODULE_INSTALL_DIR /my/location) etc. and those values should override what might be done later in code. Those values may also get cached, so you might need to double-check and maybe hand edit the CMakeCache.txt in your build folder (you could edit there directly or clear it and allow the setting from commandline or Custom.cmake to take effect). On Mon, Nov 11, 2013 at 11:12 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: I just saw this now. I am not quite sure, but I would suggest that you should try to make any changes in Custom.cmake, because things can get entangled by changing CMakeLists.txt. However, it is my impression that things get set in CMakelists.txt later than Custom.cmake, so they might override them. So in this case, my suggestion might not be possible. Maybe Steven can help more with this, since he wrote most of the CMakeLists.txt script. Victor On 8 Nov 2013, at 16:48, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-14 16:04
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import csnd6 >>> with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-14 16:23
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	On 14.11.2013, at 17:04, David Worrall <david.worrall@iis.fraunhofer.de> wrote: when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. Apologies -it does not - it seems Python.h includes stuff not in the OPcodes/py directory: In file included from /Users/wor/csound6-git/Opcodes/py/pythonopcodes.c:26: /Users/wor/csound6-git/Opcodes/py/Python.h:7:10: fatal error: 'patchlevel.h' file not found So the way Python.h is included in the Opcodes/py code needs to be resolved. D. ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-18 16:07
From	Steven Yi
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall wrote: > An update on this attempt to use a "non-standard" python in a csound6 build > on OSX. > > The bug reported earlier that prevented the python interface being build was > caused by SWIG, specifically v 2.0.10 - the most recent version provided and > installed by MacPorts. > With the latest version of SWIG (2.0.11) from their own website, the bug > disappear and the Python interface seems to work - at least w. the OSX > system python: > % /usr/bin/python > Python 2.7.2 (default, Oct 11 2012, 20:14:37) > [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin > Type "help", "copyright", "credits" or "license" for more information. >>>> import csnd6 >>>> > with that sorted, the build works w. the OSX system python. > > The next step is to try to get it to work w. the anaconda python framework. > At the moment it exceptions on import: > % python > Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) > [GCC 4.0.1 (Apple Inc. build 5493)] on darwin > Type "help", "copyright", "credits" or "license" for more information. >>>> import csnd6 > Fatal Python error: PyThreadState_Get: no current thread > Abort > % > This is the same exception I get with the import of csnd6 from the OSX > installer package. FYI: > % otool -L _csnd6.so > _csnd6.so: > CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, > current version 0.0.0) > /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current > version 2.25.0) > /System/Library/Frameworks/Python.framework/Versions/2.7/Python > (compatibility version 2.7.0, current version 2.7.2) > libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) > /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version > 56.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version > 169.3.0) > % > > So perhaps the library is sensitive to the different versions of python > (v2.7.2. c.f v2.7.5) ?? > ------ > Stephen, you said > > I think the python library should work regardless of what python > installtion it is running with. At least, we had done some work to > not link with libpython, so that it lib_csnd6.dylib could load with > any python version. Perhaps that's changed? > > As for CMake, you can override any value from the command-line or from > Custom.cmake. So you should be able to use: > > -DPYTHON_MODULE_INSTALL_DIR=/my/location > -DPYTHON_INCLUDE_DIR=/path/to/my/python > > > when I did these overrides, the build aborted on meeting #include > in .../Opcodes/py/pythonopcodes.c > > so I copied the Python.h from the python I'm using (2.7.5) and altered it to > #include "Python.h" > and it built successfully. > > But the import of the resulting csnd6.py still causes the python exception, > as above. > > Thoughts as to where to look next? > > thanks, > > David > > > On 08.11.2013, at 17:48, David Worrall > wrote: > > Thanks for your help! > > I have some opcode questions as well, but firstly, the python interface... > > In Custom.cmake, I've altered > set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") > (the Python I'm using) > > In CMakeLists.txt, do I need to change > if(APPLE) > if(BUILD_INSTALLER) > …. > else() > get_filename_component(PYTHON_MODULE_INSTALL_DIR > "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) > > or do I copy the change to Custom.cmake? > i.e. does Custom.cmake override settings in CMakeLists.txt? > > Is there anything else required to get the libraries build for the python on > question? > > thanks, > David > > On 08.11.2013, at 12:06, Victor Lazzarini wrote: > > Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? > You can put your custom cmake configuration there. > > On 8 Nov 2013, at 10:56, David Worrall > wrote: > > I'm trying to do something conceptually very simple but haven't succeeded. > I'm trying to build csound6 from a git clone (depth=1) sources, with two > modifications to the standard build (which works fine): > > a) Install the dependencies using MacPorts, and > b) make it using a python2.7 which is not installed in one of the "normal" > places (but is is the shell's $PATH) > > What do I need to do to effect that (in terms of changes to $PATH, and/or > csound-git/CMakeLists.txt > I can provide output from cmake if that helps. > > Perhaps it is documented somewhere - but I haven't found it. > > > Can anyone help? > > Thanks, > > David > > ... > > ______________________________________ > Prof. Dr. David Worrall > Emerging Audio Research (EAR) > Audio Department > International Audio Laboratories Erlangen > Fraunhofer-Institut für Integrierte Schaltungen IIS > Am Wolfsmantel 33 > 91058 Erlangen > Telefon +49 (0) 91 31 / 7 76-62 44 > Fax +49 (0) 91 31 / 7 76-20 99 > E-Mail: david.worrall@iis.fraunhofer.de > Internet: www.iis.fraunhofer.de > > > >

Date	2013-11-22 03:59
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-22 04:54
From	Steven Yi
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-22 08:44
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-22 15:27
From	joachim heintz
Subject	Re: [Csnd] "odd" csound6 build on OSX
	hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: > Hi Steven, > > Thanks for that - it works like a charm :-) > > So now we have a csound that works with at least one major packaging > environment for scientific work on OSX. > > Thanks to all who have contributed to this. > > I'll write up the build process and post a link for those interested. > > David > > > On 21.11.2013, at 18:02, Forrest Cahoon > wrote: > >> Hi David, >> >> Are you using the develop branch? If not you should be able to do >> "git checkout develop" and do a pull after to get the latest from >> develop. Let me know and we can continue diagnosing from there. >> >> All best, >> Steven >> >> On Nov 21, 2013 11:00 PM, "David Worrall" >> > > wrote: >> >> Hi Stephen, >> Apologies for my delay in replying… >> >> I've done as you suggested, and double-checked it. Same result, >> I'm afraid. >> i.e. I have sound building against the system python and csnd6 >> works fine with it. >> Same trap error. >> >> I have resisted altering the Makefiles, but when grep >> for PYTHON_LIBRARY I see it is still linking to the system python >> library: >> >> [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* >> ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib >> ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND >> ./build/CMakeCache.txt:1219://ADVANCED property for variable: >> PYTHON_LIBRARY >> ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 >> ./build/CMakeCache.txt:1221://ADVANCED property for variable: >> PYTHON_LIBRARY_DEBUG >> ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 >> ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) >> ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS >> ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} >> ${PYTHON_LIBRARY} libcsnd6) >> >> am I git-ing the correct version? >> I could try hand-editing the make files (after ccmake?) if that >> would help as a x-check. If so, which ones? >> >> Thanks for your assistance, >> >> David >> >> >> >> On 18.11.2013, at 17:07, Steven Yi > > wrote: >> >>> Hi David, >>> >>> I think this part is key as to why you're getting the thread >>> state error: >>> >>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>> (compatibility version 2.7.0, current version 2.7.2) >>> >>> the _csnd6.so is linking to the system python. I had removed that a >>> while ago but I just went through the history and found that someone >>> had put PYTHON_LIBRARY back in to the library link list. >>> >>> I've taken that back out and tested on OSX. If I remember correctly, >>> it worked fine on Windows and Linux this way too. If others have >>> problems compiling on those platforms, please let me know. >>> >>> Could you pull the latest from GIT and try compiling again? I'm >>> going >>> to assume that the releases I've done since 2013-03-17 when that >>> commit re-added the python lib to linking have the system python >>> linked in. That shouldn't have been the case. >>> >>> Also Dave, you might want to try just compiling against the system >>> python without any changes, then just install the python stuff into >>> your anaconda python. With this change, it should work. (It was one >>> of the motivating reasons for removing the python lib link back >>> when I >>> first did this). >>> >>> steven >>> >>> >>> >>> On Thu, Nov 14, 2013 at 11:04 AM, David Worrall >>> >> > wrote: >>>> An update on this attempt to use a "non-standard" python in a >>>> csound6 build >>>> on OSX. >>>> >>>> The bug reported earlier that prevented the python interface >>>> being build was >>>> caused by SWIG, specifically v 2.0.10 - the most recent version >>>> provided and >>>> installed by MacPorts. >>>> With the latest version of SWIG (2.0.11) from their own website, >>>> the bug >>>> disappear and the Python interface seems to work - at least w. >>>> the OSX >>>> system python: >>>> % /usr/bin/python >>>> Python 2.7.2 (default, Oct 11 2012, 20:14:37) >>>> [GCC 4.2.1 Compatible Apple Clang 4.0 >>>> (tags/Apple/clang-418.0.60)] on darwin >>>> Type "help", "copyright", "credits" or "license" for more >>>> information. >>>>>>> import csnd6 >>>>>>> >>>> with that sorted, the build works w. the OSX system python. >>>> >>>> The next step is to try to get it to work w. the anaconda python >>>> framework. >>>> At the moment it exceptions on import: >>>> % python >>>> Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, >>>> 22:20:13) >>>> [GCC 4.0.1 (Apple Inc. build 5493)] on darwin >>>> Type "help", "copyright", "credits" or "license" for more >>>> information. >>>>>>> import csnd6 >>>> Fatal Python error: PyThreadState_Get: no current thread >>>> Abort >>>> % >>>> This is the same exception I get with the import of csnd6 from >>>> the OSX >>>> installer package. FYI: >>>> % otool -L _csnd6.so >>>> _csnd6.so: >>>> CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility >>>> version 6.0.0, >>>> current version 0.0.0) >>>> /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, >>>> current >>>> version 2.25.0) >>>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>>> (compatibility version 2.7.0, current version 2.7.2) >>>> libcsnd6.6.0.dylib (compatibility version 6.0.0, current version >>>> 0.0.0) >>>> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current >>>> version >>>> 56.0.0) >>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current >>>> version >>>> 169.3.0) >>>> % >>>> >>>> So perhaps the library is sensitive to the different versions of >>>> python >>>> (v2.7.2. c.f v2.7.5) ?? >>>> ------ >>>> Stephen, you said >>>> >>>> I think the python library should work regardless of what python >>>> installtion it is running with. At least, we had done some work to >>>> not link with libpython, so that it lib_csnd6.dylib could load with >>>> any python version. Perhaps that's changed? >>>> >>>> As for CMake, you can override any value from the command-line >>>> or from >>>> Custom.cmake. So you should be able to use: >>>> >>>> -DPYTHON_MODULE_INSTALL_DIR=/my/location >>>> -DPYTHON_INCLUDE_DIR=/path/to/my/python >>>> >>>> >>>> when I did these overrides, the build aborted on meeting >>>> #include >>>> in .../Opcodes/py/pythonopcodes.c >>>> >>>> so I copied the Python.h from the python I'm using (2.7.5) and >>>> altered it to >>>> #include "Python.h" >>>> and it built successfully. >>>> >>>> But the import of the resulting csnd6.py still causes the python >>>> exception, >>>> as above. >>>> >>>> Thoughts as to where to look next? >>>> >>>> thanks, >>>> >>>> David >>>> >>>> >>>> On 08.11.2013, at 17:48, David Worrall >>>> >>> > >>>> wrote: >>>> >>>> Thanks for your help! >>>> >>>> I have some opcode questions as well, but firstly, the python >>>> interface... >>>> >>>> In Custom.cmake, I've altered >>>> set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") >>>> (the Python I'm using) >>>> >>>> In CMakeLists.txt, do I need to change >>>> if(APPLE) >>>> if(BUILD_INSTALLER) >>>> …. >>>> else() >>>> get_filename_component(PYTHON_MODULE_INSTALL_DIR >>>> "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) >>>> >>>> or do I copy the change to Custom.cmake? >>>> i.e. does Custom.cmake override settings in CMakeLists.txt? >>>> >>>> Is there anything else required to get the libraries build for >>>> the python on >>>> question? >>>> >>>> thanks, >>>> David >>>> >>>> On 08.11.2013, at 12:06, Victor Lazzarini >>>> > wrote: >>>> >>>> Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? >>>> You can put your custom cmake configuration there. >>>> >>>> On 8 Nov 2013, at 10:56, David Worrall >>>> >>> > >>>> wrote: >>>> >>>> I'm trying to do something conceptually very simple but haven't >>>> succeeded. >>>> I'm trying to build csound6 from a git clone (depth=1) sources, >>>> with two >>>> modifications to the standard build (which works fine): >>>> >>>> a) Install the dependencies using MacPorts, and >>>> b) make it using a python2.7 which is not installed in one of >>>> the "normal" >>>> places (but is is the shell's $PATH) >>>> >>>> What do I need to do to effect that (in terms of changes to >>>> $PATH, and/or >>>> csound-git/CMakeLists.txt >>>> I can provide output from cmake if that helps. >>>> >>>> Perhaps it is documented somewhere - but I haven't found it. >>>> >>>> >>>> Can anyone help? >>>> >>>> Thanks, >>>> >>>> David >>>> >>>> … > ... > ______________________________________ > Prof. Dr. David Worrall > Emerging Audio Research (EAR) > Audio Department > International Audio Laboratories Erlangen > Fraunhofer-Institut für Integrierte Schaltungen IIS > Am Wolfsmantel 33 > 91058 Erlangen > Telefon +49 (0) 91 31 / 7 76-62 44 > Fax +49 (0) 91 31 / 7 76-20 99 > E-Mail: david.worrall@iis.fraunhofer.de > > Internet: www.iis.fraunhofer.de > > > >

Date	2013-11-22 15:46
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Of course! no worries….. D. On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote: hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com <mailto:forrest.cahoon@gmail.com>> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com <mailto:stevenyi@gmail.com>> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de> Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de> Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-22 21:18
From	Victor Lazzarini
Subject	Re: [Csnd] "odd" csound6 build on OSX
	What is this major scientific packaging you’ve mentioned? I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need for a custom build, on OSX. Victor On 22 Nov 2013, at 15:46, David Worrall wrote: > Of course! no worries….. > D. > > > On 22.11.2013, at 16:27, joachim heintz wrote: > >> hi david - >> >> if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). >> >> best - >> >> joachim >> >> >> Am 22.11.2013 09:44, schrieb David Worrall: >>> Hi Steven, >>> >>> Thanks for that - it works like a charm :-) >>> >>> So now we have a csound that works with at least one major packaging >>> environment for scientific work on OSX. >>> >>> Thanks to all who have contributed to this. >>> >>> I'll write up the build process and post a link for those interested. >>> >>> David >>> >>> >>> On 21.11.2013, at 18:02, Forrest Cahoon >> > wrote: >>> >>>> Hi David, >>>> >>>> Are you using the develop branch? If not you should be able to do >>>> "git checkout develop" and do a pull after to get the latest from >>>> develop. Let me know and we can continue diagnosing from there. >>>> >>>> All best, >>>> Steven >>>> >>>> On Nov 21, 2013 11:00 PM, "David Worrall" >>>> >>> > wrote: >>>> >>>> Hi Stephen, >>>> Apologies for my delay in replying… >>>> >>>> I've done as you suggested, and double-checked it. Same result, >>>> I'm afraid. >>>> i.e. I have sound building against the system python and csnd6 >>>> works fine with it. >>>> Same trap error. >>>> >>>> I have resisted altering the Makefiles, but when grep >>>> for PYTHON_LIBRARY I see it is still linking to the system python >>>> library: >>>> >>>> [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* >>>> ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib >>>> ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND >>>> ./build/CMakeCache.txt:1219://ADVANCED property for variable: >>>> PYTHON_LIBRARY >>>> ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 >>>> ./build/CMakeCache.txt:1221://ADVANCED property for variable: >>>> PYTHON_LIBRARY_DEBUG >>>> ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 >>>> ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) >>>> ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS >>>> ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} >>>> ${PYTHON_LIBRARY} libcsnd6) >>>> >>>> am I git-ing the correct version? >>>> I could try hand-editing the make files (after ccmake?) if that >>>> would help as a x-check. If so, which ones? >>>> >>>> Thanks for your assistance, >>>> >>>> David >>>> >>>> >>>> >>>> On 18.11.2013, at 17:07, Steven Yi >>> > wrote: >>>> >>>>> Hi David, >>>>> >>>>> I think this part is key as to why you're getting the thread >>>>> state error: >>>>> >>>>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>>>> (compatibility version 2.7.0, current version 2.7.2) >>>>> >>>>> the _csnd6.so is linking to the system python. I had removed that a >>>>> while ago but I just went through the history and found that someone >>>>> had put PYTHON_LIBRARY back in to the library link list. >>>>> >>>>> I've taken that back out and tested on OSX. If I remember correctly, >>>>> it worked fine on Windows and Linux this way too. If others have >>>>> problems compiling on those platforms, please let me know. >>>>> >>>>> Could you pull the latest from GIT and try compiling again? I'm >>>>> going >>>>> to assume that the releases I've done since 2013-03-17 when that >>>>> commit re-added the python lib to linking have the system python >>>>> linked in. That shouldn't have been the case. >>>>> >>>>> Also Dave, you might want to try just compiling against the system >>>>> python without any changes, then just install the python stuff into >>>>> your anaconda python. With this change, it should work. (It was one >>>>> of the motivating reasons for removing the python lib link back >>>>> when I >>>>> first did this). >>>>> >>>>> steven >>>>> >>>>> >>>>> >>>>> On Thu, Nov 14, 2013 at 11:04 AM, David Worrall >>>>> >>>> > wrote: >>>>>> An update on this attempt to use a "non-standard" python in a >>>>>> csound6 build >>>>>> on OSX. >>>>>> >>>>>> The bug reported earlier that prevented the python interface >>>>>> being build was >>>>>> caused by SWIG, specifically v 2.0.10 - the most recent version >>>>>> provided and >>>>>> installed by MacPorts. >>>>>> With the latest version of SWIG (2.0.11) from their own website, >>>>>> the bug >>>>>> disappear and the Python interface seems to work - at least w. >>>>>> the OSX >>>>>> system python: >>>>>> % /usr/bin/python >>>>>> Python 2.7.2 (default, Oct 11 2012, 20:14:37) >>>>>> [GCC 4.2.1 Compatible Apple Clang 4.0 >>>>>> (tags/Apple/clang-418.0.60)] on darwin >>>>>> Type "help", "copyright", "credits" or "license" for more >>>>>> information. >>>>>>>>> import csnd6 >>>>>>>>> >>>>>> with that sorted, the build works w. the OSX system python. >>>>>> >>>>>> The next step is to try to get it to work w. the anaconda python >>>>>> framework. >>>>>> At the moment it exceptions on import: >>>>>> % python >>>>>> Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, >>>>>> 22:20:13) >>>>>> [GCC 4.0.1 (Apple Inc. build 5493)] on darwin >>>>>> Type "help", "copyright", "credits" or "license" for more >>>>>> information. >>>>>>>>> import csnd6 >>>>>> Fatal Python error: PyThreadState_Get: no current thread >>>>>> Abort >>>>>> % >>>>>> This is the same exception I get with the import of csnd6 from >>>>>> the OSX >>>>>> installer package. FYI: >>>>>> % otool -L _csnd6.so >>>>>> _csnd6.so: >>>>>> CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility >>>>>> version 6.0.0, >>>>>> current version 0.0.0) >>>>>> /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, >>>>>> current >>>>>> version 2.25.0) >>>>>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>>>>> (compatibility version 2.7.0, current version 2.7.2) >>>>>> libcsnd6.6.0.dylib (compatibility version 6.0.0, current version >>>>>> 0.0.0) >>>>>> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current >>>>>> version >>>>>> 56.0.0) >>>>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current >>>>>> version >>>>>> 169.3.0) >>>>>> % >>>>>> >>>>>> So perhaps the library is sensitive to the different versions of >>>>>> python >>>>>> (v2.7.2. c.f v2.7.5) ?? >>>>>> ------ >>>>>> Stephen, you said >>>>>> >>>>>> I think the python library should work regardless of what python >>>>>> installtion it is running with. At least, we had done some work to >>>>>> not link with libpython, so that it lib_csnd6.dylib could load with >>>>>> any python version. Perhaps that's changed? >>>>>> >>>>>> As for CMake, you can override any value from the command-line >>>>>> or from >>>>>> Custom.cmake. So you should be able to use: >>>>>> >>>>>> -DPYTHON_MODULE_INSTALL_DIR=/my/location >>>>>> -DPYTHON_INCLUDE_DIR=/path/to/my/python >>>>>> >>>>>> >>>>>> when I did these overrides, the build aborted on meeting >>>>>> #include >>>>>> in .../Opcodes/py/pythonopcodes.c >>>>>> >>>>>> so I copied the Python.h from the python I'm using (2.7.5) and >>>>>> altered it to >>>>>> #include "Python.h" >>>>>> and it built successfully. >>>>>> >>>>>> But the import of the resulting csnd6.py still causes the python >>>>>> exception, >>>>>> as above. >>>>>> >>>>>> Thoughts as to where to look next? >>>>>> >>>>>> thanks, >>>>>> >>>>>> David >>>>>> >>>>>> >>>>>> On 08.11.2013, at 17:48, David Worrall >>>>>> >>>>> > >>>>>> wrote: >>>>>> >>>>>> Thanks for your help! >>>>>> >>>>>> I have some opcode questions as well, but firstly, the python >>>>>> interface... >>>>>> >>>>>> In Custom.cmake, I've altered >>>>>> set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") >>>>>> (the Python I'm using) >>>>>> >>>>>> In CMakeLists.txt, do I need to change >>>>>> if(APPLE) >>>>>> if(BUILD_INSTALLER) >>>>>> …. >>>>>> else() >>>>>> get_filename_component(PYTHON_MODULE_INSTALL_DIR >>>>>> "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) >>>>>> >>>>>> or do I copy the change to Custom.cmake? >>>>>> i.e. does Custom.cmake override settings in CMakeLists.txt? >>>>>> >>>>>> Is there anything else required to get the libraries build for >>>>>> the python on >>>>>> question? >>>>>> >>>>>> thanks, >>>>>> David >>>>>> >>>>>> On 08.11.2013, at 12:06, Victor Lazzarini >>>>>> > wrote: >>>>>> >>>>>> Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? >>>>>> You can put your custom cmake configuration there. >>>>>> >>>>>> On 8 Nov 2013, at 10:56, David Worrall >>>>>> >>>>> > >>>>>> wrote: >>>>>> >>>>>> I'm trying to do something conceptually very simple but haven't >>>>>> succeeded. >>>>>> I'm trying to build csound6 from a git clone (depth=1) sources, >>>>>> with two >>>>>> modifications to the standard build (which works fine): >>>>>> >>>>>> a) Install the dependencies using MacPorts, and >>>>>> b) make it using a python2.7 which is not installed in one of >>>>>> the "normal" >>>>>> places (but is is the shell's $PATH) >>>>>> >>>>>> What do I need to do to effect that (in terms of changes to >>>>>> $PATH, and/or >>>>>> csound-git/CMakeLists.txt >>>>>> I can provide output from cmake if that helps. >>>>>> >>>>>> Perhaps it is documented somewhere - but I haven't found it. >>>>>> >>>>>> >>>>>> Can anyone help? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> David >>>>>> >>>>>> … >>> ... >>> ______________________________________ >>> Prof. Dr. David Worrall >>> Emerging Audio Research (EAR) >>> Audio Department >>> International Audio Laboratories Erlangen >>> Fraunhofer-Institut für Integrierte Schaltungen IIS >>> Am Wolfsmantel 33 >>> 91058 Erlangen >>> Telefon +49 (0) 91 31 / 7 76-62 44 >>> Fax +49 (0) 91 31 / 7 76-20 99 >>> E-Mail: david.worrall@iis.fraunhofer.de >>> >>> Internet: www.iis.fraunhofer.de >>> >>> >>> >>> >> >> >> Send bugs reports to the Sourceforge bug trackers >> csound6: >> https://sourceforge.net/p/csound/tickets/ >> csound5: >> https://sourceforge.net/p/csound/bugs/ >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" >> >> > > ______________________________________ > Prof. Dr. David Worrall > Emerging Audio Research (EAR) > Audio Department > International Audio Laboratories Erlangen > Fraunhofer-Institut für Integrierte Schaltungen IIS > Am Wolfsmantel 33 > 91058 Erlangen > Telefon +49 (0) 91 31 / 7 76-62 44 > Fax +49 (0) 91 31 / 7 76-20 99 > E-Mail: david.worrall@iis.fraunhofer.de > Internet: www.iis.fraunhofer.de > > > >

Date

2013-11-23 15:00

From

David Worrall

Subject

Re: [Csnd] "odd" csound6 build on OSX

The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++.

Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms.

They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda

apptools 4.2.0
astropy 0.2.5
atom 0.3.4
beautiful-soup 4.3.1
binstar 0.3.1
biopython 1.62
bitarray 0.8.1
blaze 0.3
bokeh 0.2
boto 2.15.0
cairo 1.12.2 L
casuarius 1.1
chaco 4.3.0
colorama 0.2.7
configobj 4.7.2
cubes 0.10.2
curl 7.30.0 LM
cython 0.19.2
dateutil 2.1
disco 0.4.4 L
distribute 0.6.45
docutils 0.11
dynd-python 0.5.0
enable 4.3.0
enaml 0.8.3
envisage 4.3.0
erlang R15B01 L
flask 0.10.1
freetype 2.4.10
gevent 0.13.8
gevent-websocket 0.3.6

gevent_zeromq 0.2.5
greenlet 0.4.1
grin 1.2.1
h5py 2.2.0
hdf5 1.8.9
imaging 1.1.7
ipython 1.1.0
itsdangerous 0.23
jinja2 2.7.1
keyring 3.2
launcher 0.1.2
libevent 2.0.20
libnetcdf 4.2.1.1 LM
libpng 1.5.13 LM
libtiff 4.0.2 LM
libxml2 2.9.0 LM
libxslt 1.1.28 LM
llvm 3.3
llvmmath 0.1.1
llvmpy 0.12.0
lxml 3.2.3
markupsafe 0.18
matplotlib 1.3.1
mayavi 4.3.0
mdp 3.3
menuinst 1.0.3 W
meta 0.4.2.dev
mingw 4.7 W
mpi4py 1.3 L
mpich2 1.4.1p1 L
netcdf4 1.0.6 LM

networkx 1.8.1
nltk 2.0.4
nose 1.3.0
numba 0.11.0
numexpr 2.2.2
numpy 1.7.1
opencv 2.4.6 L
openpyxl 1.6.2
pandas 0.12.0
patsy 0.2.1
pep8 1.4.6
pip 1.4.1
ply 3.4
psutil 1.1.2
py 1.4.17
py2cairo 1.10.0 L
pyaudio 0.2.7 M
pycosat 0.6.0
pycparser 2.9.1
pycrypto 2.6.1
pycurl 7.19.0 LM
pyface 4.3.0
pyflakes 0.7.3
pygments 1.6
pykit 0.1.0
pyparsing 1.5.6
pyreadline 2.0.dev W
pysal 1.6.0
pysam 0.6 LM
pyside 1.2.1
pytables 3.0.0

pytest 2.4.2
python 2.7.5
pytz 2013b
pywin32 218.4 W
pyyaml 3.10
pyzmq 2.2.0.1
qt 4.8.5
redis 2.6.9 LM
redis-py 2.7.2 LM
requests 1.2.3
rope 0.9.4
scikit-image 0.9.3
scikit-learn 0.14.1
scipy 0.13.0
six 1.4.1
sphinx 1.1.3
spyder 2.2.5
sqlalchemy 0.8.3
statsmodels 0.5.0
sympy 0.7.3
theano 0.5.0 L
tornado 3.1.1
traits 4.3.0
traitsui 4.3.0
vtk 5.10.1
werkzeug 0.9.4
xlrd 0.9.2
xlwt 0.7.5
yaml 0.1.4 LM
zeromq 2.2.0 LM
zlib 1.2.7

David

On 22.11.2013, at 22:18, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

What is this major scientific packaging you’ve mentioned?

I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need
for a custom build, on OSX.

Victor

On 22 Nov 2013, at 15:46, David Worrall <david.worrall@iis.fraunhofer.de> wrote:

Of course! no worries…..
D.

On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote:

hi david -

if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/).

best -

joachim

Am 22.11.2013 09:44, schrieb David Worrall:
Hi Steven,

Thanks for that - it works like a charm :-)

So now we have a csound that works with at least one major packaging
environment for scientific work on OSX.

Thanks to all who have contributed to this.

I'll write up the build process and post a link for those interested.

David

On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com
<mailto:forrest.cahoon@gmail.com>> wrote:

Hi David,

Are you using the develop branch? If not you should be able to do
"git checkout develop" and do a pull after to get the latest from
develop. Let me know and we can continue diagnosing from there.

All best,
Steven

On Nov 21, 2013 11:00 PM, "David Worrall"
<david.worrall@iis.fraunhofer.de
<mailto:david.worrall@iis.fraunhofer.de>> wrote:

  Hi Stephen,
  Apologies for my delay in replying…

  I've done as you suggested, and double-checked it. Same result,
  I'm afraid.
  i.e. I have sound building against the system python and csnd6
  works fine with it.
  Same trap error.

  I have resisted altering the Makefiles, but when grep
  for PYTHON_LIBRARY I see it is still linking to the system python
  library:

  [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./*
  ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib
  ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND
  ./build/CMakeCache.txt:1219://ADVANCED property for variable:
  PYTHON_LIBRARY
  ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1
  ./build/CMakeCache.txt:1221://ADVANCED property for variable:
  PYTHON_LIBRARY_DEBUG
  ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY})
  ./interfaces/CMakeLists.txt:80:        set(swigpython_LIBS
  ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY}
  ${PYTHON_LIBRARY} libcsnd6)

  am I git-ing the correct version?
  I could try hand-editing the make files (after ccmake?) if that
  would help as a x-check. If so, which ones?

  Thanks for your assistance,

  David

  On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com
  <mailto:stevenyi@gmail.com>> wrote:

  Hi David,

  I think this part is key as to why you're getting the thread
  state error:

  /System/Library/Frameworks/Python.framework/Versions/2.7/Python
  (compatibility version 2.7.0, current version 2.7.2)

  the _csnd6.so is linking to the system python. I had removed that a
  while ago but I just went through the history and found that someone
  had put PYTHON_LIBRARY back in to the library link list.

  I've taken that back out and tested on OSX. If I remember correctly,
  it worked fine on Windows and Linux this way too. If others have
  problems compiling on those platforms, please let me know.

  Could you pull the latest from GIT and try compiling again? I'm
  going
  to assume that the releases I've done since 2013-03-17 when that
  commit re-added the python lib to linking have the system python
  linked in. That shouldn't have been the case.

  Also Dave, you might want to try just compiling against the system
  python without any changes, then just install the python stuff into
  your anaconda python. With this change, it should work. (It was one
  of the motivating reasons for removing the python lib link back
  when I
  first did this).

  steven

  On Thu, Nov 14, 2013 at 11:04 AM, David Worrall
  <david.worrall@iis.fraunhofer.de
  <mailto:david.worrall@iis.fraunhofer.de>> wrote:
  An update on this attempt to use a "non-standard" python in a
  csound6 build
  on OSX.

  The bug reported earlier that prevented the python interface
  being build was
  caused by SWIG, specifically v 2.0.10 - the most recent version
  provided and
  installed by MacPorts.
  With the latest version of SWIG (2.0.11) from their own website,
  the bug
  disappear and the Python interface seems to work - at least w.
  the OSX
  system python:
  % /usr/bin/python
  Python 2.7.2 (default, Oct 11 2012, 20:14:37)
  [GCC 4.2.1 Compatible Apple Clang 4.0
  (tags/Apple/clang-418.0.60)] on darwin
  Type "help", "copyright", "credits" or "license" for more
  information.
  import csnd6

  with that sorted, the build works w. the OSX system python.

  The next step is to try to get it to work w. the anaconda python
  framework.
  At the moment it exceptions on import:
  % python
  Python 2.7.5 |Anaconda 1.7.0 (x86_64)| (default, Jun 28 2013,
  22:20:13)
  [GCC 4.0.1 (Apple Inc. build 5493)] on darwin
  Type "help", "copyright", "credits" or "license" for more
  information.
  import csnd6
  Fatal Python error: PyThreadState_Get: no current thread
  Abort
  %
  This is the same exception I get with the import of csnd6 from
  the OSX
  installer package. FYI:
  % otool -L _csnd6.so
  _csnd6.so:
  CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility
  version 6.0.0,
  current version 0.0.0)
  /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0,
  current
  version 2.25.0)
  /System/Library/Frameworks/Python.framework/Versions/2.7/Python
  (compatibility version 2.7.0, current version 2.7.2)
  libcsnd6.6.0.dylib (compatibility version 6.0.0, current version
  0.0.0)
  /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
  version
  56.0.0)
  /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
  version
  169.3.0)
  %

  So perhaps the library is sensitive to the different versions of
  python
  (v2.7.2. c.f v2.7.5) ??
  ------
  Stephen, you said

  I think the python library should work regardless of what python
  installtion it is running with. At least, we had done some work to
  not link with libpython, so that it lib_csnd6.dylib could load with
  any python version. Perhaps that's changed?

  As for CMake, you can override any value from the command-line
  or from
  Custom.cmake. So you should be able to use:

  -DPYTHON_MODULE_INSTALL_DIR=/my/location
  -DPYTHON_INCLUDE_DIR=/path/to/my/python

  when I did these overrides, the build aborted on meeting
  #include<Python.h>
  in .../Opcodes/py/pythonopcodes.c

  so I copied the Python.h from the python I'm using (2.7.5) and
  altered it to
  #include "Python.h"
  and it built successfully.

  But the import of the resulting csnd6.py still causes the python
  exception,
  as above.

  Thoughts as to where to look next?

  thanks,

  David

  On 08.11.2013, at 17:48, David Worrall
  <david.worrall@iis.fraunhofer.de
  <mailto:david.worrall@iis.fraunhofer.de>>
  wrote:

  Thanks for your help!

  I have some opcode questions as well, but firstly, the python
  interface...

  In Custom.cmake, I've altered
  set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include")
  (the Python I'm using)

  In CMakeLists.txt, do I need to change
  if(APPLE)
     if(BUILD_INSTALLER)
  ….
     else()
         get_filename_component(PYTHON_MODULE_INSTALL_DIR
  "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE)

  or do I copy the change to Custom.cmake?
  i.e. does Custom.cmake override settings in CMakeLists.txt?

  Is there anything else required to get the libraries build for
  the python on
  question?

  thanks,
  David

  On 08.11.2013, at 12:06, Victor Lazzarini
  <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote:

  Did you try modifying Custom.cmake.ex and saving it as Custom.cmake?
  You can put your custom cmake configuration there.

  On 8 Nov 2013, at 10:56, David Worrall
  <david.worrall@iis.fraunhofer.de
  <mailto:david.worrall@iis.fraunhofer.de>>
  wrote:

  I'm trying to do something conceptually very simple but haven't
  succeeded.
  I'm trying to build csound6 from a git clone (depth=1) sources,
  with two
  modifications to the standard build (which works fine):

  a) Install the dependencies using MacPorts, and
  b) make it using a python2.7 which is not installed in one of
  the "normal"
  places (but is is the shell's $PATH)

  What do I need to do to effect that (in terms of changes to
  $PATH, and/or
  csound-git/CMakeLists.txt
  I can provide output from cmake if that helps.

  Perhaps it is documented somewhere - but I haven't found it.

  Can anyone help?

  Thanks,

  David

  …
...
______________________________________
Prof. Dr. David Worrall
Emerging Audio Research (EAR)
Audio Department
International Audio Laboratories Erlangen
Fraunhofer-Institut für Integrierte Schaltungen IIS
Am Wolfsmantel 33
91058 Erlangen
Telefon +49 (0) 91 31 / 7 76-62 44
Fax      +49 (0) 91 31 / 7 76-20 99
E-Mail: david.worrall@iis.fraunhofer.de
<mailto:david.worrall@iis.fraunhofer.de>
Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de>

Send bugs reports to the Sourceforge bug trackers
csound6:
         https://sourceforge.net/p/csound/tickets/
csound5:
         https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

______________________________________
Prof. Dr. David Worrall
Emerging Audio Research (EAR)
Audio Department
International Audio Laboratories Erlangen
Fraunhofer-Institut für Integrierte Schaltungen IIS
Am Wolfsmantel 33
91058 Erlangen
Telefon +49 (0) 91 31 / 7 76-62 44
Fax      +49 (0) 91 31 / 7 76-20 99
E-Mail: david.worrall@iis.fraunhofer.de
Internet: www.iis.fraunhofer.de

Send bugs reports to the Sourceforge bug trackers
csound6:
           https://sourceforge.net/p/csound/tickets/
csound5:
           https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

______________________________________
Prof. Dr. David Worrall
Emerging Audio Research (EAR)
Audio Department
International Audio Laboratories Erlangen
Fraunhofer-Institut für Integrierte Schaltungen IIS
Am Wolfsmantel 33
91058 Erlangen
Telefon +49 (0) 91 31 / 7 76-62 44
Fax +49 (0) 91 31 / 7 76-20 99
E-Mail: david.worrall@iis.fraunhofer.de
Internet: www.iis.fraunhofer.de

Date	2013-11-23 16:41
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	(Apologies for the mess the mailer made of my previous post - Here is is again - hopefully in a more readable form.) The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++. Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms. They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda * apptools 4.2.0 * astropy 0.2.5 * atom 0.3.4 * beautiful-soup 4.3.1 * binstar 0.3.1 * biopython 1.62 * bitarray 0.8.1 * blaze 0.3 * bokeh 0.2 * boto 2.15.0 * cairo 1.12.2 L * casuarius 1.1 * chaco 4.3.0 * colorama 0.2.7 * configobj 4.7.2 * cubes 0.10.2 * curl 7.30.0 LM * cython 0.19.2 * dateutil 2.1 * disco 0.4.4 L * distribute 0.6.45 * docutils 0.11 * dynd-python 0.5.0 * enable 4.3.0 * enaml 0.8.3 * envisage 4.3.0 * erlang R15B01 L * flask 0.10.1 * freetype 2.4.10 * gevent 0.13.8 * gevent-websocket 0.3.6 * gevent_zeromq 0.2.5 * greenlet 0.4.1 * grin 1.2.1 * h5py 2.2.0 * hdf5 1.8.9 * imaging 1.1.7 * ipython 1.1.0 * itsdangerous 0.23 * jinja2 2.7.1 * keyring 3.2 * launcher 0.1.2 * libevent 2.0.20 * libnetcdf 4.2.1.1 LM * libpng 1.5.13 LM * libtiff 4.0.2 LM * libxml2 2.9.0 LM * libxslt 1.1.28 LM * llvm 3.3 * llvmmath 0.1.1 * llvmpy 0.12.0 * lxml 3.2.3 * markupsafe 0.18 * matplotlib 1.3.1 * mayavi 4.3.0 * mdp 3.3 * menuinst 1.0.3 W * meta 0.4.2.dev * mingw 4.7 W * mpi4py 1.3 L * mpich2 1.4.1p1 L * netcdf4 1.0.6 LM * networkx 1.8.1 * nltk 2.0.4 * nose 1.3.0 * numba 0.11.0 * numexpr 2.2.2 * numpy 1.7.1 * opencv 2.4.6 L * openpyxl 1.6.2 * pandas 0.12.0 * patsy 0.2.1 * pep8 1.4.6 * pip 1.4.1 * ply 3.4 * psutil 1.1.2 * py 1.4.17 * py2cairo 1.10.0 L * pyaudio 0.2.7 M * pycosat 0.6.0 * pycparser 2.9.1 * pycrypto 2.6.1 * pycurl 7.19.0 LM * pyface 4.3.0 * pyflakes 0.7.3 * pygments 1.6 * pykit 0.1.0 * pyparsing 1.5.6 * pyreadline 2.0.dev W* pysal 1.6.0 * pysam 0.6 LM * pyside 1.2.1 * pytables 3.0.0 * pytest 2.4.2 * python 2.7.5 * pytz 2013b * pywin32 218.4 W * pyyaml 3.10 * pyzmq 2.2.0.1 * qt 4.8.5 * redis 2.6.9 LM * redis-py 2.7.2 LM * requests 1.2.3 * rope 0.9.4 * scikit-image 0.9.3 * scikit-learn 0.14.1 * scipy 0.13.0 * six 1.4.1 * sphinx 1.1.3 * spyder 2.2.5 * sqlalchemy 0.8.3 * statsmodels 0.5.0 * sympy 0.7.3 * theano 0.5.0 L * tornado 3.1.1 * traits 4.3.0 * traitsui 4.3.0 * vtk 5.10.1 * werkzeug 0.9.4 * xlrd 0.9.2 * xlwt 0.7.5 * yaml 0.1.4 LM * zeromq 2.2.0 LM * zlib 1.2.7 On 22.11.2013, at 22:18, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: What is this major scientific packaging you’ve mentioned? I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need for a custom build, on OSX. Victor On 22 Nov 2013, at 15:46, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Of course! no worries….. D. On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote: hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com <mailto:forrest.cahoon@gmail.com>> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com <mailto:stevenyi@gmail.com>> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de> Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de> Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-23 16:43
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	(Apologies for the mess the mailer made of my previous post - Here is is again - hopefully in a more readable form.) The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++. Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms. They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda * apptools 4.2.0 * astropy 0.2.5 * atom 0.3.4 * beautiful-soup 4.3.1 * binstar 0.3.1 * biopython 1.62 * bitarray 0.8.1 * blaze 0.3 * bokeh 0.2 * boto 2.15.0 * cairo 1.12.2 L * casuarius 1.1 * chaco 4.3.0 * colorama 0.2.7 * configobj 4.7.2 * cubes 0.10.2 * curl 7.30.0 LM * cython 0.19.2 * dateutil 2.1 * disco 0.4.4 L * distribute 0.6.45 * docutils 0.11 * dynd-python 0.5.0 * enable 4.3.0 * enaml 0.8.3 * envisage 4.3.0 * erlang R15B01 L * flask 0.10.1 * freetype 2.4.10 * gevent 0.13.8 * gevent-websocket 0.3.6 * gevent_zeromq 0.2.5 * greenlet 0.4.1 * grin 1.2.1 * h5py 2.2.0 * hdf5 1.8.9 * imaging 1.1.7 * ipython 1.1.0 * itsdangerous 0.23 * jinja2 2.7.1 * keyring 3.2 * launcher 0.1.2 * libevent 2.0.20 * libnetcdf 4.2.1.1 LM * libpng 1.5.13 LM * libtiff 4.0.2 LM * libxml2 2.9.0 LM * libxslt 1.1.28 LM * llvm 3.3 * llvmmath 0.1.1 * llvmpy 0.12.0 * lxml 3.2.3 * markupsafe 0.18 * matplotlib 1.3.1 * mayavi 4.3.0 * mdp 3.3 * menuinst 1.0.3 W * meta 0.4.2.dev * mingw 4.7 W * mpi4py 1.3 L * mpich2 1.4.1p1 L * netcdf4 1.0.6 LM * networkx 1.8.1 * nltk 2.0.4 * nose 1.3.0 * numba 0.11.0 * numexpr 2.2.2 * numpy 1.7.1 * opencv 2.4.6 L * openpyxl 1.6.2 * pandas 0.12.0 * patsy 0.2.1 * pep8 1.4.6 * pip 1.4.1 * ply 3.4 * psutil 1.1.2 * py 1.4.17 * py2cairo 1.10.0 L * pyaudio 0.2.7 M * pycosat 0.6.0 * pycparser 2.9.1 * pycrypto 2.6.1 * pycurl 7.19.0 LM * pyface 4.3.0 * pyflakes 0.7.3 * pygments 1.6 * pykit 0.1.0 * pyparsing 1.5.6 * pyreadline 2.0.dev W* pysal 1.6.0 * pysam 0.6 LM * pyside 1.2.1 * pytables 3.0.0 * pytest 2.4.2 * python 2.7.5 * pytz 2013b * pywin32 218.4 W * pyyaml 3.10 * pyzmq 2.2.0.1 * qt 4.8.5 * redis 2.6.9 LM * redis-py 2.7.2 LM * requests 1.2.3 * rope 0.9.4 * scikit-image 0.9.3 * scikit-learn 0.14.1 * scipy 0.13.0 * six 1.4.1 * sphinx 1.1.3 * spyder 2.2.5 * sqlalchemy 0.8.3 * statsmodels 0.5.0 * sympy 0.7.3 * theano 0.5.0 L * tornado 3.1.1 * traits 4.3.0 * traitsui 4.3.0 * vtk 5.10.1 * werkzeug 0.9.4 * xlrd 0.9.2 * xlwt 0.7.5 * yaml 0.1.4 LM * zeromq 2.2.0 LM * zlib 1.2.7 On 22.11.2013, at 22:18, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: What is this major scientific packaging you’ve mentioned? I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need for a custom build, on OSX. Victor On 22 Nov 2013, at 15:46, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Of course! no worries….. D. On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote: hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com <mailto:forrest.cahoon@gmail.com>> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com <mailto:stevenyi@gmail.com>> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de> Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de> Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-23 17:07
From	Victor Lazzarini
Subject	Re: [Csnd] "odd" csound6 build on OSX
	Do you think it is time we do bindings for Python 3 too? Victor On 23 Nov 2013, at 16:43, David Worrall wrote: > (Apologies for the mess the mailer made of my previous post - Here is is again - hopefully in a more readable form.) > > > The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++. > > Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms. > They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda > > * apptools 4.2.0 * astropy 0.2.5 * atom 0.3.4 * beautiful-soup 4.3.1 > * binstar 0.3.1 * biopython 1.62 * bitarray 0.8.1 * blaze 0.3 > * bokeh 0.2 * boto 2.15.0 * cairo 1.12.2 L * casuarius 1.1 > * chaco 4.3.0 * colorama 0.2.7 * configobj 4.7.2 * cubes 0.10.2 > * curl 7.30.0 LM * cython 0.19.2 * dateutil 2.1 * disco 0.4.4 L > * distribute 0.6.45 * docutils 0.11 * dynd-python 0.5.0 * enable 4.3.0 > * enaml 0.8.3 * envisage 4.3.0 * erlang R15B01 L * flask 0.10.1 > * freetype 2.4.10 * gevent 0.13.8 * gevent-websocket 0.3.6 * gevent_zeromq 0.2.5 > * greenlet 0.4.1 * grin 1.2.1 * h5py 2.2.0 * hdf5 1.8.9 > * imaging 1.1.7 * ipython 1.1.0 * itsdangerous 0.23 * jinja2 2.7.1 > * keyring 3.2 * launcher 0.1.2 * libevent 2.0.20 * libnetcdf 4.2.1.1 LM > * libpng 1.5.13 LM * libtiff 4.0.2 LM * libxml2 2.9.0 LM * libxslt 1.1.28 LM > * llvm 3.3 * llvmmath 0.1.1 * llvmpy 0.12.0 * lxml 3.2.3 > * markupsafe 0.18 * matplotlib 1.3.1 * mayavi 4.3.0 * mdp 3.3 > * menuinst 1.0.3 W * meta 0.4.2.dev * mingw 4.7 W * mpi4py 1.3 L > * mpich2 1.4.1p1 L * netcdf4 1.0.6 LM * networkx 1.8.1 * nltk 2.0.4 > * nose 1.3.0 * numba 0.11.0 * numexpr 2.2.2 * numpy 1.7.1 > * opencv 2.4.6 L * openpyxl 1.6.2 * pandas 0.12.0 * patsy 0.2.1 > * pep8 1.4.6 * pip 1.4.1 * ply 3.4 * psutil 1.1.2 > * py 1.4.17 * py2cairo 1.10.0 L * pyaudio 0.2.7 M * pycosat 0.6.0 > * pycparser 2.9.1 * pycrypto 2.6.1 * pycurl 7.19.0 LM * pyface 4.3.0 > * pyflakes 0.7.3 * pygments 1.6 * pykit 0.1.0 * pyparsing 1.5.6 > * pyreadline 2.0.dev W* pysal 1.6.0 * pysam 0.6 LM * pyside 1.2.1 > * pytables 3.0.0 * pytest 2.4.2 * python 2.7.5 * pytz 2013b > * pywin32 218.4 W * pyyaml 3.10 * pyzmq 2.2.0.1 * qt 4.8.5 > * redis 2.6.9 LM * redis-py 2.7.2 LM * requests 1.2.3 * rope 0.9.4 > * scikit-image 0.9.3 * scikit-learn 0.14.1 * scipy 0.13.0 * six 1.4.1 > * sphinx 1.1.3 * spyder 2.2.5 * sqlalchemy 0.8.3 * statsmodels 0.5.0 > * sympy 0.7.3 * theano 0.5.0 L * tornado 3.1.1 * traits 4.3.0 > * traitsui 4.3.0 * vtk 5.10.1 * werkzeug 0.9.4 * xlrd 0.9.2 > * xlwt 0.7.5 * yaml 0.1.4 LM * zeromq 2.2.0 LM * zlib 1.2.7 > > > > > > On 22.11.2013, at 22:18, Victor Lazzarini wrote: > >> What is this major scientific packaging you’ve mentioned? >> >> I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need >> for a custom build, on OSX. >> >> Victor >> >> On 22 Nov 2013, at 15:46, David Worrall wrote: >> >>> Of course! no worries….. >>> D. >>> >>> >>> On 22.11.2013, at 16:27, joachim heintz wrote: >>> >>>> hi david - >>>> >>>> if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). >>>> >>>> best - >>>> >>>> joachim >>>> >>>> >>>> Am 22.11.2013 09:44, schrieb David Worrall: >>>>> Hi Steven, >>>>> >>>>> Thanks for that - it works like a charm :-) >>>>> >>>>> So now we have a csound that works with at least one major packaging >>>>> environment for scientific work on OSX. >>>>> >>>>> Thanks to all who have contributed to this. >>>>> >>>>> I'll write up the build process and post a link for those interested. >>>>> >>>>> David >>>>> >>>>> >>>>> On 21.11.2013, at 18:02, Forrest Cahoon >>>> > wrote: >>>>> >>>>>> Hi David, >>>>>> >>>>>> Are you using the develop branch? If not you should be able to do >>>>>> "git checkout develop" and do a pull after to get the latest from >>>>>> develop. Let me know and we can continue diagnosing from there. >>>>>> >>>>>> All best, >>>>>> Steven >>>>>> >>>>>> On Nov 21, 2013 11:00 PM, "David Worrall" >>>>>> >>>>> > wrote: >>>>>> >>>>>> Hi Stephen, >>>>>> Apologies for my delay in replying… >>>>>> >>>>>> I've done as you suggested, and double-checked it. Same result, >>>>>> I'm afraid. >>>>>> i.e. I have sound building against the system python and csnd6 >>>>>> works fine with it. >>>>>> Same trap error. >>>>>> >>>>>> I have resisted altering the Makefiles, but when grep >>>>>> for PYTHON_LIBRARY I see it is still linking to the system python >>>>>> library: >>>>>> >>>>>> [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* >>>>>> ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib >>>>>> ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND >>>>>> ./build/CMakeCache.txt:1219://ADVANCED property for variable: >>>>>> PYTHON_LIBRARY >>>>>> ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 >>>>>> ./build/CMakeCache.txt:1221://ADVANCED property for variable: >>>>>> PYTHON_LIBRARY_DEBUG >>>>>> ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 >>>>>> ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) >>>>>> ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS >>>>>> ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} >>>>>> ${PYTHON_LIBRARY} libcsnd6) >>>>>> >>>>>> am I git-ing the correct version? >>>>>> I could try hand-editing the make files (after ccmake?) if that >>>>>> would help as a x-check. If so, which ones? >>>>>> >>>>>> Thanks for your assistance, >>>>>> >>>>>> David >>>>>> >>>>>> >>>>>> >>>>>> On 18.11.2013, at 17:07, Steven Yi >>>>> > wrote: >>>>>> >>>>>>> Hi David, >>>>>>> >>>>>>> I think this part is key as to why you're getting the thread >>>>>>> state error: >>>>>>> >>>>>>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>>>>>> (compatibility version 2.7.0, current version 2.7.2) >>>>>>> >>>>>>> the _csnd6.so is linking to the system python. I had removed that a >>>>>>> while ago but I just went through the history and found that someone >>>>>>> had put PYTHON_LIBRARY back in to the library link list. >>>>>>> >>>>>>> I've taken that back out and tested on OSX. If I remember correctly, >>>>>>> it worked fine on Windows and Linux this way too. If others have >>>>>>> problems compiling on those platforms, please let me know. >>>>>>> >>>>>>> Could you pull the latest from GIT and try compiling again? I'm >>>>>>> going >>>>>>> to assume that the releases I've done since 2013-03-17 when that >>>>>>> commit re-added the python lib to linking have the system python >>>>>>> linked in. That shouldn't have been the case. >>>>>>> >>>>>>> Also Dave, you might want to try just compiling against the system >>>>>>> python without any changes, then just install the python stuff into >>>>>>> your anaconda python. With this change, it should work. (It was one >>>>>>> of the motivating reasons for removing the python lib link back >>>>>>> when I >>>>>>> first did this). >>>>>>> >>>>>>> steven >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Nov 14, 2013 at 11:04 AM, David Worrall >>>>>>> >>>>>> > wrote: >>>>>>>> An update on this attempt to use a "non-standard" python in a >>>>>>>> csound6 build >>>>>>>> on OSX. >>>>>>>> >>>>>>>> The bug reported earlier that prevented the python interface >>>>>>>> being build was >>>>>>>> caused by SWIG, specifically v 2.0.10 - the most recent version >>>>>>>> provided and >>>>>>>> installed by MacPorts. >>>>>>>> With the latest version of SWIG (2.0.11) from their own website, >>>>>>>> the bug >>>>>>>> disappear and the Python interface seems to work - at least w. >>>>>>>> the OSX >>>>>>>> system python: >>>>>>>> % /usr/bin/python >>>>>>>> Python 2.7.2 (default, Oct 11 2012, 20:14:37) >>>>>>>> [GCC 4.2.1 Compatible Apple Clang 4.0 >>>>>>>> (tags/Apple/clang-418.0.60)] on darwin >>>>>>>> Type "help", "copyright", "credits" or "license" for more >>>>>>>> information. >>>>>>>>>>> import csnd6 >>>>>>>>>>> >>>>>>>> with that sorted, the build works w. the OSX system python. >>>>>>>> >>>>>>>> The next step is to try to get it to work w. the anaconda python >>>>>>>> framework. >>>>>>>> At the moment it exceptions on import: >>>>>>>> % python >>>>>>>> Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, >>>>>>>> 22:20:13) >>>>>>>> [GCC 4.0.1 (Apple Inc. build 5493)] on darwin >>>>>>>> Type "help", "copyright", "credits" or "license" for more >>>>>>>> information. >>>>>>>>>>> import csnd6 >>>>>>>> Fatal Python error: PyThreadState_Get: no current thread >>>>>>>> Abort >>>>>>>> % >>>>>>>> This is the same exception I get with the import of csnd6 from >>>>>>>> the OSX >>>>>>>> installer package. FYI: >>>>>>>> % otool -L _csnd6.so >>>>>>>> _csnd6.so: >>>>>>>> CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility >>>>>>>> version 6.0.0, >>>>>>>> current version 0.0.0) >>>>>>>> /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, >>>>>>>> current >>>>>>>> version 2.25.0) >>>>>>>> /System/Library/Frameworks/Python.framework/Versions/2.7/Python >>>>>>>> (compatibility version 2.7.0, current version 2.7.2) >>>>>>>> libcsnd6.6.0.dylib (compatibility version 6.0.0, current version >>>>>>>> 0.0.0) >>>>>>>> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current >>>>>>>> version >>>>>>>> 56.0.0) >>>>>>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current >>>>>>>> version >>>>>>>> 169.3.0) >>>>>>>> % >>>>>>>> >>>>>>>> So perhaps the library is sensitive to the different versions of >>>>>>>> python >>>>>>>> (v2.7.2. c.f v2.7.5) ?? >>>>>>>> ------ >>>>>>>> Stephen, you said >>>>>>>> >>>>>>>> I think the python library should work regardless of what python >>>>>>>> installtion it is running with. At least, we had done some work to >>>>>>>> not link with libpython, so that it lib_csnd6.dylib could load with >>>>>>>> any python version. Perhaps that's changed? >>>>>>>> >>>>>>>> As for CMake, you can override any value from the command-line >>>>>>>> or from >>>>>>>> Custom.cmake. So you should be able to use: >>>>>>>> >>>>>>>> -DPYTHON_MODULE_INSTALL_DIR=/my/location >>>>>>>> -DPYTHON_INCLUDE_DIR=/path/to/my/python >>>>>>>> >>>>>>>> >>>>>>>> when I did these overrides, the build aborted on meeting >>>>>>>> #include >>>>>>>> in .../Opcodes/py/pythonopcodes.c >>>>>>>> >>>>>>>> so I copied the Python.h from the python I'm using (2.7.5) and >>>>>>>> altered it to >>>>>>>> #include "Python.h" >>>>>>>> and it built successfully. >>>>>>>> >>>>>>>> But the import of the resulting csnd6.py still causes the python >>>>>>>> exception, >>>>>>>> as above. >>>>>>>> >>>>>>>> Thoughts as to where to look next? >>>>>>>> >>>>>>>> thanks, >>>>>>>> >>>>>>>> David >>>>>>>> >>>>>>>> >>>>>>>> On 08.11.2013, at 17:48, David Worrall >>>>>>>> >>>>>>> > >>>>>>>> wrote: >>>>>>>> >>>>>>>> Thanks for your help! >>>>>>>> >>>>>>>> I have some opcode questions as well, but firstly, the python >>>>>>>> interface... >>>>>>>> >>>>>>>> In Custom.cmake, I've altered >>>>>>>> set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") >>>>>>>> (the Python I'm using) >>>>>>>> >>>>>>>> In CMakeLists.txt, do I need to change >>>>>>>> if(APPLE) >>>>>>>> if(BUILD_INSTALLER) >>>>>>>> …. >>>>>>>> else() >>>>>>>> get_filename_component(PYTHON_MODULE_INSTALL_DIR >>>>>>>> "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) >>>>>>>> >>>>>>>> or do I copy the change to Custom.cmake? >>>>>>>> i.e. does Custom.cmake override settings in CMakeLists.txt? >>>>>>>> >>>>>>>> Is there anything else required to get the libraries build for >>>>>>>> the python on >>>>>>>> question? >>>>>>>> >>>>>>>> thanks, >>>>>>>> David >>>>>>>> >>>>>>>> On 08.11.2013, at 12:06, Victor Lazzarini >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? >>>>>>>> You can put your custom cmake configuration there. >>>>>>>> >>>>>>>> On 8 Nov 2013, at 10:56, David Worrall >>>>>>>> >>>>>>> > >>>>>>>> wrote: >>>>>>>> >>>>>>>> I'm trying to do something conceptually very simple but haven't >>>>>>>> succeeded. >>>>>>>> I'm trying to build csound6 from a git clone (depth=1) sources, >>>>>>>> with two >>>>>>>> modifications to the standard build (which works fine): >>>>>>>> >>>>>>>> a) Install the dependencies using MacPorts, and >>>>>>>> b) make it using a python2.7 which is not installed in one of >>>>>>>> the "normal" >>>>>>>> places (but is is the shell's $PATH) >>>>>>>> >>>>>>>> What do I need to do to effect that (in terms of changes to >>>>>>>> $PATH, and/or >>>>>>>> csound-git/CMakeLists.txt >>>>>>>> I can provide output from cmake if that helps. >>>>>>>> >>>>>>>> Perhaps it is documented somewhere - but I haven't found it. >>>>>>>> >>>>>>>> >>>>>>>> Can anyone help? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> David >>>>>>>> >>>>>>>> … >>>>> ... >>>>> ______________________________________ >>>>> Prof. Dr. David Worrall >>>>> Emerging Audio Research (EAR) >>>>> Audio Department >>>>> International Audio Laboratories Erlangen >>>>> Fraunhofer-Institut für Integrierte Schaltungen IIS >>>>> Am Wolfsmantel 33 >>>>> 91058 Erlangen >>>>> Telefon +49 (0) 91 31 / 7 76-62 44 >>>>> Fax +49 (0) 91 31 / 7 76-20 99 >>>>> E-Mail: david.worrall@iis.fraunhofer.de >>>>> >>>>> Internet: www.iis.fraunhofer.de >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> Send bugs reports to the Sourceforge bug trackers >>>> csound6: >>>> https://sourceforge.net/p/csound/tickets/ >>>> csound5: >>>> https://sourceforge.net/p/csound/bugs/ >>>> Discussions of bugs and features can be posted here >>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" >>>> >>>> >>> >>> ______________________________________ >>> Prof. Dr. David Worrall >>> Emerging Audio Research (EAR) >>> Audio Department >>> International Audio Laboratories Erlangen >>> Fraunhofer-Institut für Integrierte Schaltungen IIS >>> Am Wolfsmantel 33 >>> 91058 Erlangen >>> Telefon +49 (0) 91 31 / 7 76-62 44 >>> Fax +49 (0) 91 31 / 7 76-20 99 >>> E-Mail: david.worrall@iis.fraunhofer.de >>> Internet: www.iis.fraunhofer.de >>> >>> >>> >>> >> >> >> >> Send bugs reports to the Sourceforge bug trackers >> csound6: >> https://sourceforge.net/p/csound/tickets/ >> csound5: >> https://sourceforge.net/p/csound/bugs/ >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" >> >> > > ______________________________________ > Prof. Dr. David Worrall > Emerging Audio Research (EAR) > Audio Department > International Audio Laboratories Erlangen > Fraunhofer-Institut für Integrierte Schaltungen IIS > Am Wolfsmantel 33 > 91058 Erlangen > Telefon +49 (0) 91 31 / 7 76-62 44 > Fax +49 (0) 91 31 / 7 76-20 99 > E-Mail: david.worrall@iis.fraunhofer.de > Internet: www.iis.fraunhofer.de > > > >

Date	2013-11-25 15:14
From	David Worrall
Subject	Re: [Csnd] "odd" csound6 build on OSX
	I have yet to see a killer-app in Python3 only so the only info I have to go on is the number of packages available. Python 3 is more of a transform than an upgrade if you get my meaning. So I don't see a pressing need ATM. It wouldn't hurt to test it. Perhaps others on this list are using Python 3 for other things and have another opinion. D. On 23.11.2013, at 18:07, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Do you think it is time we do bindings for Python 3 too? Victor On 23 Nov 2013, at 16:43, David Worrall <david.worrall@iis.fraunhofer.de> wrote: (Apologies for the mess the mailer made of my previous post - Here is is again - hopefully in a more readable form.) The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++. Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms. They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda * apptools 4.2.0 * astropy 0.2.5 * atom 0.3.4 * beautiful-soup 4.3.1 * binstar 0.3.1 * biopython 1.62 * bitarray 0.8.1 * blaze 0.3 * bokeh 0.2 * boto 2.15.0 * cairo 1.12.2 L * casuarius 1.1 * chaco 4.3.0 * colorama 0.2.7 * configobj 4.7.2 * cubes 0.10.2 * curl 7.30.0 LM * cython 0.19.2 * dateutil 2.1 * disco 0.4.4 L * distribute 0.6.45 * docutils 0.11 * dynd-python 0.5.0 * enable 4.3.0 * enaml 0.8.3 * envisage 4.3.0 * erlang R15B01 L * flask 0.10.1 * freetype 2.4.10 * gevent 0.13.8 * gevent-websocket 0.3.6 * gevent_zeromq 0.2.5 * greenlet 0.4.1 * grin 1.2.1 * h5py 2.2.0 * hdf5 1.8.9 * imaging 1.1.7 * ipython 1.1.0 * itsdangerous 0.23 * jinja2 2.7.1 * keyring 3.2 * launcher 0.1.2 * libevent 2.0.20 * libnetcdf 4.2.1.1 LM * libpng 1.5.13 LM * libtiff 4.0.2 LM * libxml2 2.9.0 LM * libxslt 1.1.28 LM * llvm 3.3 * llvmmath 0.1.1 * llvmpy 0.12.0 * lxml 3.2.3 * markupsafe 0.18 * matplotlib 1.3.1 * mayavi 4.3.0 * mdp 3.3 * menuinst 1.0.3 W * meta 0.4.2.dev * mingw 4.7 W * mpi4py 1.3 L * mpich2 1.4.1p1 L * netcdf4 1.0.6 LM * networkx 1.8.1 * nltk 2.0.4 * nose 1.3.0 * numba 0.11.0 * numexpr 2.2.2 * numpy 1.7.1 * opencv 2.4.6 L * openpyxl 1.6.2 * pandas 0.12.0 * patsy 0.2.1 * pep8 1.4.6 * pip 1.4.1 * ply 3.4 * psutil 1.1.2 * py 1.4.17 * py2cairo 1.10.0 L * pyaudio 0.2.7 M * pycosat 0.6.0 * pycparser 2.9.1 * pycrypto 2.6.1 * pycurl 7.19.0 LM * pyface 4.3.0 * pyflakes 0.7.3 * pygments 1.6 * pykit 0.1.0 * pyparsing 1.5.6 * pyreadline 2.0.dev W* pysal 1.6.0 * pysam 0.6 LM * pyside 1.2.1 * pytables 3.0.0 * pytest 2.4.2 * python 2.7.5 * pytz 2013b * pywin32 218.4 W * pyyaml 3.10 * pyzmq 2.2.0.1 * qt 4.8.5 * redis 2.6.9 LM * redis-py 2.7.2 LM * requests 1.2.3 * rope 0.9.4 * scikit-image 0.9.3 * scikit-learn 0.14.1 * scipy 0.13.0 * six 1.4.1 * sphinx 1.1.3 * spyder 2.2.5 * sqlalchemy 0.8.3 * statsmodels 0.5.0 * sympy 0.7.3 * theano 0.5.0 L * tornado 3.1.1 * traits 4.3.0 * traitsui 4.3.0 * vtk 5.10.1 * werkzeug 0.9.4 * xlrd 0.9.2 * xlwt 0.7.5 * yaml 0.1.4 LM * zeromq 2.2.0 LM * zlib 1.2.7 On 22.11.2013, at 22:18, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: What is this major scientific packaging you’ve mentioned? I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need for a custom build, on OSX. Victor On 22 Nov 2013, at 15:46, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Of course! no worries….. D. On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote: hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com <mailto:forrest.cahoon@gmail.com>> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com <mailto:stevenyi@gmail.com>> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de> Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de> Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de

Date	2013-11-25 15:23
From	Michael Gogins
Subject	Re: [Csnd] "odd" csound6 build on OSX
	The time to bind for Python 3 is when the scientific python community has moved to Python 3. These are the people who make the libraries that algorithmic composers would use. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Nov 25, 2013 at 10:14 AM, David Worrall <david.worrall@iis.fraunhofer.de> wrote: I have yet to see a killer-app in Python3 only so the only info I have to go on is the number of packages available. Python 3 is more of a transform than an upgrade if you get my meaning. So I don't see a pressing need ATM. It wouldn't hurt to test it. Perhaps others on this list are using Python 3 for other things and have another opinion. D. On 23.11.2013, at 18:07, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: Do you think it is time we do bindings for Python 3 too? Victor On 23 Nov 2013, at 16:43, David Worrall <david.worrall@iis.fraunhofer.de> wrote: (Apologies for the mess the mailer made of my previous post - Here is is again - hopefully in a more readable form.) The one I'm experimenting with at the moment is for python visualization and data exploration by Anaconda from Continuum Analytics (http://www.continuum.io/ ). I'm interested in extending this to "python visualization, sonification and data exploration" using csound6 ++. Conda Version 1.8.0 currently manages the versioning of the packages listed below: for Python 2.7 on all platforms. They also have a Python 3 set. Package compatibility is a major issue with this language so it is an enormous help. You can read about their approach to this here: http://www.continuum.io/blog/new-advances-in-conda * apptools 4.2.0 * astropy 0.2.5 * atom 0.3.4 * beautiful-soup 4.3.1 * binstar 0.3.1 * biopython 1.62 * bitarray 0.8.1 * blaze 0.3 * bokeh 0.2 * boto 2.15.0 * cairo 1.12.2 L * casuarius 1.1 * chaco 4.3.0 * colorama 0.2.7 * configobj 4.7.2 * cubes 0.10.2 * curl 7.30.0 LM * cython 0.19.2 * dateutil 2.1 * disco 0.4.4 L * distribute 0.6.45 * docutils 0.11 * dynd-python 0.5.0 * enable 4.3.0 * enaml 0.8.3 * envisage 4.3.0 * erlang R15B01 L * flask 0.10.1 * freetype 2.4.10 * gevent 0.13.8 * gevent-websocket 0.3.6 * gevent_zeromq 0.2.5 * greenlet 0.4.1 * grin 1.2.1 * h5py 2.2.0 * hdf5 1.8.9 * imaging 1.1.7 * ipython 1.1.0 * itsdangerous 0.23 * jinja2 2.7.1 * keyring 3.2 * launcher 0.1.2 * libevent 2.0.20 * libnetcdf 4.2.1.1 LM * libpng 1.5.13 LM * libtiff 4.0.2 LM * libxml2 2.9.0 LM * libxslt 1.1.28 LM * llvm 3.3 * llvmmath 0.1.1 * llvmpy 0.12.0 * lxml 3.2.3 * markupsafe 0.18 * matplotlib 1.3.1 * mayavi 4.3.0 * mdp 3.3 * menuinst 1.0.3 W * meta 0.4.2.dev * mingw 4.7 W * mpi4py 1.3 L * mpich2 1.4.1p1 L * netcdf4 1.0.6 LM * networkx 1.8.1 * nltk 2.0.4 * nose 1.3.0 * numba 0.11.0 * numexpr 2.2.2 * numpy 1.7.1 * opencv 2.4.6 L * openpyxl 1.6.2 * pandas 0.12.0 * patsy 0.2.1 * pep8 1.4.6 * pip 1.4.1 * ply 3.4 * psutil 1.1.2 * py 1.4.17 * py2cairo 1.10.0 L * pyaudio 0.2.7 M * pycosat 0.6.0 * pycparser 2.9.1 * pycrypto 2.6.1 * pycurl 7.19.0 LM * pyface 4.3.0 * pyflakes 0.7.3 * pygments 1.6 * pykit 0.1.0 * pyparsing 1.5.6 * pyreadline 2.0.dev W* pysal 1.6.0 * pysam 0.6 LM * pyside 1.2.1 * pytables 3.0.0 * pytest 2.4.2 * python 2.7.5 * pytz 2013b * pywin32 218.4 W * pyyaml 3.10 * pyzmq 2.2.0.1 * qt 4.8.5 * redis 2.6.9 LM * redis-py 2.7.2 LM * requests 1.2.3 * rope 0.9.4 * scikit-image 0.9.3 * scikit-learn 0.14.1 * scipy 0.13.0 * six 1.4.1 * sphinx 1.1.3 * spyder 2.2.5 * sqlalchemy 0.8.3 * statsmodels 0.5.0 * sympy 0.7.3 * theano 0.5.0 L * tornado 3.1.1 * traits 4.3.0 * traitsui 4.3.0 * vtk 5.10.1 * werkzeug 0.9.4 * xlrd 0.9.2 * xlwt 0.7.5 * yaml 0.1.4 LM * zeromq 2.2.0 LM * zlib 1.2.7 On 22.11.2013, at 22:18, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: What is this major scientific packaging you’ve mentioned? I have Csound with Python, scipy, numpy, matplotlib and ipython here without any special need for a custom build, on OSX. Victor On 22 Nov 2013, at 15:46, David Worrall <david.worrall@iis.fraunhofer.de> wrote: Of course! no worries….. D. On 22.11.2013, at 16:27, joachim heintz <jh@joachimheintz.de> wrote: hi david - if you don't mind, i'll put it in the csound wiki on sourceforge after you have finished (http://sourceforge.net/p/csound/wiki/Home/). best - joachim Am 22.11.2013 09:44, schrieb David Worrall: Hi Steven, Thanks for that - it works like a charm :-) So now we have a csound that works with at least one major packaging environment for scientific work on OSX. Thanks to all who have contributed to this. I'll write up the build process and post a link for those interested. David On 21.11.2013, at 18:02, Forrest Cahoon <forrest.cahoon@gmail.com <mailto:forrest.cahoon@gmail.com>> wrote: Hi David, Are you using the develop branch? If not you should be able to do "git checkout develop" and do a pull after to get the latest from develop. Let me know and we can continue diagnosing from there. All best, Steven On Nov 21, 2013 11:00 PM, "David Worrall" <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Hi Stephen, Apologies for my delay in replying… I've done as you suggested, and double-checked it. Same result, I'm afraid. i.e. I have sound building against the system python and csnd6 works fine with it. Same trap error. I have resisted altering the Makefiles, but when grep for PYTHON_LIBRARY I see it is still linking to the system python library: [mbp288:~/sonipy/csound6-git] wor% grep -rn PYTHON_LIBRARY ./* ./build/CMakeCache.txt:547:PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.dylib ./build/CMakeCache.txt:550:PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND ./build/CMakeCache.txt:1219://ADVANCED property for variable: PYTHON_LIBRARY ./build/CMakeCache.txt:1220:PYTHON_LIBRARY-ADVANCED:INTERNAL=1 ./build/CMakeCache.txt:1221://ADVANCED property for variable: PYTHON_LIBRARY_DEBUG ./build/CMakeCache.txt:1222:PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 ./interfaces/CMakeLists.txt:56:MESSAGE(STATUS ${PYTHON_LIBRARY}) ./interfaces/CMakeLists.txt:80: set(swigpython_LIBS ${CSOUNDLIB} ${LIBSNDFILE_LIBRARY} ${LIBSNDFILE_LIBRARY} ${PYTHON_LIBRARY} libcsnd6) am I git-ing the correct version? I could try hand-editing the make files (after ccmake?) if that would help as a x-check. If so, which ones? Thanks for your assistance, David On 18.11.2013, at 17:07, Steven Yi <stevenyi@gmail.com <mailto:stevenyi@gmail.com>> wrote: Hi David, I think this part is key as to why you're getting the thread state error: /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) the _csnd6.so is linking to the system python. I had removed that a while ago but I just went through the history and found that someone had put PYTHON_LIBRARY back in to the library link list. I've taken that back out and tested on OSX. If I remember correctly, it worked fine on Windows and Linux this way too. If others have problems compiling on those platforms, please let me know. Could you pull the latest from GIT and try compiling again? I'm going to assume that the releases I've done since 2013-03-17 when that commit re-added the python lib to linking have the system python linked in. That shouldn't have been the case. Also Dave, you might want to try just compiling against the system python without any changes, then just install the python stuff into your anaconda python. With this change, it should work. (It was one of the motivating reasons for removing the python lib link back when I first did this). steven On Thu, Nov 14, 2013 at 11:04 AM, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: An update on this attempt to use a "non-standard" python in a csound6 build on OSX. The bug reported earlier that prevented the python interface being build was caused by SWIG, specifically v 2.0.10 - the most recent version provided and installed by MacPorts. With the latest version of SWIG (2.0.11) from their own website, the bug disappear and the Python interface seems to work - at least w. the OSX system python: % /usr/bin/python Python 2.7.2 (default, Oct 11 2012, 20:14:37) [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 with that sorted, the build works w. the OSX system python. The next step is to try to get it to work w. the anaconda python framework. At the moment it exceptions on import: % python Python 2.7.5 \|Anaconda 1.7.0 (x86_64)\| (default, Jun 28 2013, 22:20:13) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. import csnd6 Fatal Python error: PyThreadState_Get: no current thread Abort % This is the same exception I get with the import of csnd6 from the OSX installer package. FYI: % otool -L _csnd6.so _csnd6.so: CsoundLib64.framework/Versions/6.0/CsoundLib64 (compatibility version 6.0.0, current version 0.0.0) /opt/local/lib/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.25.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2) libcsnd6.6.0.dylib (compatibility version 6.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) % So perhaps the library is sensitive to the different versions of python (v2.7.2. c.f v2.7.5) ?? ------ Stephen, you said I think the python library should work regardless of what python installtion it is running with. At least, we had done some work to not link with libpython, so that it lib_csnd6.dylib could load with any python version. Perhaps that's changed? As for CMake, you can override any value from the command-line or from Custom.cmake. So you should be able to use: -DPYTHON_MODULE_INSTALL_DIR=/my/location -DPYTHON_INCLUDE_DIR=/path/to/my/python when I did these overrides, the build aborted on meeting #include<Python.h> in .../Opcodes/py/pythonopcodes.c so I copied the Python.h from the python I'm using (2.7.5) and altered it to #include "Python.h" and it built successfully. But the import of the resulting csnd6.py still causes the python exception, as above. Thoughts as to where to look next? thanks, David On 08.11.2013, at 17:48, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: Thanks for your help! I have some opcode questions as well, but firstly, the python interface... In Custom.cmake, I've altered set(PYTHON_INCLUDE_DIRS "/Users/wor/sonipy/anaconda/include") (the Python I'm using) In CMakeLists.txt, do I need to change if(APPLE) if(BUILD_INSTALLER) …. else() get_filename_component(PYTHON_MODULE_INSTALL_DIR "~/Library/Python/2.7/lib/python/site-packages" ABSOLUTE) or do I copy the change to Custom.cmake? i.e. does Custom.cmake override settings in CMakeLists.txt? Is there anything else required to get the libraries build for the python on question? thanks, David On 08.11.2013, at 12:06, Victor Lazzarini <Victor.Lazzarini@nuim.ie <mailto:Victor.Lazzarini@nuim.ie>> wrote: Did you try modifying Custom.cmake.ex and saving it as Custom.cmake? You can put your custom cmake configuration there. On 8 Nov 2013, at 10:56, David Worrall <david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de>> wrote: I'm trying to do something conceptually very simple but haven't succeeded. I'm trying to build csound6 from a git clone (depth=1) sources, with two modifications to the standard build (which works fine): a) Install the dependencies using MacPorts, and b) make it using a python2.7 which is not installed in one of the "normal" places (but is is the shell's $PATH) What do I need to do to effect that (in terms of changes to $PATH, and/or csound-git/CMakeLists.txt I can provide output from cmake if that helps. Perhaps it is documented somewhere - but I haven't found it. Can anyone help? Thanks, David … ... ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de <mailto:david.worrall@iis.fraunhofer.de> Internet: www.iis.fraunhofer.de <http://www.iis.fraunhofer.de> Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de Send bugs reports to the Sourceforge bug trackers csound6: https://sourceforge.net/p/csound/tickets/ csound5: https://sourceforge.net/p/csound/bugs/ Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" ______________________________________ Prof. Dr. David Worrall Emerging Audio Research (EAR) Audio Department International Audio Laboratories Erlangen Fraunhofer-Institut für Integrierte Schaltungen IIS Am Wolfsmantel 33 91058 Erlangen Telefon +49 (0) 91 31 / 7 76-62 44 Fax +49 (0) 91 31 / 7 76-20 99 E-Mail: david.worrall@iis.fraunhofer.de Internet: www.iis.fraunhofer.de