Comment on BuildInstructions in casacore

1 view
Skip to first unread message

codesite...@google.com

unread,
Apr 7, 2008, 9:23:06 AM4/7/08
to casacor...@googlegroups.com
Comment by marjolein.verkouter:

HV: As there seems to be not a "clean" target, I think I have the
commands that, when executed, allow you to do a complete fresh build.

Allegedly, there is an undocumented way to do it but all I got so far
was that indeed it was undocumented, propably even "sekrit" (which
didn't help me much).

Why this comment? Well, when changing the option(s) on the commandline
of batchbuild.py - they will not be 'honoured' if you have run
batchbuild.py/scons before: the system stores info in files only once
and doesn't detect that you (want to) re-run with different options.
That in itself is not a problem, as long as you can force the system
to ... clean and/or do a full rebuild, neither of which seems to be available.

You have to either edit the configfiles by hand (...) or remove them
such that the next invocation of batchbuild.py/scons will write new configurationfiles.

The commands that seem to trigger a full rebuild are - at least in my
experience - are:

#!/bin/sh
find . -name \*.o -o -name \*.a -o -name \*.so | xargs rm -f
find . -name options.cfg | xargs rm -f
find . -name .sconf_temp | xargs rm -rf
find . -name config.log | xargs rm -f
find . -name .sconsign.dblite | xargs rm -f


For more information:
http://code.google.com/p/casacore/wiki/BuildInstructions

codesite...@google.com

unread,
Apr 7, 2008, 9:27:07 AM4/7/08
to casacor...@googlegroups.com
Comment by harro.en.yvonne:

HV: As there seems to be not a "clean" target, I think I have the
commands that, when executed, allow you to do a complete fresh build.

Allegedly, there is an undocumented way to do it but all I got so far
was that indeed it was undocumented, propably even "sekrit" (which
didn't help me much).

Why this comment? Well, when changing the option(s) on the commandline
of batchbuild.py - they will not be 'honoured' if you have run
batchbuild.py/scons before: the system stores info in files only once
and doesn't detect that you (want to) re-run with different options.
That in itself is not a problem, as long as you can force the system
to ... clean and/or do a full rebuild, neither of which seems to be available.

You have to either edit the configfiles by hand (...) or remove them
such that the next invocation of batchbuild.py/scons will write new configurationfiles.

The commands that seem to trigger a full rebuild are - at least in my
experience - are:
{{{
#!/bin/sh

find . -name \.o -o -name \.a -o -name \.so | xargs rm -f

Reply all
Reply to author
Forward
0 new messages