Hi All,

I've gone through and redid how the compiler optimization flags are set:

1. I have added a cmake folder for utility scripts and added a
CompilerOptimizations.cmake file.  This file is included into the main
CmakeFiles.txt.

2. The CompilerOptimzations.cmake use check_c_compiler_flag and
check_cxx_compiler_flag for each flag. If found, it will add it to the
global CMAKE_C_FLAGS and CMAKE_CXX_FLAGS.

3. In the main CMakeFiles.txt, I added an option for
"USE_COMPILER_OPTIMIZATIONS".  This will allow packagers like Felipe
to turn the checks and flags off altogether.

4. This should fix Bug #28 (building on Raspberry Pi)

5. I saw some flags set in the main project I was unsure of.
Particularly, there was one line setting "-g", which seemed wrong. The
default setting for the Debug c flags is:

cmake ../csound6 -DCMAKE_BUILD_TYPE=Release

CMAKE_CXX_FLAGS_DEBUG:STRING=-g

Users should use "cmake ../csound6 -DCMAKE_BUILD_TYPE=Debug" if they
want to have debug symbols.

6. I have commented out "set(CMAKE_BUILD_TYPE "Debug")" in
Custom.cmake.ex. I think we should leave it there for users to easily
enable, but having it in there can cause problems (like it did for
me!).

7. I tested on Debian and got a successful compile. One thing I
thought interesting was -fomit-frame-pointer did not show up as a
success in the testing and was not used.  This seems odd, but not sure
what's going on there.

Otherwise, I'm going to rebuild the last OSX release (6.00.1) and
re-release it shortly. I don't think the iOS release was affected by
any thing and was properly built in the first place.

Things seem to work on OSX and Debian.  I'm going to fire up my
Windows VM momentarily and give it a try there, but that will take a
while as the VM is quite slow for me.

Please report and issues and feel free to improve/modify whatever is in git!

Thanks!
steven

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I've updated and opened cmake-gui but I can't find USE_COMPILER_OPTIMIZATIONS.

Shouldn't it be there?
On 11 Aug 2013, at 12:02, Steven Yi wrote:

> Hi All,
> 
> I've gone through and redid how the compiler optimization flags are set:
> 
> 1. I have added a cmake folder for utility scripts and added a
> CompilerOptimizations.cmake file.  This file is included into the main
> CmakeFiles.txt.
> 
> 2. The CompilerOptimzations.cmake use check_c_compiler_flag and
> check_cxx_compiler_flag for each flag. If found, it will add it to the
> global CMAKE_C_FLAGS and CMAKE_CXX_FLAGS.
> 
> 3. In the main CMakeFiles.txt, I added an option for
> "USE_COMPILER_OPTIMIZATIONS".  This will allow packagers like Felipe
> to turn the checks and flags off altogether.
> 
> 4. This should fix Bug #28 (building on Raspberry Pi)
> 
> 5. I saw some flags set in the main project I was unsure of.
> Particularly, there was one line setting "-g", which seemed wrong. The
> default setting for the Debug c flags is:
> 
> cmake ../csound6 -DCMAKE_BUILD_TYPE=Release
> 
> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
> 
> Users should use "cmake ../csound6 -DCMAKE_BUILD_TYPE=Debug" if they
> want to have debug symbols.
> 
> 6. I have commented out "set(CMAKE_BUILD_TYPE "Debug")" in
> Custom.cmake.ex. I think we should leave it there for users to easily
> enable, but having it in there can cause problems (like it did for
> me!).
> 
> 7. I tested on Debian and got a successful compile. One thing I
> thought interesting was -fomit-frame-pointer did not show up as a
> success in the testing and was not used.  This seems odd, but not sure
> what's going on there.
> 
> Otherwise, I'm going to rebuild the last OSX release (6.00.1) and
> re-release it shortly. I don't think the iOS release was affected by
> any thing and was properly built in the first place.
> 
> Things seem to work on OSX and Debian.  I'm going to fire up my
> Windows VM momentarily and give it a try there, but that will take a
> while as the VM is quite slow for me.
> 
> Please report and issues and feel free to improve/modify whatever is in git!
> 
> Thanks!
> steven
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It should be, but I rarely use the GUI so I'm not sure if something is
cached or not. I just checked here and I'm seeing it in the GUI.
Maybe you need to run the configuration once to update what options
are shown?

On Sun, Aug 11, 2013 at 1:56 PM, Victor Lazzarini
 wrote:
> I've updated and opened cmake-gui but I can't find USE_COMPILER_OPTIMIZATIONS.
>
> Shouldn't it be there?
> On 11 Aug 2013, at 12:02, Steven Yi wrote:
>
>> Hi All,
>>
>> I've gone through and redid how the compiler optimization flags are set:
>>
>> 1. I have added a cmake folder for utility scripts and added a
>> CompilerOptimizations.cmake file.  This file is included into the main
>> CmakeFiles.txt.
>>
>> 2. The CompilerOptimzations.cmake use check_c_compiler_flag and
>> check_cxx_compiler_flag for each flag. If found, it will add it to the
>> global CMAKE_C_FLAGS and CMAKE_CXX_FLAGS.
>>
>> 3. In the main CMakeFiles.txt, I added an option for
>> "USE_COMPILER_OPTIMIZATIONS".  This will allow packagers like Felipe
>> to turn the checks and flags off altogether.
>>
>> 4. This should fix Bug #28 (building on Raspberry Pi)
>>
>> 5. I saw some flags set in the main project I was unsure of.
>> Particularly, there was one line setting "-g", which seemed wrong. The
>> default setting for the Debug c flags is:
>>
>> cmake ../csound6 -DCMAKE_BUILD_TYPE=Release
>>
>> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
>>
>> Users should use "cmake ../csound6 -DCMAKE_BUILD_TYPE=Debug" if they
>> want to have debug symbols.
>>
>> 6. I have commented out "set(CMAKE_BUILD_TYPE "Debug")" in
>> Custom.cmake.ex. I think we should leave it there for users to easily
>> enable, but having it in there can cause problems (like it did for
>> me!).
>>
>> 7. I tested on Debian and got a successful compile. One thing I
>> thought interesting was -fomit-frame-pointer did not show up as a
>> success in the testing and was not used.  This seems odd, but not sure
>> what's going on there.
>>
>> Otherwise, I'm going to rebuild the last OSX release (6.00.1) and
>> re-release it shortly. I don't think the iOS release was affected by
>> any thing and was properly built in the first place.
>>
>> Things seem to work on OSX and Debian.  I'm going to fire up my
>> Windows VM momentarily and give it a try there, but that will take a
>> while as the VM is quite slow for me.
>>
>> Please report and issues and feel free to improve/modify whatever is in git!
>>
>> Thanks!
>> steven
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Forget it, I found it.
On 11 Aug 2013, at 12:56, Victor Lazzarini wrote:

> I've updated and opened cmake-gui but I can't find USE_COMPILER_OPTIMIZATIONS.
> 
> Shouldn't it be there?
> On 11 Aug 2013, at 12:02, Steven Yi wrote:
> 
>> Hi All,
>> 
>> I've gone through and redid how the compiler optimization flags are set:
>> 
>> 1. I have added a cmake folder for utility scripts and added a
>> CompilerOptimizations.cmake file.  This file is included into the main
>> CmakeFiles.txt.
>> 
>> 2. The CompilerOptimzations.cmake use check_c_compiler_flag and
>> check_cxx_compiler_flag for each flag. If found, it will add it to the
>> global CMAKE_C_FLAGS and CMAKE_CXX_FLAGS.
>> 
>> 3. In the main CMakeFiles.txt, I added an option for
>> "USE_COMPILER_OPTIMIZATIONS".  This will allow packagers like Felipe
>> to turn the checks and flags off altogether.
>> 
>> 4. This should fix Bug #28 (building on Raspberry Pi)
>> 
>> 5. I saw some flags set in the main project I was unsure of.
>> Particularly, there was one line setting "-g", which seemed wrong. The
>> default setting for the Debug c flags is:
>> 
>> cmake ../csound6 -DCMAKE_BUILD_TYPE=Release
>> 
>> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
>> 
>> Users should use "cmake ../csound6 -DCMAKE_BUILD_TYPE=Debug" if they
>> want to have debug symbols.
>> 
>> 6. I have commented out "set(CMAKE_BUILD_TYPE "Debug")" in
>> Custom.cmake.ex. I think we should leave it there for users to easily
>> enable, but having it in there can cause problems (like it did for
>> me!).
>> 
>> 7. I tested on Debian and got a successful compile. One thing I
>> thought interesting was -fomit-frame-pointer did not show up as a
>> success in the testing and was not used.  This seems odd, but not sure
>> what's going on there.
>> 
>> Otherwise, I'm going to rebuild the last OSX release (6.00.1) and
>> re-release it shortly. I don't think the iOS release was affected by
>> any thing and was properly built in the first place.
>> 
>> Things seem to work on OSX and Debian.  I'm going to fire up my
>> Windows VM momentarily and give it a try there, but that will take a
>> while as the VM is quite slow for me.
>> 
>> Please report and issues and feel free to improve/modify whatever is in git!
>> 
>> Thanks!
>> steven
>> 
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead. 
>> Download for free and get started troubleshooting in minutes. 
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Update: I just tried a compile on windows and the compile failed. I
got some messages about SSE and then an error regarding DWORD (pasted
below).  Michael: any advice?

[ 14%] Building C object CMakeFiles/csound64.dir/Opcodes/sfont.c.obj
/C/MinGW/bin/gcc.exe  -Dcsound64_EXPORTS -DUSE_DOUBLE -D_CSOUND_RELEASE_ -DUSE_L
RINT -DWIN32 -ftree-vectorize -ffast-math -fvisibility=hidden -mfpmath=sse -fomi
t-frame-pointer -W -Wall -O3 -mtune=core2 -ftree-vectorize -ffast-math -O3 -DNDE
BUG @CMakeFiles/csound64.dir/includes_C.rsp   -Wno-format   -D__BUILDING_LIBCSOU
ND -DPARCS -DGNU_GETTEXT -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TYPES_H -o C
MakeFiles/csound64.dir/Opcodes/sfont.c.obj   -c /c/Users/Steven/work2/csound6/Op
codes/sfont.c
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1:0: warning: SSE instruction set
disabled, using 387 arithmetics [enabled by default]
In file included from c:/Users/Steven/work2/csound6/Opcodes/sfont.h:24:0,
                 from c:/Users/Steven/work2/csound6/Opcodes/sfont.c:41:
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:119:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:120:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:121:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:209:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:210:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:211:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:212:9: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sftype.h:213:9: error: unknown type name '
DWORD'
In file included from c:/Users/Steven/work2/csound6/Opcodes/sfont.h:25:0,
                 from c:/Users/Steven/work2/csound6/Opcodes/sfont.c:41:
c:/Users/Steven/work2/csound6/Opcodes/sf.h:99:3: error: unknown type name 'DWORD
'
In file included from c:/Users/Steven/work2/csound6/Opcodes/sfont.c:41:0:
c:/Users/Steven/work2/csound6/Opcodes/sfont.h:55:9: error: unknown type name 'DW
ORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.h:69:9: error: unknown type name 'DW
ORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.h:83:9: error: unknown type name 'DW
ORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.h:97:9: error: unknown type name 'DW
ORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPreset':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:275:29: error: 'DWORD' undeclared
(first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:275:29: note: each undeclared iden
tifier is reported only once for each function it appears in
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlay_set':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:307:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:307:20: error: 'DWORD' undeclared
(first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:337:19: error: expected ';' before
 'start'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:364:40: error: 'start' undeclared
(first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlay':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:468:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:460:27: warning: unused parameter
'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlay3':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:559:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:551:28: warning: unused parameter
'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlayMono_set':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:643:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:643:20: error: 'DWORD' undeclared
(first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:674:19: error: expected ';' before
 'start'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:695:40: error: 'start' undeclared
(first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlayMono':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:743:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:735:31: warning: unused parameter
'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfPlayMono3':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:831:5: error: unknown type name 'D
WORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:823:32: warning: unused parameter
'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlay_set':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:934:11: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlay':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1006:5: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:998:32: warning: unused parameter
'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlay3':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1098:5: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1090:33: warning: unused parameter
 'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlayMono_set'
:
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1206:11: error: unknown type name
'DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlayMono':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1272:5: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1264:36: warning: unused parameter
 'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'SfInstrPlayMono3':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1361:5: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:1353:37: warning: unused parameter
 'csound' [-Wunused-parameter]
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: At top level:
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2013:1: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'dword':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2016:7: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c: In function 'fill_SfPointers':
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2029:5: error: unknown type name '
DWORD'
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2065:20: error: 'DWORD' undeclared
 (first use in this function)
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2065:20: error: expected expressio
n before ')' token
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2080:22: error: expected expressio
n before ')' token
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2084:27: error: expected expressio
n before ')' token
c:/Users/Steven/work2/csound6/Opcodes/sfont.c:2101:29: error: expected
expressio...

On Sun, Aug 11, 2013 at 2:05 PM, Steven Yi  wrote:
> It should be, but I rarely use the GUI so I'm not sure if something is
> cached or not. I just checked here and I'm seeing it in the GUI.
> Maybe you need to run the configuration once to update what options
> are shown?
>
> On Sun, Aug 11, 2013 at 1:56 PM, Victor Lazzarini
>  wrote:
>> I've updated and opened cmake-gui but I can't find USE_COMPILER_OPTIMIZATIONS.
>>
>> Shouldn't it be there?
>> On 11 Aug 2013, at 12:02, Steven Yi wrote:
>>
>>> Hi All,
>>>
>>> I've gone through and redid how the compiler optimization flags are set:
>>>
>>> 1. I have added a cmake folder for utility scripts and added a
>>> CompilerOptimizations.cmake file.  This file is included into the main
>>> CmakeFiles.txt.
>>>
>>> 2. The CompilerOptimzations.cmake use check_c_compiler_flag and
>>> check_cxx_compiler_flag for each flag. If found, it will add it to the
>>> global CMAKE_C_FLAGS and CMAKE_CXX_FLAGS.
>>>
>>> 3. In the main CMakeFiles.txt, I added an option for
>>> "USE_COMPILER_OPTIMIZATIONS".  This will allow packagers like Felipe
>>> to turn the checks and flags off altogether.
>>>
>>> 4. This should fix Bug #28 (building on Raspberry Pi)
>>>
>>> 5. I saw some flags set in the main project I was unsure of.
>>> Particularly, there was one line setting "-g", which seemed wrong. The
>>> default setting for the Debug c flags is:
>>>
>>> cmake ../csound6 -DCMAKE_BUILD_TYPE=Release
>>>
>>> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
>>>
>>> Users should use "cmake ../csound6 -DCMAKE_BUILD_TYPE=Debug" if they
>>> want to have debug symbols.
>>>
>>> 6. I have commented out "set(CMAKE_BUILD_TYPE "Debug")" in
>>> Custom.cmake.ex. I think we should leave it there for users to easily
>>> enable, but having it in there can cause problems (like it did for
>>> me!).
>>>
>>> 7. I tested on Debian and got a successful compile. One thing I
>>> thought interesting was -fomit-frame-pointer did not show up as a
>>> success in the testing and was not used.  This seems odd, but not sure
>>> what's going on there.
>>>
>>> Otherwise, I'm going to rebuild the last OSX release (6.00.1) and
>>> re-release it shortly. I don't think the iOS release was affected by
>>> any thing and was properly built in the first place.
>>>
>>> Things seem to work on OSX and Debian.  I'm going to fire up my
>>> Windows VM momentarily and give it a try there, but that will take a
>>> while as the VM is quite slow for me.
>>>
>>> Please report and issues and feel free to improve/modify whatever is in git!
>>>
>>> Thanks!
>>> steven
>>>
>>> ------------------------------------------------------------------------------
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>>> It's a free troubleshooting tool designed for production.
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net