Opened 18 years ago
Closed 15 years ago
#57 closed defect (fixed)
allow to run setup.csh from any place
| Reported by: | Owned by: | arnault | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | a. Usage | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Marco.Clemencic@…, Pere.Mato@… | OS: | All |
| If Other, could you precise: | Experiment: | LHCb | |
| If Other, could you precise: | |||
| Stack trace: | |||
| Steps to reproduce: | |||
Description
We have a problem with the setup.[c]sh (setup.bat on windows) script which is produced by "cmt config" and I think this is a defect.
Without using the project paradigm, we could setup the runtime environment of a package simply by doing "source [path to package]/cmt/setup.csh". And everything was working fine, deduced from the CMTPATH variable.
Now with the CMTPROJECTPATH, we cannot do this anymore. If I do the previous command in a random directory (with a correct CMTPROJECTPATH) this will failed. The setup will not be done.
In order tout have the setup script run correctly, I have to go to the cmt directory of the package I want to setup and run the "source setup.csh" from there.
Kind regards,
Hubert
This is now resolved in version CMT v1r21.