Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Build routine] Automatic detection of installation path #121

Open
kevinmatthes opened this issue Oct 29, 2021 · 2 comments
Open

[Build routine] Automatic detection of installation path #121

kevinmatthes opened this issue Oct 29, 2021 · 2 comments
Labels
automation Suggestions and possible candidates for automation. build routine Topics concerning the build routine. enhancement question
Milestone

Comments

@kevinmatthes
Copy link
Contributor

When building the project using the ./configure step, users might pass the options --with-matlab= and --with-octave=, followed by the actual installation path each.

UNIX systems offer the which command which returns exactly this installation path. For instance, the default Octave installation may be referred by

./configure <other options here> --with-octave=`which octave`

Windows offers such a semantic, as well. There, the default installation location may be referenced by Magic Variables, framed within %.

I would like to suggest the following additional feature: if users have multiple installations on their systems, they may decide to use the default one (which octave / which matlab) by using another option, --with-default-octave / --with-default-matlab, for example, or by directly stating the paths with the current options. This would benefit the build and testing procedure on systems where just one version of the applications is installed. Most users can be expected to configure their preferred version as default to their account such that this feature would come in handy.

The usage of the system semantics for installation location detection would furthermore reduce the possibility of mistakes during the build process due to some incorrectly stated paths. Since the OS is detected during the build in an earlier step, the semantic would be chosen depending on the already known value, hence the selection would be processed securely.

What do you think about this additional feature?

@kevinmatthes kevinmatthes added enhancement question automation Suggestions and possible candidates for automation. build routine Topics concerning the build routine. labels Oct 29, 2021
@kevinmatthes kevinmatthes added this to the 3.5.3 milestone Oct 29, 2021
@michaelquellmalz
Copy link
Member

Sounds good if you come up with a solution. Maybe the easiest way for users might be if you say --with-matlab without options, then it tries to determine the Matlab path and throws an error if it does not find any, and if you use it with an argument then it is the old behavior.

By the way, we use bash also on Windows. Then one might look for subfolders of $PROGRAMFILES/Matlab, usually named something like R2020b.

@tvolkmer
Copy link
Contributor

Sounds good to me as well. I agree with Michael on --with-matlab without options.

@kevinmatthes kevinmatthes modified the milestones: 3.5.3, 4.0.0 Nov 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Suggestions and possible candidates for automation. build routine Topics concerning the build routine. enhancement question
Projects
None yet
Development

No branches or pull requests

3 participants