-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Makefile fixes #2
Conversation
Thank you, could you add your readme.md updates to the copy in the RPi subfolder as well? |
Yup can do, however would it make more sense to just have one of the readme files reference the other rather than having duplicate content ? Another option could be to just symlink one to the other - I believe github honours this but could confuse anyone cloning the repo on Windows. |
Well, yes and no? A reference equals a link, which equals another mouse click and page load on the users part. I like having it in the main RPi folder, since it displays prominently when viewing on GitHub, while users are provided with a local copy when they download the repo. On the ohter hand, It may be better to refer them to the online version, since it will be kept up-to-date, so an html link in the repo readme and/or a symlink may be the way to go? I'm not of a strong opinion one way or the other, as long as things are clear and consistent to users. |
Copy header files to system during 'make install' for convenience,
Few fixes to Makefile:
#include <RF24.h>