[cctbxbb] Building cctbx bundles without phenix.* dispatcher scripts

[Richard Gildea]

Hi Nigel,

I think what Graeme is after is a mechanism such that we don't end up with
dispatchers such as phenix.merging_statistics (replaced, e.g. with
iotbx.merging_statistics) in the DIALS bundles, as to an uninformed
observer, it looks as though we are distributing part of phenix.

Cheers,

Richard


On 2 July 2015 at 17:05, Nigel Moriarty <nwmoriarty at lbl.gov> wrote:

> Greame
>
> You can name it anything using the mechanism below. Put these lines at the
> top of the file that is being "dispatched" (ie any file in a command_line
> directory) and it will be named accordingly. I suggest not_phenix.dials.
> This is from the top of the eLBOW file called builder.py but the dispatcher
> is called phenix.elbow. The other two lines are needed if you want to build
> a GUI. You still have other things to do to get a GUI, however.
>
> # LIBTBX_SET_DISPATCHER_NAME phenix.elbow
> # LIBTBX_PRE_DISPATCHER_INCLUDE_SH PHENIX_GUI_ENVIRONMENT=1
> # LIBTBX_PRE_DISPATCHER_INCLUDE_SH export PHENIX_GUI_ENVIRONMENT
>
> Cheers
>
> Nigel
>
> ---
> Nigel W. Moriarty
> Building 64R0246B, Physical Biosciences Division
> Lawrence Berkeley National Laboratory
> Berkeley, CA 94720-8235
> Phone : 510-486-5709     Email : NWMoriarty at LBL.gov
> Fax   : 510-486-5909       Web  : CCI.LBL.gov
>
> On Thu, Jul 2, 2015 at 6:42 AM, <Graeme.Winter at diamond.ac.uk> wrote:
>
>> Hi Folks
>>
>> Following on from various conversations going on here about programs in
>> the default dials bundle which necessarily includes cctbx & lots of useful
>> utilities in there, the question was asked why it includes bits of Phenix.
>> In real life it does not include bits of phenix - they are bits of e.g.
>> mmtbx which have dispatcher scripts which ask to be called phenix.xyz for
>> example, as they are *also* used in phenix.
>>
>> Is there a way we can set the dispatcher prefix at the time of running
>> libtbx.configure? That way you could have phenix.xyz or cctbx.xyz in other
>> situations… then in the dials bundles we could make it clear that there are
>> no bits of Phenix in there.
>>
>> Many thanks in advance, Graeme
>>
>>
>>
>>
>>
>> --
>> 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
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phenix-online.org/pipermail/cctbxbb/attachments/20150702/a28faee7/attachment.htm>