build: Fix missing FreeSOLID includes error. #46
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
windows
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: speed-dreams/speed-dreams-code#46
Loading…
Reference in a new issue
No description provided.
Delete branch "apteryx/speed-dreams-code:fix-feesolid-missing-include"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
to include directories of sumv4.1.
to include directories of sumv4.
to include directories of sumv5.
Fixes: #45
63c793e5f6
to8555176241
build: Add missing FreeSOLID include directories.to build: Fix missing FreeSOLID includes error.@ -82,6 +82,14 @@ if(NOT SOLID_FOUND)
add_subdirectory(freesolid)
endif()
if(TARGET PkgConfig::SOLID)
Instead of assigning a
SOLID_TARGET
variable and assign its value based on the condition above, I would rather set up anALIAS
target oncmake/FindSOLID.cmake
so that thesolid
target can be transparently used:WDYT?
I didn't know about ALIAS; that sounds like a good idea indeed! I'll push a new revision shortly.
@ -24,2 +23,3 @@
PKG_CHECK_MODULES(SOLID FreeSOLID IMPORTED_TARGET)
IF(NOT SOLID_FOUND)
PKG_CHECK_MODULES(SOLID SOLID)
PKG_CHECK_MODULES(SOLID SOLID IMPORTED_TARGET)
Related to this, add the following suggestion inside the
IF(SOLID_FOUND)
condition:@ -32,3 +32,3 @@
#SET_TARGET_PROPERTIES(simuv3 PROPERTIES VERSION ${VERSION} SOVERSION 0.0.0)
ADD_SDLIB_LIBRARY(simuv3 portability tgf robottools solid)
ADD_SDLIB_LIBRARY(simuv3 portability tgf robottools ${SOLID_TARGET})
This change should not be required if an
ALIAS
target is set.@ -32,3 +32,2 @@
#SET_TARGET_PROPERTIES(simuv2.1 PROPERTIES VERSION ${VERSION} SOVERSION 0.0.0)
ADD_SDLIB_LIBRARY(simuv4.1 portability tgf robottools solid)
ADD_SDLIB_LIBRARY(simuv4.1 portability tgf robottools ${SOLID_TARGET})
This change should not be required if an
ALIAS
target is set.@ -32,3 +32,3 @@
#SET_TARGET_PROPERTIES(simuv2.1 PROPERTIES VERSION ${VERSION} SOVERSION 0.0.0)
ADD_SDLIB_LIBRARY(simuv4 portability tgf robottools solid)
ADD_SDLIB_LIBRARY(simuv4 portability tgf robottools ${SOLID_TARGET})
This change should not be required if an
ALIAS
target is set.@ -32,3 +32,3 @@
#SET_TARGET_PROPERTIES(simuv2.1 PROPERTIES VERSION ${VERSION} SOVERSION 0.0.0)
ADD_SDLIB_LIBRARY(simuv5 portability tgf robottools solid)
ADD_SDLIB_LIBRARY(simuv5 portability tgf robottools ${SOLID_TARGET})
This change should not be required if an
ALIAS
target is set.8555176241
to49c039da64
I've implemented the suggestions; it's now a 3 lines change, thank you!
LGTM, thank you!
I have just approved the workflows so that the artifacts are made available from the CI/CD.
Yay! But it seems there's currently an issue with the workflow/CI (git clone fails).
This is a known issue:
git clone
fails when the PR comes from a forked repository. I wroteforgejo-clone
and more specifically #44 to fix several issues, including this one.#44 has been merged. Please rebase against latest
main
so the workflows can work again.49c039da64
to3046331a70
You rock! Thanks for working both on this cool game and on the forge that hosts its development. I've now rebased and force pushed.
I have just merged #52 to fix one last standing issue with the CI/CD on forked repositories. @apteryx could you please rebase again?
Thank you!
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.