Closed mmverstraete closed 4 years ago
The README and documentation have notes about how to enable the IDL DLM path and are pretty up front that this needs an extra step: ... Setup your Mtk environment (pick any):
For csh:
source $MTK_INSTALLDIR/bin/Mtk_c_env.csh for C
source $MTK_INSTALLDIR/bin/Mtk_idl_env.csh for IDL
source $MTK_INSTALLDIR/bin/Mtk_python_env.csh for Python (Don't need
to do if installed in site-packages (see step 8))
For bash:
. $MTK_INSTALLDIR/bin/Mtk_c_env.sh for C
. $MTK_INSTALLDIR/bin/Mtk_idl_env.sh for IDL
. $MTK_INSTALLDIR/bin/Mtk_python_env.sh for Python (Don't need to do
if installed in site-packages (see step 8))
Can you suggest a way we can make it more clear that users should be undertaking these steps if they want to use Mtk?
Thanks for your quick response. I think this issue will be resolved once "Issue #3" will be addressed: the point is that the README file is currently NOT seen by users who only rely only on the script package for Macs. - Michel.
The previous installers are no longer used and a new system was developed for distribution that includes a README in all packages and within the IDL package's README it explains the addition of the IDL_DLM_PATH environment variable or setting the IDL_DLM_PATH preference in IDL.
Please feel free to comment if this is not adequate or there is some suggestion for improvement.
Whenever the MtkInstaller-1.5.0.pkg package completes the installation of Mtk successfully on a Mac, it currently leaves the two files 'idl_MisrToolkit.dlm' and 'idl_MisrToolkit.so' in the /Applications/Mtk-1.5.0/ subdirectory, where IDL will not find them by default. It would be much more useful to copy or move those two files in the folder where IDL expects to find all DLMs, or to modify the DLM_PATH of IDL to point to this folder. If neither action can be easily implemented (or is not safe for an external script to do), then a message to this effect needs to be provided so the user understands that one more step needs to be done manually. - Michel.