General comments and questions about meson HOT 4 CLOSED

It seems like you have a dependency library that you are trying to use. It is very strongly recommended that you provide a pkg-config file for that so then you can do this

foodep = dependency('yourlibrary')
executable( ..., dependencies : foodep)

If this is not possible for you, then you can set the flags manually by something like this:

custom_incs = include_directories('prefix/include', ... , '/usr/local/include')
executable(...,
 include_directories : custom_incs,
link_args : '-L/usr/local/lib')

Note that you don't need to set /usr/include to include path or /usr/lib to library path. They are provided by your compiler's default settings.

from meson.

Thank you for the suggestions. We don't use packages at all, at the moment. In fact, both ${PREFIX}/include and ${PREFIX}/lib are install targets for the ${PREFIX}/src/lib parts of the repository. So we have dependency rules to insure they are built first before each app which depends on them is built. Right now, it's all in done in BSD Make, but I'd sure like to use a better tool, like Meson! :-)

from meson.

If you are linking against libraries that you build yourself, you really don't need to deal with linker flags or anything like that.

Say you are in subsystem/lib and do sublib = shared_library(...). Then when you get to some/other/dir you just do executable('myexe', ..., link_with : sublib). Meson will automatically:

• take care of linker flags
• take care of dependencies
• set up rpath so you can run myexe directly from the build dir without fiddling with LD_LIBRARY_PATH or something similar
• unset all this magic when you do "ninja install"

from meson.

The questions raised in this bug seem to be answered so closing. If you have more questions or clarifications, feel free to reopen this bug or file a new one.

from meson.