Split into Runtime and Designtime Packages #7
Conversation
This file contains hidden or 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
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.
Having a combined run- and design-time package is tedious to work with - either when compiling and distributing a project with packages or using List & Label components in another package.
This branch adds separate packages for runtime and designtime and a project group combining them.
I know I got rid of the version 28 in the package names, but put it in the LIBVERSION suffix instead. I don't know why this was introduced in the first place, as it makes upgrading to a newer version unnecessary cumbersome (it still is with some unit and component names). In case this turns out to be mandatory, I probably can be convinced to change the code accordingly.