feat: allow custom priconfig #25
Open
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.
Allow user-provided
priconfig.xmljust likeappxmanifest.xml.A default
priconfig.xmlgenerated bymakepri createconfigsimply exports every single file in the package, recursively. Also because<autoResourcePackage qualifier="Language"/>is set,makepriautomatically createsresources.language-xx.prifor every language even when you don't use any language specific resources. This is most likely undesired, and users would instead want to provide their ownpriconfig.xml.The new
PackagingOptionsparameters are designed to not affect current behavior. If you would prefer a different schema let me know.One minor difference is that the original code path of
makepri createconfigcreates the config directly in the package directory, and thus will be packaged into themsix. In this implementation when users provide a custompriconfig.xmlit will not be copied into the package directory. I'm not sure whether this is worth mentioning in README, or should add as an option, because you don't need to ship thepriconfig.xml, only theresources.pri.