meta-lxatac-software: tinyxml2: remove recipe #200
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
This allows us to drop our own tinyxml2 recipe in the next step and also aligns the recipe with the uuu recipe in meta-freescale. Signed-off-by: Leonard Göhrs <[email protected]>
The recipe was introduced under the false assumption that tinyxml2 has not been packaged. It is though and has been for quite some time as libtinyxml2 in meta-oe. This means there is no reason to keep our local recipe. Signed-off-by: Leonard Göhrs <[email protected]>
Emantor
approved these changes
Oct 30, 2024
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.
I've noticed that we can remove our local
tinyxml2recipe becauselibtinyxml2is already in meta-oe (and has been for a long time. Not sure why I did not notice back then).This came up while investigation whether we should upsteam the
imx-uuupackage somewhere.There is however already a
uuurecipe inmeta-freescale, so I guess the answer is no.Adding the
meta-freescalelayer just for this recipe does not seem like a sensible thing to do either, so I guess things will stay as they are.