We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Guys,
As you can see in https://groups.google.com/forum/#!topic/gqrx/Y1uUZSJ5hJ0, Michael Dickens helped me with an issue in libairspy, whilst trying to install gqrx through macports.
He suggested: Before building libairspy, modify host/libairspy/CMakeLists.txt and add the following near the beginning:
if(APPLE) set(GR_LIBRARY_DIR "lib") if(NOT CMAKE_INSTALL_NAME_DIR) set(CMAKE_INSTALL_NAME_DIR ${CMAKE_INSTALL_PREFIX}/${GR_LIBRARY_DIR} CACHE PATH "Library Install Name Destination Directory" FORCE) endif(NOT CMAKE_INSTALL_NAME_DIR) if(NOT CMAKE_INSTALL_RPATH) set(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_PREFIX}/${GR_LIBRARY_DIR} CACHE PATH "Library Install RPath" FORCE) endif(NOT CMAKE_INSTALL_RPATH) if(NOT CMAKE_BUILD_WITH_INSTALL_RPATH) set(CMAKE_BUILD_WITH_INSTALL_RPATH ON CACHE BOOL "Do Build Using Library Install RPath" FORCE) endif(NOT CMAKE_BUILD_WITH_INSTALL_RPATH) endif(APPLE)
Works for me...
Kind regards and thanks for the good work.
Derk
The text was updated successfully, but these errors were encountered:
Fix CMake issue (@rpath) on osx #15
198b1e5
Thanks for the patch I have fixed it in trunk any feedback is welcome from users with macos ...
Sorry, something went wrong.
No branches or pull requests
Guys,
As you can see in https://groups.google.com/forum/#!topic/gqrx/Y1uUZSJ5hJ0, Michael Dickens helped me with an issue in libairspy, whilst trying to install gqrx through macports.
He suggested:
Before building libairspy, modify host/libairspy/CMakeLists.txt and add the following near the beginning:
Works for me...
Kind regards and thanks for the good work.
Derk
The text was updated successfully, but these errors were encountered: