[cctbxbb] shall iotbx really depends on dxtbx?

[Graeme.Winter at diamond.ac.uk]

Nick

It does the right thing - dxtbx does depend on iotbx - Luc’s problem is that iotbx also depends on dxtbx

Dependency resolution 101: depends on … 

This is in general fine unless you want acyclic graphs, in which case we would want to break one direction of this => move the bits of  iotbx.detectors which depend on dxtbx *into* dxtbx

Would you be OK with this?

Thanks Graeme

> On 26 May 2017, at 15:18, Nicholas Sauter <nksauter at lbl.gov> wrote:
> 
> Do the right thing. Make Dxtbx depend on Iotbx
> 
> Sent from my iPhone
> 
>> On May 26, 2017, at 8:40 AM, Luc Bourhis <luc_j_bourhis at mac.com> wrote:
>> 
>> Hi,
>> 
>> iotbx/libtbx_config:
>> 
>> {
>> "modules_required_for_use": ["cctbx", "fable", "ucif", "smtbx", "dxtbx"],
>> "optional_modules": ["ccp4io", "cbflib"],
>> }
>> 
>> A search for dxtbx in the source code of iotbx does not return anything. Did I miss something? Moreover dxtbx/libtbx_config:
>> 
>> {
>> "modules_required_for_use" : [ "iotbx" ],
>> }
>> 
>> The problem is that dxtbx pulls in HDF5 and that it fails to compiles on Windows 64 with a 64-bit Python, a configuration we need for Olex 2. If the solution was as simple as dropping the dependence of iotbx on dxtbx, that would make my day!
>> 
>> Thoughts?
>> 
>> Best wishes,
>> 
>> Luc Bourhis
>> 
>> _______________________________________________
>> cctbxbb mailing list
>> cctbxbb at phenix-online.org
>> http://phenix-online.org/mailman/listinfo/cctbxbb
> _______________________________________________
> cctbxbb mailing list
> cctbxbb at phenix-online.org
> http://phenix-online.org/mailman/listinfo/cctbxbb


-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom