<div class="gmail_quote"><div>Hi Martin,</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">I totally agree - if cherry picking is time consuming then it's not</div>
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
worth it. I just wondered if there was a quick way to strip out some<br>
of the top level namespaces completely from the build dependencies.<br></blockquote><div><br></div><div>Yes. The libtbx/configure.py command lists all the top-level names of the modules used. You can simply rm -rf the rest.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">One other quick question that's quite important to my project: is<br>
there a way to build a debug version cctbx? At the moment I'm having a<br>
lot of problems due to mixing of release/debug CRTs (when I build my<br>
code in debug).<br></blockquote><div><br></div><div>We have libtbx/configure.py --build=debug option. I'm occasionally using this under Linux and Mac OS X. I don't remember if I ever tried this under Windows.</div>
<div><br></div><div>Ralf</div><div><br></div></div>