As an aside,

I have noticed that even if I run the command scons -c the installation directories are not cleaned. I have recently discovered that one set of code that I was running was functioning via links that were generated by a previous version. This had the affect of artificially giving me a functioning code. I am sure that the nightly builds are made in a clean directory, however other users might run into a similar problem as I was previously was.

With most build tools (scons, make etc), clean just cleans up the build directories rather than uninstalls the package. The normal pattern (when installing) is something like

scons

# put it somewhere easy to access, perhaps, using sudo to put it somewhere not normally writeable

(sudo) scons install

# clean up the intermediate files to save disk space

scons -c all

We have tried to be careful so that an installed IMP setup will not get mixed in with a local build when running tests and using imppy.sh (assuming that the build doesn't return an error). How did you get the problem? And with what versions if IMP? Thanks.

Daniel

Bryn

--
R. Bryn Fenwick
Sent with Sparrow
On Friday, 21 January 2011 at 17:16, R. Bryn Fenwick wrote:

Can you give me a hint on how to disable the cgal module, I am not sure I understand how to do this.

Bryn

--
R. Bryn Fenwick
Sent with Sparrow
On Friday, 21 January 2011 at 17:13, Ben Webb wrote:
don't use CGAL, you could simply disable the IMP.cgal module.

_______________________________________________
IMP-users mailing list
IMP-users@salilab.org
https://salilab.org/mailman/listinfo/imp-users