On 06/02/09 08:18, Kevin Cowtan wrote: > I can see implementation problems. It looks to me as though this will > only work if you build in place. All the coot dependencies get built in > their own trees and the installed later. I suspect therefore that the > link step might not work, because the rpath will be wrong until the > binaries are shifted into place. Maybe that can be dealt with using > LD_LIBRARY_PATH while building (but I'm out of my depth here).
Yes, I suppose run-time linking may fail if the coot is run before it's installed. The Autotools (or rather, libtool, I guess) solve this by outputting temporary wrapper scripts to resolve runtime linking until the everything is installed--sort of like the coot wrapper, I presume. Whether this will work robustly across the full set of coot dependencies, I dare not say. Then again... for practical purposes I think it's a non-issue. This has been an enlightening thread. Thanks, all! // Cheers; Johan
