Use relative resource paths in PDX root #103
Merged
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.
Adds resource subdirectory preservation so users can organize their subdirectories and take advantage of pdxinfo features to allow marketing resources to be grouped.
Resources are copied with their relative folder structure preserved.
A
Resources
folder is required in the package module source and only it's contents are copied.This removes the possibility of copying things like Source Art and documentation to the pdx.
PlaydateKit's
Resources/Core/
has been renamed toResources/PlaydateKit/
which is less likely to cause collisions with users own resource subdirectory names.The pdxinfo file is always copied to the pdx root no matter what subdirectory it is in.
This PR builds on the ideas in #75 by @YogurtTheHorse