[ogre] Do not use strict mode by default in ogre for backward compatibility #15789
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.
Describe the pull request
What does your PR fix? All versions of ogre since it was added in vcpkg had the strict resource mode disabled by default. [ogre] make zziplib, freeimage, assimp, freetype and less strict resource manager as feature #15194 added support to enable it as a feature, that is great for user interested in it, but also added it as a default feature, meaning that downstream users of the ogre library may break (see for example Add irrlicht, update vcpkg and install ignition libraries via vcpkg robotology/robotology-superbuild-dependencies-vcpkg#39 (comment)) without any change at all in the Ogre version, just a bump in the vcpkg port version. This PR just removes the
strict
feature from the default enabled features, but any interested user can still enable it if interested.Which triplets are supported/not supported? Have you updated the CI baseline? The change should not affect the CI baseline.
Does your PR follow the maintainer guide? Yes