Skip to content
New issue

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

[Question] why link to librf24-bcm? #175

Closed
2bndy5 opened this issue May 29, 2021 · 2 comments · Fixed by #176
Closed

[Question] why link to librf24-bcm? #175

2bndy5 opened this issue May 29, 2021 · 2 comments · Fixed by #176
Labels

Comments

@2bndy5
Copy link
Member

2bndy5 commented May 29, 2021

I took a peek at the makefile for this lib to envision what is needed to implement CMake as an alternative build system. But I found that this lib links to a symlink that is marked deprecated (via variable name) in the RF24 lib's configure file.

Currently the CMake implementation for the RF24 lib does not build and install this librf24-bcm.so. Is this going to be a problem going forward with CMake for RF24Network?

Other than this question, I think implementing CMake for this lib (& RF24Mesh) will be a simple matter of copy-n-paste (with differently defined install rules) from the RF24 lib's CMake for Linux implementation.

@2bndy5
Copy link
Member Author

2bndy5 commented May 29, 2021

I'm also assuming the jam file in the lib's root is another relic from ManiacBug days.

@2bndy5
Copy link
Member Author

2bndy5 commented May 29, 2021

I think this may answer my own question

brendan@B-DESKTOP:/mnt/c/Users/ytreh$ file /usr/local/lib/librf24-bcm.so
/usr/local/lib/librf24-bcm.so: symbolic link to /usr/local/lib/librf24.so

So it seems that the deprecated symlink is just an alias for the latest installed librf24.so?

@2bndy5 2bndy5 linked a pull request Jun 19, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant