Csound Csound-dev Csound-tekno Search About

[Cs-dev] CsoundAC, STK, Cmake

Date2012-02-22 15:56
FromSteven Yi
Subject[Cs-dev] CsoundAC, STK, Cmake
Hi All,

Just an update.  I found that STK opcodes are built but are not
loading on OSX with CMake or SConstruct.  With SConstruct, the module
reports a 0 for loading correctly, but no entries in the opcode list.
WIth CMake, using "nm libstk.dylib | grep Module" shows no
csoundModule* functions.  Anyone have any thoughts on why those
functions would get stripped in CMake (or, just in development in
general)?  I assume it's a C++ flag that hasn't been set in CMake that
is in SConstruct, but I haven't found out what it is.  Also, why would
it load the module but have no opcodes when using SConstruct build?
(Note this is using stk source, not linking to libstk.a)

Also, CsoundAC seems to import fine on CMake and SConstruct builds and
show the same symbols when i do "import CsoundAC; dir(CsoundAC)".

steven

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

Date2012-02-22 16:13
FromSteven Yi
SubjectRe: [Cs-dev] CsoundAC, STK, Cmake
One note, I found why the symbols weren't showing with CMake on STK,
which was due to an incorrect appending of stkOpcodes.cpp to the list
of sources. I corrected that and am now at the same situation as I
have with Scons-built libstk.dylib, which is it that the library loads
but now opcodes show up. (CMake change pushed to git)

Thanks,
steven

On Wed, Feb 22, 2012 at 3:56 PM, Steven Yi  wrote:
> Hi All,
>
> Just an update.  I found that STK opcodes are built but are not
> loading on OSX with CMake or SConstruct.  With SConstruct, the module
> reports a 0 for loading correctly, but no entries in the opcode list.
> WIth CMake, using "nm libstk.dylib | grep Module" shows no
> csoundModule* functions.  Anyone have any thoughts on why those
> functions would get stripped in CMake (or, just in development in
> general)?  I assume it's a C++ flag that hasn't been set in CMake that
> is in SConstruct, but I haven't found out what it is.  Also, why would
> it load the module but have no opcodes when using SConstruct build?
> (Note this is using stk source, not linking to libstk.a)
>
> Also, CsoundAC seems to import fine on CMake and SConstruct builds and
> show the same symbols when i do "import CsoundAC; dir(CsoundAC)".
>
> steven

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

Date2012-02-22 16:21
FromSteven Yi
SubjectRe: [Cs-dev] CsoundAC, STK, Cmake
Ah, and now it's fine, I just didn't have RAWWAVE_PATH set. (Though,
confusedly, I did have it set before and didn't see the opcodes...).
STK seems fine now, loading with both SCons and CMake.

Using the CMake build, I was able to run StrangeAtrractor.py and
Koch.py.  Michael: I'm not sure what you need for CsoundAC and the
whole business with static/dynamic libs, but the SConstruct stuff for
that was a bit tough to go through and I've spent a lot of time on
this and am going to go focus on my own work for a while.  If you
could give the latest CMake stuff a try, that'd be great and let me
know if there's any further issues with that.

Thanks,
steven

On Wed, Feb 22, 2012 at 4:13 PM, Steven Yi  wrote:
> One note, I found why the symbols weren't showing with CMake on STK,
> which was due to an incorrect appending of stkOpcodes.cpp to the list
> of sources. I corrected that and am now at the same situation as I
> have with Scons-built libstk.dylib, which is it that the library loads
> but now opcodes show up. (CMake change pushed to git)
>
> Thanks,
> steven
>
> On Wed, Feb 22, 2012 at 3:56 PM, Steven Yi  wrote:
>> Hi All,
>>
>> Just an update.  I found that STK opcodes are built but are not
>> loading on OSX with CMake or SConstruct.  With SConstruct, the module
>> reports a 0 for loading correctly, but no entries in the opcode list.
>> WIth CMake, using "nm libstk.dylib | grep Module" shows no
>> csoundModule* functions.  Anyone have any thoughts on why those
>> functions would get stripped in CMake (or, just in development in
>> general)?  I assume it's a C++ flag that hasn't been set in CMake that
>> is in SConstruct, but I haven't found out what it is.  Also, why would
>> it load the module but have no opcodes when using SConstruct build?
>> (Note this is using stk source, not linking to libstk.a)
>>
>> Also, CsoundAC seems to import fine on CMake and SConstruct builds and
>> show the same symbols when i do "import CsoundAC; dir(CsoundAC)".
>>
>> steven

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

Date2012-02-22 16:33
FromMichael Gogins
SubjectRe: [Cs-dev] CsoundAC, STK, Cmake
Thanks again for all your work on this. I will try the CMake build and
test it in the next day or so. If you were running StrangeAttractor,
that does use CsoundAC, so if your CsoundAC was built with CMake, we
should be good to go.

Best,
Mike

On Wed, Feb 22, 2012 at 11:21 AM, Steven Yi  wrote:
> Ah, and now it's fine, I just didn't have RAWWAVE_PATH set. (Though,
> confusedly, I did have it set before and didn't see the opcodes...).
> STK seems fine now, loading with both SCons and CMake.
>
> Using the CMake build, I was able to run StrangeAtrractor.py and
> Koch.py.  Michael: I'm not sure what you need for CsoundAC and the
> whole business with static/dynamic libs, but the SConstruct stuff for
> that was a bit tough to go through and I've spent a lot of time on
> this and am going to go focus on my own work for a while.  If you
> could give the latest CMake stuff a try, that'd be great and let me
> know if there's any further issues with that.
>
> Thanks,
> steven
>
> On Wed, Feb 22, 2012 at 4:13 PM, Steven Yi  wrote:
>> One note, I found why the symbols weren't showing with CMake on STK,
>> which was due to an incorrect appending of stkOpcodes.cpp to the list
>> of sources. I corrected that and am now at the same situation as I
>> have with Scons-built libstk.dylib, which is it that the library loads
>> but now opcodes show up. (CMake change pushed to git)
>>
>> Thanks,
>> steven
>>
>> On Wed, Feb 22, 2012 at 3:56 PM, Steven Yi  wrote:
>>> Hi All,
>>>
>>> Just an update.  I found that STK opcodes are built but are not
>>> loading on OSX with CMake or SConstruct.  With SConstruct, the module
>>> reports a 0 for loading correctly, but no entries in the opcode list.
>>> WIth CMake, using "nm libstk.dylib | grep Module" shows no
>>> csoundModule* functions.  Anyone have any thoughts on why those
>>> functions would get stripped in CMake (or, just in development in
>>> general)?  I assume it's a C++ flag that hasn't been set in CMake that
>>> is in SConstruct, but I haven't found out what it is.  Also, why would
>>> it load the module but have no opcodes when using SConstruct build?
>>> (Note this is using stk source, not linking to libstk.a)
>>>
>>> Also, CsoundAC seems to import fine on CMake and SConstruct builds and
>>> show the same symbols when i do "import CsoundAC; dir(CsoundAC)".
>>>
>>> steven
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

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

Date2012-02-22 16:39
FromSteven Yi
SubjectRe: [Cs-dev] CsoundAC, STK, Cmake
Sounds good, there does seem to be some other issues to sort out, as
some of the libraries that are built are coming out very large as I
think they may be statically linking to libcsound instead of
dynamically linking, but I am not certain.  But hopefully these things
should be much easier to sort out than the rest.  I'm going to give
Cmake a break rest of day today and will pick back up probably Friday
to take care of some other things.

Thanks!
steven

On Wed, Feb 22, 2012 at 4:33 PM, Michael Gogins
 wrote:
> Thanks again for all your work on this. I will try the CMake build and
> test it in the next day or so. If you were running StrangeAttractor,
> that does use CsoundAC, so if your CsoundAC was built with CMake, we
> should be good to go.
>
> Best,
> Mike
>
> On Wed, Feb 22, 2012 at 11:21 AM, Steven Yi  wrote:
>> Ah, and now it's fine, I just didn't have RAWWAVE_PATH set. (Though,
>> confusedly, I did have it set before and didn't see the opcodes...).
>> STK seems fine now, loading with both SCons and CMake.
>>
>> Using the CMake build, I was able to run StrangeAtrractor.py and
>> Koch.py.  Michael: I'm not sure what you need for CsoundAC and the
>> whole business with static/dynamic libs, but the SConstruct stuff for
>> that was a bit tough to go through and I've spent a lot of time on
>> this and am going to go focus on my own work for a while.  If you
>> could give the latest CMake stuff a try, that'd be great and let me
>> know if there's any further issues with that.
>>
>> Thanks,
>> steven
>>
>> On Wed, Feb 22, 2012 at 4:13 PM, Steven Yi  wrote:
>>> One note, I found why the symbols weren't showing with CMake on STK,
>>> which was due to an incorrect appending of stkOpcodes.cpp to the list
>>> of sources. I corrected that and am now at the same situation as I
>>> have with Scons-built libstk.dylib, which is it that the library loads
>>> but now opcodes show up. (CMake change pushed to git)
>>>
>>> Thanks,
>>> steven
>>>
>>> On Wed, Feb 22, 2012 at 3:56 PM, Steven Yi  wrote:
>>>> Hi All,
>>>>
>>>> Just an update.  I found that STK opcodes are built but are not
>>>> loading on OSX with CMake or SConstruct.  With SConstruct, the module
>>>> reports a 0 for loading correctly, but no entries in the opcode list.
>>>> WIth CMake, using "nm libstk.dylib | grep Module" shows no
>>>> csoundModule* functions.  Anyone have any thoughts on why those
>>>> functions would get stripped in CMake (or, just in development in
>>>> general)?  I assume it's a C++ flag that hasn't been set in CMake that
>>>> is in SConstruct, but I haven't found out what it is.  Also, why would
>>>> it load the module but have no opcodes when using SConstruct build?
>>>> (Note this is using stk source, not linking to libstk.a)
>>>>
>>>> Also, CsoundAC seems to import fine on CMake and SConstruct builds and
>>>> show the same symbols when i do "import CsoundAC; dir(CsoundAC)".
>>>>
>>>> steven
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

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