Csound Csound-dev Csound-tekno Search About

[Cs-dev] CMake and old parser build issues

Date2012-06-09 07:23
FromForrest Cahoon
Subject[Cs-dev] CMake and old parser build issues
As I've been working on updating the debian package to the latest
release, I've encountered a couple of issues. First, I had to tweak
frontends/CSoundAC/CMakeLists.txt like so :

--- a/frontends/CsoundAC/CMakeLists.txt
+++ b/frontends/CsoundAC/CMakeLists.txt
@@ -29,7 +29,6 @@
 	allegrowr.cpp
 	Cell.cpp
 	ChordLindenmayer.cpp
-	cmake_install.cmake
 	Composition.cpp
 	Conversions.cpp
 	Counterpoint.cpp



It looks like when someone was kindly sorting the source files, they
got that spurious file in there.

Then I found out I could not build with BUILD_NEW_PARSER turned off
(as it apparently has been on prior debian releases) -- The build dies
with the error:

/home/forrest/debian/csound_build/csound/Engine/otran.c: In function ‘oload’:
/home/forrest/debian/csound_build/csound/Engine/otran.c:1225:10:
error: ‘OPARMS’ has no member named ‘newParser’

This is because there's an #ifdef ENABLE_NEW_PARSER around that
element where it's defined in H/csoundCore.h but it's just assumed to
be there in otran.c .


Forrest

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-de

Date2012-06-09 10:29
Fromjpff@cs.bath.ac.uk
SubjectRe: [Cs-dev] CMake and old parser build issues
Csound5 is built with scons; the cmake is not supported centrally

Building without the new parser is not correct from 5.17
All BUILD_NEW_PARSER references should have been removed

==John

> As I've been working on updating the debian package to the latest
> release, I've encountered a couple of issues. First, I had to tweak
> frontends/CSoundAC/CMakeLists.txt like so :
>
> --- a/frontends/CsoundAC/CMakeLists.txt
> +++ b/frontends/CsoundAC/CMakeLists.txt
> @@ -29,7 +29,6 @@
>  	allegrowr.cpp
>  	Cell.cpp
>  	ChordLindenmayer.cpp
> -	cmake_install.cmake
>  	Composition.cpp
>  	Conversions.cpp
>  	Counterpoint.cpp
>
>
>
> It looks like when someone was kindly sorting the source files, they
> got that spurious file in there.
>
> Then I found out I could not build with BUILD_NEW_PARSER turned off
> (as it apparently has been on prior debian releases) -- The build dies
> with the error:
>
> /home/forrest/debian/csound_build/csound/Engine/otran.c: In function
> ‘oload’:
> /home/forrest/debian/csound_build/csound/Engine/otran.c:1225:10:
> error: ‘OPARMS’ has no member named ‘newParser’
>
> This is because there's an #ifdef ENABLE_NEW_PARSER around that
> element where it's defined in H/csoundCore.h but it's just assumed to
> be there in otran.c .
>
>
> Forrest
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-06-09 19:28
FromForrest Cahoon
SubjectRe: [Cs-dev] CMake and old parser build issues
On Sat, Jun 9, 2012 at 4:29 AM,   wrote:
> Csound5 is built with scons; the cmake is not supported centrally
>
> Building without the new parser is not correct from 5.17
> All BUILD_NEW_PARSER references should have been removed
>
> ==John

It's also still possible to specify buildNewParser=0 when building
with scons, which results in the same error.

If the old parser is really gone for good, shouldn't ENABLE_NEW_PARSER
be defined in a global header somewhere (if there is such a thing),
instead of the build system having to specify -DENABLE_NEW_PARSER for
every compile? Of course, even better would be excising all the old
parser code altogether, but I guess that's probably a lot of work.

Forrest

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2012-06-09 22:12
Fromjpff@cs.bath.ac.uk
SubjectRe: [Cs-dev] CMake and old parser build issues
In csound6 I have indeed removed all the old parser.  I have a version of
cs5 with new parser enabled for ever; not committed yet

==John ff
> On Sat, Jun 9, 2012 at 4:29 AM,   wrote:
>> Csound5 is built with scons; the cmake is not supported centrally
>>
>> Building without the new parser is not correct from 5.17
>> All BUILD_NEW_PARSER references should have been removed
>>
>> ==John
>
> It's also still possible to specify buildNewParser=0 when building
> with scons, which results in the same error.
>
> If the old parser is really gone for good, shouldn't ENABLE_NEW_PARSER
> be defined in a global header somewhere (if there is such a thing),
> instead of the build system having to specify -DENABLE_NEW_PARSER for
> every compile? Of course, even better would be excising all the old
> parser code altogether, but I guess that's probably a lot of work.
>
> Forrest
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net