-
Notifications
You must be signed in to change notification settings - Fork 15
started to update the project to the current Beman standard #151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
73c7631
to
bd17f0f
Compare
I can not understand what is going on this project?see https://github.com/ClausKlein/execution/actions/runs/15373746732/job/43256183253#step:5:121 Some of my checks are deleted? The build fails on OSX? The installed version is not usable: bash-5.2$ cmake -B build -S .
CMake Error at CMakeLists.txt:17 (find_package):
Could not find a configuration file for package "beman.execution" that
exactly matches requested version "0.0.2".
The following configuration files were considered but not accepted:
/Users/clausklein/.local/lib/cmake/beman.execution/beman.execution-config.cmake, version: unknown
-- Configuring incomplete, errors occurred!
bash-5.2$ ... |
Do you know why this code was removed and what the konsequences are?if(NOT PROJECT_IS_TOP_LEVEL)
# test if the targets are findable from the build directory
# cmake-format: off
add_test(NAME find-package-test
COMMAND ${CMAKE_CTEST_COMMAND}
# --verbose
--output-on-failure
-C $<CONFIG>
--build-and-test
"${CMAKE_CURRENT_SOURCE_DIR}"
"${CMAKE_CURRENT_BINARY_DIR}/find-package-test"
--build-generator ${CMAKE_GENERATOR}
--build-makeprogram ${CMAKE_MAKE_PROGRAM}
--build-options
"-DCMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER}"
"-DCMAKE_CXX_STANDARD=${CMAKE_CXX_STANDARD}"
"-DCMAKE_BUILD_TYPE=$<CONFIG>"
"-DCMAKE_PREFIX_PATH=${CMAKE_PREFIX_PATH}"
# TODO(CK): Needed too? "--config $<CONFIG>"
)
# cmake-format: on
endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
damit ist quasi das project tot!
tests/beman/execution/CMakeLists.txt
Outdated
"${CMAKE_CURRENT_SOURCE_DIR}" | ||
"${CMAKE_CURRENT_BINARY_DIR}/find-package-test" | ||
--build-generator ${CMAKE_GENERATOR} | ||
--build-makeprogram ${CMAKE_MAKE_PROGRAM} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... den sie wissen nicht was sie tun!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to my previous comment, I admit that I don't understand what this test tries to achieve. In my development it was always executed (and I haven't figured out, yet, why) and took a substantial amount of time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with bemanproject/exemplar#173 this variant, only examples are used.
|
||
if(PROJECT_IS_TOP_LEVEL) | ||
find_package(beman_execution 0.0.1 EXACT QUIET) | ||
if(beman_execution_FOUND) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... den sie wissen nicht was sie tun!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do understand the German but I don't quite understand the implication. I admit that I don't understand what that is trying to achieve. There is certainly no equivalent logic in the exemplar
version of the file. Explicitly testing for a version number seems ill-advised, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At C++Now we had multiple discussions on the build infrastructure. The general consensus was (is?) that Beman projects should have mainly identical builds: the overall development should happen on the exemplar and/or infra repository(-ies). There are multiple parties interested in getting build right, including people from Kitware who can change The current PR is a draft bringing
Yes: see above. If the checks are useful/necessary I think they should be present in all Beman projects alike. While consistency was (is) the main driver, a secondary reason for me was that the
It most certainly doesn't when I build on my local machine(s) (I'm developing on Macs) or in the CI github. However, these use Apple's
The error on issue 153 looks like a mismatch between the used C++ run-time library and the library it was compiled with. I just noticed that the issue is with Intel Macs - so far I have only tried to run ARM Macs. I'll try with an Intel Mac, too.
That's more concerning: that is something obviously undesirable. I haven't tried the changes, yet, with projects depending on I don't have a project set up which uses |
* Restore basic cmake features * Link required threads libs * Add runtime dependency
|
I have brew installed with llvm-20. I need |
The new workflow presets are not usable in general! My old presets supports also package preset. How would you install after a workflow build? |
@dietmarkuehl close this MR please! |
see #155