Feature/bootstrap - Create new C/C++ projects with reference to the upstream tooling #45
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
|
Note - do not merge yet, using this issue to track stuff right now. |
|
See also: lancaster-university/codal-bootstrap#1 - documentation generation issues |
microbit-carlos
added a commit
to microbit-carlos/codal
that referenced
this pull request
Jan 20, 2023
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.
Tracking the
feature/bootstrapbranch here, where changes have been made to allow codal to run as a library in a larger project, rather than requiring the build system to be copied over to each new project.See also https://github.com/lancaster-university/codal-bootstrap for the bootstrap code, where the local build.py acts as a proxy for the codal one.
(More details to follow)