Makefile: build starfyre #15
Merged
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
|
blocked on #16 |
This is something that I am not even sure of. But we can assume 27 for now. |
|
post merge for issue tracking: Towards #11 |
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.
Updates the Makefile to
make buildthestarfyresource.make in-devwill now actually build the currentstarfyreand make it available intest-application.There are still a few limitations:
python,rust,cargo,emccon your machine but good place to start.starfyre-0.4.1-cp310-cp310-**emscripten_3_1_27**_wasm32.whlwheelFollow ups, remove files:
package.json- unused.cargo.lock- iiuc, this shouldnt be in the source control for libraries.poetry.lock- we dont seem to use poetry at the moment?build.sh- unused.