Hi All,

Felipe and I had been working off and on for a CMake build for Csound.
 I wanted to get the CMake files in sync with the latest in Csound so
have imported and updated the CMake files into the git repository.  To
note:

1. This is not an official build system for Csound.

2. I will be using and updating this to match as closely to the Scons
system as possible.

3. I am using these files so that I can start working on Csound once
again more closely, as it allows me to generate Makefiles, XCode
projects, and Eclipse projects, all of which I enjoy using for
development. (For a list of what it supports, see:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)

4. The system is not yet 100% on par with the SConstruct build for
release builds, though I would say probably 95% of what is in
SConstruct is in the CMake build. (Felipe: I updated to add csbeats
today, which is the only target which was new from when we started
working and latest in git, though I just realized we should remove the
OLPC stuff like it had been done in SConstruct).

5. There is a Custom.cmake.ex file that is to be used like custom.py.
To use it, you will need to copy it to Custom.cmake and modify.

As far as I remember where we had last left it, everything was
building on OSX and Linux, though CsoundAC was having some issues
building on Windows. Last I checked too some of the target seemed to
build statically linking instead of dynamically linking on some
things, but I don't remember which platform that was on.

One difference we put in is that the CMake files will build everything
that it can (meaning what it has found all dependencies for) by
default.  Commandline options are provided to turn things off.

In using CMake I've found that I prefer it's emphasis on out of source
builds, it's general build speed (seems to build more quickly for me
than Scons), and the ability to use my favorite coding environments in
navigating through and working with Csound code. If anyone else is
interested to take a look and give it a try, I'll be happy to assist.

Thanks!
steven

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Also to note, Felipe had done a significant portion of the work on the
Cmake files, and I just wanted to recognize this contribution and to
thank him for it.  Thanks Felipe!

On Sat, Apr 30, 2011 at 10:48 PM, Steven Yi  wrote:
> Hi All,
>
> Felipe and I had been working off and on for a CMake build for Csound.
>  I wanted to get the CMake files in sync with the latest in Csound so
> have imported and updated the CMake files into the git repository.  To
> note:
>
> 1. This is not an official build system for Csound.
>
> 2. I will be using and updating this to match as closely to the Scons
> system as possible.
>
> 3. I am using these files so that I can start working on Csound once
> again more closely, as it allows me to generate Makefiles, XCode
> projects, and Eclipse projects, all of which I enjoy using for
> development. (For a list of what it supports, see:
> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>
> 4. The system is not yet 100% on par with the SConstruct build for
> release builds, though I would say probably 95% of what is in
> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
> today, which is the only target which was new from when we started
> working and latest in git, though I just realized we should remove the
> OLPC stuff like it had been done in SConstruct).
>
> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
> To use it, you will need to copy it to Custom.cmake and modify.
>
> As far as I remember where we had last left it, everything was
> building on OSX and Linux, though CsoundAC was having some issues
> building on Windows. Last I checked too some of the target seemed to
> build statically linking instead of dynamically linking on some
> things, but I don't remember which platform that was on.
>
> One difference we put in is that the CMake files will build everything
> that it can (meaning what it has found all dependencies for) by
> default.  Commandline options are provided to turn things off.
>
> In using CMake I've found that I prefer it's emphasis on out of source
> builds, it's general build speed (seems to build more quickly for me
> than Scons), and the ability to use my favorite coding environments in
> navigating through and working with Csound code. If anyone else is
> interested to take a look and give it a try, I'll be happy to assist.
>
> Thanks!
> steven
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Steven,

I'm trying this out, and build fails with this error:

[ 22%] Building C object CMakeFiles/csound64.dir/Top/threads.c.o
/home/andres/src/csound5/Top/threads.c: In function ‘csoundCreateBarrier’:
/home/andres/src/csound5/Top/threads.c:404: error: ‘barrier_t’
undeclared (first use in this function)
/home/andres/src/csound5/Top/threads.c:404: error: (Each undeclared
identifier is reported only once
/home/andres/src/csound5/Top/threads.c:404: error: for each function
it appears in.)
/home/andres/src/csound5/Top/threads.c:404: error: ‘b’ undeclared
(first use in this function)
/home/andres/src/csound5/Top/threads.c:406: error: expected expression
before ‘)’ token
/home/andres/src/csound5/Top/threads.c: In function ‘csoundDestroyBarrier’:
/home/andres/src/csound5/Top/threads.c:427: error: ‘barrier_t’
undeclared (first use in this function)
/home/andres/src/csound5/Top/threads.c:427: error: ‘b’ undeclared
(first use in this function)
/home/andres/src/csound5/Top/threads.c:427: error: expected expression
before ‘)’ token
/home/andres/src/csound5/Top/threads.c: In function ‘csoundWaitBarrier’:
/home/andres/src/csound5/Top/threads.c:443: error: ‘barrier_t’
undeclared (first use in this function)
/home/andres/src/csound5/Top/threads.c:443: error: ‘b’ undeclared
(first use in this function)
/home/andres/src/csound5/Top/threads.c:443: error: expected expression
before ‘)’ token
make[2]: *** [CMakeFiles/csound64.dir/Top/threads.c.o] Error 1
make[1]: *** [CMakeFiles/csound64.dir/all] Error 2
make: *** [all] Error 2

And this is the result of running CMake:

$ cmake CMakeLists.txt
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- /home/andres/src/csound5
-- BUILD_BIN_DIR set to /home/andres/src/csound5
-- BUILD_LIB_DIR set to /home/andres/src/csound5
-- BUILD_PLUGINS_DIR set to /home/andres/src/csound5
-- Check if the system is big endian
-- Searching 16 bit integer
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of unsigned short
-- Check size of unsigned short - done
-- Using unsigned short
-- Check if the system is big endian - little endian
-- Found FLEX: /usr/bin/flex
-- Found BISON: /usr/bin/bison
-- BUILD_NEW_PARSER is enabled
-- Not building with new parser debugging
-- Using GNU Gettext
-- Building on Linux
-- Compiler flags used for sfont lib: -fno-strict-aliasing
-- 
-- ## REALTIME AUDIO AND MIDI ##
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so
-- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib/libX11.so
-- Found FLTK: fltk_images;fltk_forms;fltk_gl;/usr/lib/libGL.so;fltk
-- APPLE="", so disabling USE_COREAUDIO
-- COREAUDIO_INCLUDE_PATH="COREAUDIO_INCLUDE_PATH-NOTFOUND", so
disabling USE_COREAUDIO
-- COREAUDIO_LIBRARY="COREAUDIO_LIBRARY-NOTFOUND", so disabling USE_COREAUDIO
-- USE_COREAUDIO is disabled
-- USE_ALSA is enabled
-- USE_PULSEAUDIO is enabled
-- USE_PORTAUDIO is enabled
-- USE_PORTMIDI is enabled
-- USE_JACK is enabled
-- USE_FLTK is enabled
-- BUILD_VIRTUAL_KEYBOARD is enabled
-- 
-- Building C++ interface library
-- Found PythonLibs: /usr/lib/libpython2.6.so
-- Could NOT find Lua51  (missing:  LUA_LIBRARIES LUA_INCLUDE_DIR)
-- BUILD_PYTHON_INTERFACE is enabled
-- JNI_FOUND="", so disabling BUILD_JAVA_INTERFACE
-- JAVA_FOUND="", so disabling BUILD_JAVA_INTERFACE
-- BUILD_JAVA_INTERFACE is disabled
-- LUA51_FOUND="FALSE", so disabling BUILD_LUA_INTERFACE
-- BUILD_LUA_INTERFACE is disabled
-- Building csLadspa
-- Found Tclsh: /usr/bin/tclsh
-- Could NOT find TCL  (missing:  TCL_INCLUDE_PATH)
-- Could NOT find TCLTK  (missing:  TCL_INCLUDE_PATH TK_INCLUDE_PATH)
-- Could NOT find TK  (missing:  TK_INCLUDE_PATH)
-- TCL_FOUND="FALSE", so disabling BUILD_TCLCSOUND
-- TK_FOUND="FALSE", so disabling BUILD_TCLCSOUND
-- BUILD_TCLCSOUND is disabled
-- BUILD_CSBEATS is enabled
-- Boost version: 1.40.0
-- Found the following Boost libraries:
-- Could NOT find Lua51  (missing:  LUA_LIBRARIES LUA_INCLUDE_DIR)
-- BUILD_CSOUND_AC is enabled
-- BUILD_CSOUND_AC_PYTHON_INTERFACE is enabled
-- LUA51_FOUND="FALSE", so disabling BUILD_CSOUND_AC_LUA_INTERFACE
-- BUILD_CSOUND_AC_LUA_INTERFACE is disabled
-- Building CsoundAC Python interface
-- Configuring done
-- Generating done
-- Build files have been written to: /home/andres/src/csound5

Am I missing something? (I've never used CMake before)

Cheers,
Andres

On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
> Hi All,
>
> Felipe and I had been working off and on for a CMake build for Csound.
>  I wanted to get the CMake files in sync with the latest in Csound so
> have imported and updated the CMake files into the git repository.  To
> note:
>
> 1. This is not an official build system for Csound.
>
> 2. I will be using and updating this to match as closely to the Scons
> system as possible.
>
> 3. I am using these files so that I can start working on Csound once
> again more closely, as it allows me to generate Makefiles, XCode
> projects, and Eclipse projects, all of which I enjoy using for
> development. (For a list of what it supports, see:
> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>
> 4. The system is not yet 100% on par with the SConstruct build for
> release builds, though I would say probably 95% of what is in
> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
> today, which is the only target which was new from when we started
> working and latest in git, though I just realized we should remove the
> OLPC stuff like it had been done in SConstruct).
>
> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
> To use it, you will need to copy it to Custom.cmake and modify.
>
> As far as I remember where we had last left it, everything was
> building on OSX and Linux, though CsoundAC was having some issues
> building on Windows. Last I checked too some of the target seemed to
> build statically linking instead of dynamically linking on some
> things, but I don't remember which platform that was on.
>
> One difference we put in is that the CMake files will build everything
> that it can (meaning what it has found all dependencies for) by
> default.  Commandline options are provided to turn things off.
>
> In using CMake I've found that I prefer it's emphasis on out of source
> builds, it's general build speed (seems to build more quickly for me
> than Scons), and the ability to use my favorite coding environments in
> navigating through and working with Csound code. If anyone else is
> interested to take a look and give it a try, I'll be happy to assist.
>
> Thanks!
> steven
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists

The error can be fixed with:

-------------------------------- Top/threads.c --------------------------------
index 66da06c..895c0b4 100644
@@ -181,7 +181,6 @@ PUBLIC void csoundSleep(size_t milliseconds)

 #define BARRIER_SERIAL_THREAD (-1)

-/* VL: already defined in CsoundCore.h:70
 #if !defined(HAVE_PTHREAD_BARRIER_INIT)

 typedef struct barrier {
@@ -191,7 +190,6 @@ typedef struct barrier {
 } barrier_t;

 #endif
-*/

 PUBLIC void *csoundCreateThread(uintptr_t (*threadRoutine)(void *),
                                 void *userdata)

This also should fix John's report:
http://csound.1045644.n5.nabble.com/cs-and-threads-td3412324.html

Now having a build inside Eclipse. Nice.

Cheers,
Andres

On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
> Hi All,
>
> Felipe and I had been working off and on for a CMake build for Csound.
>  I wanted to get the CMake files in sync with the latest in Csound so
> have imported and updated the CMake files into the git repository.  To
> note:
>
> 1. This is not an official build system for Csound.
>
> 2. I will be using and updating this to match as closely to the Scons
> system as possible.
>
> 3. I am using these files so that I can start working on Csound once
> again more closely, as it allows me to generate Makefiles, XCode
> projects, and Eclipse projects, all of which I enjoy using for
> development. (For a list of what it supports, see:
> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>
> 4. The system is not yet 100% on par with the SConstruct build for
> release builds, though I would say probably 95% of what is in
> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
> today, which is the only target which was new from when we started
> working and latest in git, though I just realized we should remove the
> OLPC stuff like it had been done in SConstruct).
>
> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
> To use it, you will need to copy it to Custom.cmake and modify.
>
> As far as I remember where we had last left it, everything was
> building on OSX and Linux, though CsoundAC was having some issues
> building on Windows. Last I checked too some of the target seemed to
> build statically linking instead of dynamically linking on some
> things, but I don't remember which platform that was on.
>
> One difference we put in is that the CMake files will build everything
> that it can (meaning what it has found all dependencies for) by
> default.  Commandline options are provided to turn things off.
>
> In using CMake I've found that I prefer it's emphasis on out of source
> builds, it's general build speed (seems to build more quickly for me
> than Scons), and the ability to use my favorite coding environments in
> navigating through and working with Csound code. If anyone else is
> interested to take a look and give it a try, I'll be happy to assist.
>
> Thanks!
> steven
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.source

I remember we had to make a couple of minor changes to the csound
source to get it to play a bit more nicely with out of tree builds.
Steven, did you make those changes too in the git tree?

On Sun, May 1, 2011 at 08:54, Andres Cabrera  wrote:
> The error can be fixed with:
>
> -------------------------------- Top/threads.c --------------------------------
> index 66da06c..895c0b4 100644
> @@ -181,7 +181,6 @@ PUBLIC void csoundSleep(size_t milliseconds)
>
>  #define BARRIER_SERIAL_THREAD (-1)
>
> -/* VL: already defined in CsoundCore.h:70
>  #if !defined(HAVE_PTHREAD_BARRIER_INIT)
>
>  typedef struct barrier {
> @@ -191,7 +190,6 @@ typedef struct barrier {
>  } barrier_t;
>
>  #endif
> -*/
>
>  PUBLIC void *csoundCreateThread(uintptr_t (*threadRoutine)(void *),
>                                 void *userdata)
>
> This also should fix John's report:
> http://csound.1045644.n5.nabble.com/cs-and-threads-td3412324.html
>
> Now having a build inside Eclipse. Nice.
>
> Cheers,
> Andres
>
> On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
>> Hi All,
>>
>> Felipe and I had been working off and on for a CMake build for Csound.
>>  I wanted to get the CMake files in sync with the latest in Csound so
>> have imported and updated the CMake files into the git repository.  To
>> note:
>>
>> 1. This is not an official build system for Csound.
>>
>> 2. I will be using and updating this to match as closely to the Scons
>> system as possible.
>>
>> 3. I am using these files so that I can start working on Csound once
>> again more closely, as it allows me to generate Makefiles, XCode
>> projects, and Eclipse projects, all of which I enjoy using for
>> development. (For a list of what it supports, see:
>> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>>
>> 4. The system is not yet 100% on par with the SConstruct build for
>> release builds, though I would say probably 95% of what is in
>> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
>> today, which is the only target which was new from when we started
>> working and latest in git, though I just realized we should remove the
>> OLPC stuff like it had been done in SConstruct).
>>
>> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
>> To use it, you will need to copy it to Custom.cmake and modify.
>>
>> As far as I remember where we had last left it, everything was
>> building on OSX and Linux, though CsoundAC was having some issues
>> building on Windows. Last I checked too some of the target seemed to
>> build statically linking instead of dynamically linking on some
>> things, but I don't remember which platform that was on.
>>
>> One difference we put in is that the CMake files will build everything
>> that it can (meaning what it has found all dependencies for) by
>> default.  Commandline options are provided to turn things off.
>>
>> In using CMake I've found that I prefer it's emphasis on out of source
>> builds, it's general build speed (seems to build more quickly for me
>> than Scons), and the ability to use my favorite coding environments in
>> navigating through and working with Csound code. If anyone else is
>> interested to take a look and give it a try, I'll be happy to assist.
>>
>> Thanks!
>> steven
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.s

Hi Felipe,

The only change I saw was for CounterPoint.hpp (using stdlib.h instead
of malloc.h) which I committed to git before committing the CMake
files.  Otherwise, everything is currently building for me. If I
missed anything, just let me know!

steven



On Sun, May 1, 2011 at 7:29 PM, Felipe Sateler  wrote:
> I remember we had to make a couple of minor changes to the csound
> source to get it to play a bit more nicely with out of tree builds.
> Steven, did you make those changes too in the git tree?
>
> On Sun, May 1, 2011 at 08:54, Andres Cabrera  wrote:
>> The error can be fixed with:
>>
>> -------------------------------- Top/threads.c --------------------------------
>> index 66da06c..895c0b4 100644
>> @@ -181,7 +181,6 @@ PUBLIC void csoundSleep(size_t milliseconds)
>>
>>  #define BARRIER_SERIAL_THREAD (-1)
>>
>> -/* VL: already defined in CsoundCore.h:70
>>  #if !defined(HAVE_PTHREAD_BARRIER_INIT)
>>
>>  typedef struct barrier {
>> @@ -191,7 +190,6 @@ typedef struct barrier {
>>  } barrier_t;
>>
>>  #endif
>> -*/
>>
>>  PUBLIC void *csoundCreateThread(uintptr_t (*threadRoutine)(void *),
>>                                 void *userdata)
>>
>> This also should fix John's report:
>> http://csound.1045644.n5.nabble.com/cs-and-threads-td3412324.html
>>
>> Now having a build inside Eclipse. Nice.
>>
>> Cheers,
>> Andres
>>
>> On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
>>> Hi All,
>>>
>>> Felipe and I had been working off and on for a CMake build for Csound.
>>>  I wanted to get the CMake files in sync with the latest in Csound so
>>> have imported and updated the CMake files into the git repository.  To
>>> note:
>>>
>>> 1. This is not an official build system for Csound.
>>>
>>> 2. I will be using and updating this to match as closely to the Scons
>>> system as possible.
>>>
>>> 3. I am using these files so that I can start working on Csound once
>>> again more closely, as it allows me to generate Makefiles, XCode
>>> projects, and Eclipse projects, all of which I enjoy using for
>>> development. (For a list of what it supports, see:
>>> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>>>
>>> 4. The system is not yet 100% on par with the SConstruct build for
>>> release builds, though I would say probably 95% of what is in
>>> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
>>> today, which is the only target which was new from when we started
>>> working and latest in git, though I just realized we should remove the
>>> OLPC stuff like it had been done in SConstruct).
>>>
>>> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
>>> To use it, you will need to copy it to Custom.cmake and modify.
>>>
>>> As far as I remember where we had last left it, everything was
>>> building on OSX and Linux, though CsoundAC was having some issues
>>> building on Windows. Last I checked too some of the target seemed to
>>> build statically linking instead of dynamically linking on some
>>> things, but I don't remember which platform that was on.
>>>
>>> One difference we put in is that the CMake files will build everything
>>> that it can (meaning what it has found all dependencies for) by
>>> default.  Commandline options are provided to turn things off.
>>>
>>> In using CMake I've found that I prefer it's emphasis on out of source
>>> builds, it's general build speed (seems to build more quickly for me
>>> than Scons), and the ability to use my favorite coding environments in
>>> navigating through and working with Csound code. If anyone else is
>>> interested to take a look and give it a try, I'll be happy to assist.
>>>
>>> Thanks!
>>> steven
>>>
>>> ------------------------------------------------------------------------------
>>> WhatsUp Gold - Download Free Network Management Software
>>> The most intuitive, comprehensive, and cost-effective network
>>> management toolset available today.  Delivers lowest initial
>>> acquisition cost and overall TCO of any competing solution.
>>> http://p.sf.net/sfu/whatsupgold-sd
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I see the following diff. I don0t know if it is still relevant.


diff -r b7cc15664b02 H/csound_orc.h
--- a/H/csound_orc.h    Wed Jul 28 12:48:55 2010 -0400
+++ b/H/csound_orc.h    Sun May 01 22:43:20 2011 -0300
@@ -11,7 +11,7 @@
   struct TREE   *right;
   struct TREE   *next;
 } TREE;
-#include "../Engine/csound_orcparse.h"
+#include "csound_orcparse.h"
 #include "csoundCore.h"

 enum {
diff -r b7cc15664b02 H/sysdep.h
--- a/H/sysdep.h        Wed Jul 28 12:48:55 2010 -0400
+++ b/H/sysdep.h        Sun May 01 22:43:20 2011 -0300
@@ -62,6 +62,10 @@
 typedef uint_least16_t uint16;
 #endif

+#ifdef __MACH__
+#include 
+#endif
+
 #ifdef USE_DOUBLE
   #define ACOS acos
   #define ASIN asin
diff -r b7cc15664b02 Opcodes/gab/gab.h
--- a/Opcodes/gab/gab.h Wed Jul 28 12:48:55 2010 -0400
+++ b/Opcodes/gab/gab.h Sun May 01 22:43:20 2011 -0300
@@ -22,7 +22,7 @@
 #define GAB_H

 #include "../stdopcod.h"
-#include "H/ugrw1.h"    /* for zread function */
+#include "ugrw1.h"    /* for zread function */
 #include "ugens6.h"     /* for a_k_set function */

 typedef struct {




On Sun, May 1, 2011 at 22:10, Steven Yi  wrote:
> Hi Felipe,
>
> The only change I saw was for CounterPoint.hpp (using stdlib.h instead
> of malloc.h) which I committed to git before committing the CMake
> files.  Otherwise, everything is currently building for me. If I
> missed anything, just let me know!
>
> steven
>
>
>
> On Sun, May 1, 2011 at 7:29 PM, Felipe Sateler  wrote:
>> I remember we had to make a couple of minor changes to the csound
>> source to get it to play a bit more nicely with out of tree builds.
>> Steven, did you make those changes too in the git tree?
>>
>> On Sun, May 1, 2011 at 08:54, Andres Cabrera  wrote:
>>> The error can be fixed with:
>>>
>>> -------------------------------- Top/threads.c --------------------------------
>>> index 66da06c..895c0b4 100644
>>> @@ -181,7 +181,6 @@ PUBLIC void csoundSleep(size_t milliseconds)
>>>
>>>  #define BARRIER_SERIAL_THREAD (-1)
>>>
>>> -/* VL: already defined in CsoundCore.h:70
>>>  #if !defined(HAVE_PTHREAD_BARRIER_INIT)
>>>
>>>  typedef struct barrier {
>>> @@ -191,7 +190,6 @@ typedef struct barrier {
>>>  } barrier_t;
>>>
>>>  #endif
>>> -*/
>>>
>>>  PUBLIC void *csoundCreateThread(uintptr_t (*threadRoutine)(void *),
>>>                                 void *userdata)
>>>
>>> This also should fix John's report:
>>> http://csound.1045644.n5.nabble.com/cs-and-threads-td3412324.html
>>>
>>> Now having a build inside Eclipse. Nice.
>>>
>>> Cheers,
>>> Andres
>>>
>>> On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
>>>> Hi All,
>>>>
>>>> Felipe and I had been working off and on for a CMake build for Csound.
>>>>  I wanted to get the CMake files in sync with the latest in Csound so
>>>> have imported and updated the CMake files into the git repository.  To
>>>> note:
>>>>
>>>> 1. This is not an official build system for Csound.
>>>>
>>>> 2. I will be using and updating this to match as closely to the Scons
>>>> system as possible.
>>>>
>>>> 3. I am using these files so that I can start working on Csound once
>>>> again more closely, as it allows me to generate Makefiles, XCode
>>>> projects, and Eclipse projects, all of which I enjoy using for
>>>> development. (For a list of what it supports, see:
>>>> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>>>>
>>>> 4. The system is not yet 100% on par with the SConstruct build for
>>>> release builds, though I would say probably 95% of what is in
>>>> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
>>>> today, which is the only target which was new from when we started
>>>> working and latest in git, though I just realized we should remove the
>>>> OLPC stuff like it had been done in SConstruct).
>>>>
>>>> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
>>>> To use it, you will need to copy it to Custom.cmake and modify.
>>>>
>>>> As far as I remember where we had last left it, everything was
>>>> building on OSX and Linux, though CsoundAC was having some issues
>>>> building on Windows. Last I checked too some of the target seemed to
>>>> build statically linking instead of dynamically linking on some
>>>> things, but I don't remember which platform that was on.
>>>>
>>>> One difference we put in is that the CMake files will build everything
>>>> that it can (meaning what it has found all dependencies for) by
>>>> default.  Commandline options are provided to turn things off.
>>>>
>>>> In using CMake I've found that I prefer it's emphasis on out of source
>>>> builds, it's general build speed (seems to build more quickly for me
>>>> than Scons), and the ability to use my favorite coding environments in
>>>> navigating through and working with Csound code. If anyone else is
>>>> interested to take a look and give it a try, I'll be happy to assist.
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> ------------------------------------------------------------------------------
>>>> WhatsUp Gold - Download Free Network Management Software
>>>> The most intuitive, comprehensive, and cost-effective network
>>>> management toolset available today.  Delivers lowest initial
>>>> acquisition cost and overall TCO of any competing solution.
>>>> http://p.sf.net/sfu/whatsupgold-sd
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> WhatsUp Gold - Download Free Network Management Software
>>> The most intuitive, comprehensive, and cost-effective network
>>> management toolset available today.  Delivers lowest initial
>>> acquisition cost and overall TCO of any competing solution.
>>> http://p.sf.net/sfu/whatsupgold-sd
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/

Hi Felipe,

The only main change I see is the addition of AvailabilityMacros.h in
sysdep.h, which is done already in git.   The other parts to deal with
header location changes seem to be working alright, so I think we're
fine there.

Thanks!
steven

On Sun, May 1, 2011 at 9:45 PM, Felipe Sateler  wrote:
> I see the following diff. I don0t know if it is still relevant.
>
>
> diff -r b7cc15664b02 H/csound_orc.h
> --- a/H/csound_orc.h    Wed Jul 28 12:48:55 2010 -0400
> +++ b/H/csound_orc.h    Sun May 01 22:43:20 2011 -0300
> @@ -11,7 +11,7 @@
>   struct TREE   *right;
>   struct TREE   *next;
>  } TREE;
> -#include "../Engine/csound_orcparse.h"
> +#include "csound_orcparse.h"
>  #include "csoundCore.h"
>
>  enum {
> diff -r b7cc15664b02 H/sysdep.h
> --- a/H/sysdep.h        Wed Jul 28 12:48:55 2010 -0400
> +++ b/H/sysdep.h        Sun May 01 22:43:20 2011 -0300
> @@ -62,6 +62,10 @@
>  typedef uint_least16_t uint16;
>  #endif
>
> +#ifdef __MACH__
> +#include 
> +#endif
> +
>  #ifdef USE_DOUBLE
>   #define ACOS acos
>   #define ASIN asin
> diff -r b7cc15664b02 Opcodes/gab/gab.h
> --- a/Opcodes/gab/gab.h Wed Jul 28 12:48:55 2010 -0400
> +++ b/Opcodes/gab/gab.h Sun May 01 22:43:20 2011 -0300
> @@ -22,7 +22,7 @@
>  #define GAB_H
>
>  #include "../stdopcod.h"
> -#include "H/ugrw1.h"    /* for zread function */
> +#include "ugrw1.h"    /* for zread function */
>  #include "ugens6.h"     /* for a_k_set function */
>
>  typedef struct {
>
>
>
>
> On Sun, May 1, 2011 at 22:10, Steven Yi  wrote:
>> Hi Felipe,
>>
>> The only change I saw was for CounterPoint.hpp (using stdlib.h instead
>> of malloc.h) which I committed to git before committing the CMake
>> files.  Otherwise, everything is currently building for me. If I
>> missed anything, just let me know!
>>
>> steven
>>
>>
>>
>> On Sun, May 1, 2011 at 7:29 PM, Felipe Sateler  wrote:
>>> I remember we had to make a couple of minor changes to the csound
>>> source to get it to play a bit more nicely with out of tree builds.
>>> Steven, did you make those changes too in the git tree?
>>>
>>> On Sun, May 1, 2011 at 08:54, Andres Cabrera  wrote:
>>>> The error can be fixed with:
>>>>
>>>> -------------------------------- Top/threads.c --------------------------------
>>>> index 66da06c..895c0b4 100644
>>>> @@ -181,7 +181,6 @@ PUBLIC void csoundSleep(size_t milliseconds)
>>>>
>>>>  #define BARRIER_SERIAL_THREAD (-1)
>>>>
>>>> -/* VL: already defined in CsoundCore.h:70
>>>>  #if !defined(HAVE_PTHREAD_BARRIER_INIT)
>>>>
>>>>  typedef struct barrier {
>>>> @@ -191,7 +190,6 @@ typedef struct barrier {
>>>>  } barrier_t;
>>>>
>>>>  #endif
>>>> -*/
>>>>
>>>>  PUBLIC void *csoundCreateThread(uintptr_t (*threadRoutine)(void *),
>>>>                                 void *userdata)
>>>>
>>>> This also should fix John's report:
>>>> http://csound.1045644.n5.nabble.com/cs-and-threads-td3412324.html
>>>>
>>>> Now having a build inside Eclipse. Nice.
>>>>
>>>> Cheers,
>>>> Andres
>>>>
>>>> On Sun, May 1, 2011 at 3:48 AM, Steven Yi  wrote:
>>>>> Hi All,
>>>>>
>>>>> Felipe and I had been working off and on for a CMake build for Csound.
>>>>>  I wanted to get the CMake files in sync with the latest in Csound so
>>>>> have imported and updated the CMake files into the git repository.  To
>>>>> note:
>>>>>
>>>>> 1. This is not an official build system for Csound.
>>>>>
>>>>> 2. I will be using and updating this to match as closely to the Scons
>>>>> system as possible.
>>>>>
>>>>> 3. I am using these files so that I can start working on Csound once
>>>>> again more closely, as it allows me to generate Makefiles, XCode
>>>>> projects, and Eclipse projects, all of which I enjoy using for
>>>>> development. (For a list of what it supports, see:
>>>>> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Generators)
>>>>>
>>>>> 4. The system is not yet 100% on par with the SConstruct build for
>>>>> release builds, though I would say probably 95% of what is in
>>>>> SConstruct is in the CMake build. (Felipe: I updated to add csbeats
>>>>> today, which is the only target which was new from when we started
>>>>> working and latest in git, though I just realized we should remove the
>>>>> OLPC stuff like it had been done in SConstruct).
>>>>>
>>>>> 5. There is a Custom.cmake.ex file that is to be used like custom.py.
>>>>> To use it, you will need to copy it to Custom.cmake and modify.
>>>>>
>>>>> As far as I remember where we had last left it, everything was
>>>>> building on OSX and Linux, though CsoundAC was having some issues
>>>>> building on Windows. Last I checked too some of the target seemed to
>>>>> build statically linking instead of dynamically linking on some
>>>>> things, but I don't remember which platform that was on.
>>>>>
>>>>> One difference we put in is that the CMake files will build everything
>>>>> that it can (meaning what it has found all dependencies for) by
>>>>> default.  Commandline options are provided to turn things off.
>>>>>
>>>>> In using CMake I've found that I prefer it's emphasis on out of source
>>>>> builds, it's general build speed (seems to build more quickly for me
>>>>> than Scons), and the ability to use my favorite coding environments in
>>>>> navigating through and working with Csound code. If anyone else is
>>>>> interested to take a look and give it a try, I'll be happy to assist.
>>>>>
>>>>> Thanks!
>>>>> steven
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> WhatsUp Gold - Download Free Network Management Software
>>>>> The most intuitive, comprehensive, and cost-effective network
>>>>> management toolset available today.  Delivers lowest initial
>>>>> acquisition cost and overall TCO of any competing solution.
>>>>> http://p.sf.net/sfu/whatsupgold-sd
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> WhatsUp Gold - Download Free Network Management Software
>>>> The most intuitive, comprehensive, and cost-effective network
>>>> management toolset available today.  Delivers lowest initial
>>>> acquisition cost and overall TCO of any competing solution.
>>>> http://p.sf.net/sfu/whatsupgold-sd
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> WhatsUp Gold - Download Free Network Management Software
>>> The most intuitive, comprehensive, and cost-effective network
>>> management toolset available today.  Delivers lowest initial
>>> acquisition cost and overall TCO of any competing solution.
>>> http://p.sf.net/sfu/whatsupgold-sd
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net