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
libdir detection is buggy in many cases #2038
Comments
The default for that should probably be settable in the cross file... |
What settings would it be? sizeof_int? Is there no good way to determine if the target is 64 bit? I could think of checking As a last comment, I would not be against just defaulting to lib/ always, even when the target is know 64-bit. The directory lib64/ is somewhat considered deprecated by many distributions and I think all 64-bit distributions will look in lib/ as well as lib64/ anyway. |
I was thinking more in the line of |
In which section do you set this? I tried under every section in your doc (host_machine, binaries, properties… tried them all just to be sure) but it didn't set Edit: or I realize suddenly, did you actually mean that you should add this? Hence the feature is not there yet? |
Yes. |
ping |
The following changes were made in
|
I think this should have been closed by 4743 as well. I'm going to close this. |
I have been cross-compiling json-glib (which uses meson) for 32-bit and it would install it inside lib64/:
The compilation is fine and renders proper 32-bit:
Only the path is wrong.
Also since I am building from a 64-bit platform, this may be the problem, of course. Basically do not decide on the installation path from the build OS, but from the host one.
I filled a bug in json-glib, but they tell me the problem is with meson: https://bugzilla.gnome.org/show_bug.cgi?id=784532
Also for information, I do not consider the proposed solution of setting
--libdir
valid. I know of this option, which exists on all other build systems (and that's a good option), but it should not be a reason not to have sane defaults.The text was updated successfully, but these errors were encountered: