[cctbxbb] differing build and install directories?

William Scott wgscott at chemistry.ucsc.edu
Tue Sep 27 21:54:35 PDT 2005


  Dear Ralf:

Sorry to keep pestering you.  I'm now trying to build debian  
packages, which means the build directory differs from the install  
directory.

Because of this, a lot of the shell scripts, python scripts, and  
compiled binaries in cctbx have a path like /sw/src/fink.build/ 
ccp4-5.99.3-1/ccp4-5.99.3 hard-coded into them, and I'd like the  
final one to look like /sw/share/xtal/ccp4-5.99.3 (for example).   
Similarly for Debian linux.  Is there a simple way to build in one  
directory but use the final install-path for configuring?

I've tried changing $install_root in the file  
cctbx_install_script.csh, but that didn't work.

Similarly, I noticed the install_paths hard-coded into the dynamic  
libraries for cctbx are relative, rather than absolute like the  
others, for examle:

% otool -L cctbx_dmtbx_ext.so
cctbx_dmtbx_ext.so:
         /System/Library/Frameworks/Python.framework/Versions/2.3/ 
Python (compatibility version 2.3.0, current version 2.3.5)
         lib/libboost_python.dylib (compatibility version 0.0.0,  
current version 0.0.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
current version 88.0.0)
         /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0,  
current version 7.3.0)
         /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0,  
current version 1.0.0)

Is there a simple way to change that?



All the best,

Bill


William G. Scott

Associate Professor
Department of Chemistry and Biochemistry
and The Center for the Molecular Biology of RNA
Sinsheimer Laboratories
University of California at Santa Cruz
Santa Cruz, California 95064
USA






More information about the cctbxbb mailing list