I have already asked a related question....

If I build 
with options
buildCsoundVST=0 generateTags=0 useJack=1 usePortMIDI=1 generateZIP=0
useALSA=1 useOSC=1 buildCsoundAC=1 buildInterfaces=1 buildTclcsound=1
noDebug=1  buildJavaWrapper=1 pythonVersion=2.5 buildPythonOpcodes=1
buildRelease=1 buildPDClass=1 useUDP=1 dynamicCsoundLibrary=1
buildCsound5GUI=1 buildStkOpcodes=1 buildWinsound=1 buildVirtual=1
buildCSEditor=1 useGettext=1 buildLoris=1 useDouble=1

all is OK

but with

buildCsoundVST=0 generateTags=0 useJack=1 usePortMIDI=1 generateZIP=0
useALSA=1 useOSC=1 buildCsoundAC=1 buildInterfaces=1 buildTclcsound=1
noDebug=1  buildJavaWrapper=1 pythonVersion=2.5 buildPythonOpcodes=1
buildRelease=1 buildPDClass=1 useUDP=1 dynamicCsoundLibrary=1
buildCsound5GUI=1 buildStkOpcodes=1 buildWinsound=1 buildVirtual=1
buildCSEditor=1 useGettext=1 buildLoris=1

I get errors like
Python Version: 2.5
CONFIGURATION DECISION: Building Java wrappers for Csound interfaces library.
:1: Error: Macro 'HAVE_SOCKETS' redefined,
:1: Error: previous definition of 'HAVE_SOCKETS'.
LangSubDir: java

Has anyone any ideas? Or know what changed?  It worked the other
day...

==John ffitch

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I don't have an answer to your question, but I have one of my own.

I have been assuming that buildRelease=1 also sets noDebug=1 because the
SConstruct list of options says 'buildRelease', 'Set to 1 to build for
release (implies noDebug).'  (gcc3opt and gcc4opt say something similar). 
But I see that you are specifying both and now that I look I see no
connection between these two options in SConstruct.

Do I have to specify noDebug=1 in addition to buildRelease=1 in order to
avoid debugging info in the binaries?

Thanks.

Anthony

On Fri, December 19, 2008 4:32 am, jpff wrote:
> I have already asked a related question....
>
> If I build
> with options
> buildCsoundVST=0 generateTags=0 useJack=1 usePortMIDI=1 generateZIP=0
> useALSA=1 useOSC=1 buildCsoundAC=1 buildInterfaces=1 buildTclcsound=1
> noDebug=1  buildJavaWrapper=1 pythonVersion=2.5 buildPythonOpcodes=1
> buildRelease=1 buildPDClass=1 useUDP=1 dynamicCsoundLibrary=1
> buildCsound5GUI=1 buildStkOpcodes=1 buildWinsound=1 buildVirtual=1
> buildCSEditor=1 useGettext=1 buildLoris=1 useDouble=1




------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Not at all sure.  I do not understand the buildRelease option and am
just following a script.
I think the important lines are

if commonEnvironment['buildRelease'] == '0':
    commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])

but it does seem to me that the comment that 'buildRelease' implies
noDebug is false

>>>>> "Anthony" == Anthony Kozar  writes:

 Anthony> I don't have an answer to your question, but I have one of my own.
 Anthony> I have been assuming that buildRelease=1 also sets noDebug=1 because the
 Anthony> SConstruct list of options says 'buildRelease', 'Set to 1 to build for
 Anthony> release (implies noDebug).'  (gcc3opt and gcc4opt say something similar). 
 Anthony> But I see that you are specifying both and now that I look I see no
 Anthony> connection between these two options in SConstruct.

 Anthony> Do I have to specify noDebug=1 in addition to buildRelease=1 in order to
 Anthony> avoid debugging info in the binaries?

 Anthony> Thanks.

 Anthony> Anthony


==John ffitch

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net