build: use default cache path for squish craft target instead of separate squish path #12025
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
|
@DeepDiver1975 Could you check if this is valid and doesn't affect anything else? If we merge this then we can also remove these: |
saw-jan
force-pushed
the
build/squish-cache-path
branch
from
02a4c37 to
0611a4b
Compare
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.
By using the following as a cache path for
inux-gcc-x86_64-squishcraft target, we can separately define which Qt version to use for this target and we also omit the necessity of creating separate squish cache pathPackager/CacheVersion = ${Variables:ownCloudVersion}/Qt_${linux-gcc-x86_64-squish-BlueprintSettings:libs/qt6.version}_${Variables:CachePatchLvl}This targets the linux cache folder of defined Qt version for libraries and we no longer require squish cache folder