-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
suport for exec_prefix and libexecdir #364
Comments
What are the use cases for these? When would you install to exec-prefix/libexecdir/whatever instead of regular prefix/bin or somesuch? Is there a case when a project would want to install to both at the same time? |
Not sure how much light I can shed on practical use cases here, I can only point out that these exist in the autotools-world and that in my experience distro packagers make use of all of these (perhaps due to packaging guidelines): https://www.gnu.org/prep/standards/html_node/Directory-Variables.html |
Hmmm. That document does not really tell why they are needed, only that they are. And it is written assuming (understandably) Autotools' late evaluation semantics. I'm all for supporting this, but I'm hesitant to add functionality without understanding the reasoning behind it. That usually leads to code that seems to work but does the wrong thing. Getting comments from someone who has dealt with this issue would be necessary to get this functionality to come out right. |
libexecdir sometimes is used.. For |
In theory, |
|
I noticed meson does not have out of the box support for libexecdir yet.
Or, more generally speaking, there's also no distinction between --prefix and --exec-prefix which autotools seems to make these days, e.g. ./configure --help shows:
It seems to default to this for libexecdir, but distros will likely want to override that:
exec_prefix will likely be the same as prefix, and default to the same, but the distinction seems useful.
The text was updated successfully, but these errors were encountered: