[Clam-devel] impossible to compile CLAM in debug

[Pau Arumi]

En/na Xavier Amatriain ha escrit:
> Hi,
> 
> You mean release=0, right? In any case, I have been debugging
> these past few weeks and find it extremely difficult to know what
> is going on when I change compile options. Have you tried recompiling
> all? Do you at least get debug symbols?

i've discovered it was my fault: i wasn't doing "scons configure"
that's probably the same problems you are experimenting.
now, only "scons configure" translate the scons options to
compile parameters.
this happen in this file: clam_dependent_libs_checks.py i didn't
find it because i was looking at SConscripts

david and me have just talked about it: the obvious solution
consist in automatically force the configure each time an option
is redefined. i think it's quick to do

pau



> Pau Arumi wrote:
>>
>> i've found that changing the scons option release=1 in CLAM
>> doesn't recompile anything. which is somehow disturbing.
>> diving further i found that env['release'] is not used in the
>> SConscripts.  so now all CLAM_DEBUG_ASSERTS are ignored!
>>
>> i can't remember any change that removed this.
>> david, xavi: ideas?
>>
>> pau
>>
>>
>> _______________________________________________
>> Clam-devel mailing list
>> Clam-devel at llistes.projectes.lafarga.org
>> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
> 
> 
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel