Swig on Windows (Tracy)
ran into a problem on Windows building packages like
facilities and mootCore
which invoke swig to provide a python interface: they complain about missing
libraries. Jim Chiang found out this happens when the _debug flag is
specified. This causes Windows to look for python debug libraries, not
part of our distribution at present. This doesn't come up in RM builds
since there the _debug flag is not set (nor, more mysteriously, on Glast TS).
The _debug flag is useful when, for example, Tracy wants to be able to
step into G4 code. Possible solutions are
- Modify a header file in our swig installation in such a way that
the debug libraries are no longer required
when _debug is set
- Add python debug libraries to those we distribute
- (Jim) or could handle it with a post-process step, requiring
changes only to SwigPolicy
(Heather) votes for #3.
(Toby) mentioned the related issue that CMT alone does not
enforce proper build order for these swig-using packages. Navid has
put some extra logic in RM to handle this, but MRvcmt, for example
doesn't. facilities and
mootCore are building correctly on Windows,
but this is just luck.