You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least on Linux /usr/share/cmake/Csound/FindCsound.cmake is shipped with csound, which allows to find the location of the library and everything else needed to make use of it.
build.rs should check for this and make use of it instead of only looking in hardcoded locations.
There's probably a way to have cmake evaluate it and give cargo the relevant information.
The text was updated successfully, but these errors were encountered:
There's probably a way to have cmake evaluate it and give cargo the relevant information.
The way is to have a dummy cmake build system and extract the information from the files generated by cmake. And that's why it's a bad idea to use cmake... too bad csound doesn't even provide a pkg-config file.
yeah, It is like mocking all the process and doing it in the build.rs. I already looked at this. Thinking of adding support for pkg-config, at least for linux .
At least on Linux
/usr/share/cmake/Csound/FindCsound.cmake
is shipped with csound, which allows to find the location of the library and everything else needed to make use of it.build.rs
should check for this and make use of it instead of only looking in hardcoded locations.There's probably a way to have
cmake
evaluate it and give cargo the relevant information.The text was updated successfully, but these errors were encountered: