Replies: 2 comments
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This may be similar to #410 but my use-case is different.
I am using meson to build python extension (hdlConvertor) which depends on cmake builded library (antlr4 cpp runtime).
I can build and run the library, but during the installation the
pip3 install .fails on this linemeson-python/mesonpy/__init__.py
Line 163 in 78def82
cmake builded antlr4 library contains
If I remove it, it works, but I would like to keep it and somehow tell cmake from meson that the target should not be installed or where it shoud be installed.
'CMAKE_SKIP_INSTALL_RULES': true, 'CMAKE_SKIP_INSTALL_ALL_DEPENDENCY': true,does not seem to work.During the build I can see
But the install target still appears in intro-install_plan.json.
I guess that it is meson issue because wit set_install(false) it works https://github.com/mesonbuild/meson/blob/master/docs/markdown/CMake-module.md#cmake-options-object
Should I somehow specify the
INSTALL_PREFIXfor mentioned antrl4 library or I need to somehow exclude the library from installation?I am trying to ask if the current meson-python supports the installation of such files
or I need to found out a way how to remove the file
or if I should implement this and send pull request to meson-python.
How can I get {prefix}, {includedir}, {libdir} and others in meson?mesonbuild/meson#10777 - mentioned constants must stay in
meson-info/intro-install_plan.jsonin their native form.However if I just add
I will end up with
"<project>/build/subprojects/antlr4-runtime/__CMake_build/{libdir}/lib/libantlr4_static.a",instead of just
{libdir}/lib/libantlr4_static.a, any ideas?Beta Was this translation helpful? Give feedback.
All reactions