-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Packages outside RIOT tree #15309
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions. |
Hi there. I'm currently getting up to speed with RIOT and also ran into this issue. I'd like to provide external pkg dirs similar to external modules. @jdavid did you find a workaround? |
@NikLeberg No. Probably the easiest is to keep a fork of RIOT. |
I've hacked together a (very bad) patch that allows setting EXTERNAL_PKG_DIRS. See: 0001-Makefile-add-EXTERNAL_PKG_DIRS.zip Maybe it's of interest. |
Description
It's not possible to make packages outside of RIOT's tree, the way it can be done for modules with
EXTERNAL_MODULE_DIRS
. I get:I added the package to our own tree
wsn_riot/pkg
but it looks for the package in RIOT's tree. Tried addingEXTERNAL_MODULE_DIRS
, didn't find a way in the documentation.We have to package many Arduino libraries for sensors and it would be easier to do if it was possible to package them out of RIOT's tree, as it's possible to do with sys modules and drivers. This would help others that need the same.
Useful links
None. This concerns the RIOT build system.
The text was updated successfully, but these errors were encountered: