The Unix and Windows installation scripts can take the M269 folder as argument. If install.sh is called with a relative path like .., it exits with error message '.. is not called M269-23J'. The Windows script may have the same problem. Steps to fix:
[x] In function is_m269_folder, if argument is a folder, expand it with $(cd "$1"; pwd) before checking the basename
[ ] Similarly for Windows, I imagine
[ ] Test with paths like ., .., subfolder/../../folder/subfolder
The Unix and Windows installation scripts can take the M269 folder as argument. If
install.shis called with a relative path like.., it exits with error message '.. is not called M269-23J'. The Windows script may have the same problem. Steps to fix:is_m269_folder, if argument is a folder, expand it with$(cd "$1"; pwd)before checking the basename.,..,subfolder/../../folder/subfolder