Fix coojas path configuration when used without contiki #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the dependency of cooja to be in contiki's directory structure. This way cooja can be used standalone.
As it is right now without this patch, if one only downloads cooja and tries to start it, cooja does not find the default apps:
PATH_CONTIKIis configured as../../..in Cooja;cooja.jarlies incontiki-ng/tools/cooja/build, soPATH_CONTIKIwill becontiki-ngPATH_CONTIKI/tools/coojais then used as root for cooja and everything else (extensions)This patch uses coojas path instead.
PATH_CONTIKIandPATH_COOJAare both still configurable stuff like[APPS_DIR]is now inPATH_COOJA/appsinstead ofPATH_CONTIKI/tools/cooja/apps