Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Meson looks nice, but it still lacks a way to tell it where your dependencies are installed(like cmake’s CMAKE_PREFIX_PATH). You can try to get by, by setting pkg config path, but it doesn’t help for dependencies that don’t support pkgconfig.


You can try xmake's dependency package management.

    add_requires("libuv master", "ffmpeg", "zlib 1.20.*")
    add_requires("tbox >1.6.1", {optional = true, debug = true})
    target("test")
        set_kind("shared")
        add_files("src/*.c")
        add_packages("libuv", "ffmpeg", "tbox", "zlib")


> a way to tell it where your dependencies are installed(like cmake’s CMAKE_PREFIX_PATH).

That's not how dependencies are discovered in cmake. Dependencies are added with calls to find_package, and if you have to include dependencies that don't install their cmake or even pkconfig module then you add your own Find<dependency>.cmake file to the project to search for it, set targets, and perform sanity checks.


That's not entirely true, CMAKE_PREFIX_PATH is used in find_package and find_library calls.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: