<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Aaron,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">The key trick was to make iotbx only depend on dxtbx if dxtbx is explicitly configured. I used a keyword in libtbx_configure added by Luc a bit ago: optional_modules_only_if_explicit_request. I committed that change just now.</div></blockquote><div><br class=""></div><div>That is exactly the use case I envisioned. What I planned to use it for never made it to the official repo but it’s always nice to see it being useful to somebody else!</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="">Outstanding questions:</div><div class=""><ol class=""><li class="">Is there interest in making this a builder? It would be straightforward to add a builder named cctbx_minimal which would just do the above steps</li></ol></div></div></blockquote>I would like to have that. For reasons different from yours, I guess. But still, first, this would make our life easier at Bruker. Then there is also the teaching facet of the cctbx: I am regularly involved in the computing schools organised by the IUCr and the ECM where I give tutorials on the cctbx, and having a forced dependency on dxtbx with the added chore of an implicit dependency on HDF5 is annoying.</div><div><br class=""></div><div>Best wishes,</div><div><br class=""></div><div>Luc</div><div><br class=""><br class=""></div><div><br class=""></div><br class=""></div></body></html>