We used to have a cmake option to disable swig build - does this option still exist? If so, what should I write in cmake?
Much appreciated, Barak
On 5/30/14, 12:55 PM, Barak Raveh wrote: > We used to have a cmake option to disable swig build - does this option > still exist?
No. But why do you want to do that anyway? If all you want is to build the library for module 'x' but not the Python extension, do 'make IMP.x-lib'.
Ben
How do I make a certain executable within module_bin? (lib is not enough) - the reason I don't want swig is because it takes forever to build and I want to debug faster...
On Fri, May 30, 2014 at 1:02 PM, Ben Webb ben@salilab.org wrote:
> On 5/30/14, 12:55 PM, Barak Raveh wrote: > >> We used to have a cmake option to disable swig build - does this option >> still exist? >> > > No. But why do you want to do that anyway? If all you want is to build the > library for module 'x' but not the Python extension, do 'make IMP.x-lib'. > > Ben > -- > ben@salilab.org http://salilab.org/~ben/ > "It is a capital mistake to theorize before one has data." > - Sir Arthur Conan Doyle >
On 5/30/14, 1:22 PM, Barak Raveh wrote: > How do I make a certain executable within module_bin?
<makecmd> IMP.<module>-<binary_name>
e.g. ninja IMP.multifit-single_prot_fft_fit
BTW, ninja does tab completion, so you could just type "ninja IMP.<module>" then hit tab to see all the targets.
Ben
participants (2)
-
Barak Raveh -
Ben Webb