This repository has been archived by the owner on Aug 9, 2023. It is now read-only.
Target profiles, directory generation, and automatically moving dependencies when needed #16
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.
Issue
Each build profile should have their own target folder as each build profile can have different settings. Furthermore, the application being build may require files/folders at runtime, these can be moved from
/deps
(default) to the build profile target directory so the application has direct access to them when it is being ran.Solution
The implementation currently is not very flexible, although this should change when the compilation profile code is refactored in the near future. Below is a list of the features implemented.
/target/{build|run}
(default)/deps
(default) are copied into/target/{build|run}
Notes about the implementation
Currently the entire
/deps
folder is copied. This should be changed to only copy files/folders inside the/deps
.