-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Reduce unnecessary nesting in "CMakeLists.txt" #2718
Reduce unnecessary nesting in "CMakeLists.txt" #2718
Conversation
f76ca8a
to
1531b2d
Compare
I've restarted the Ubuntu job two times, but it always failed. This does not look like a compilation problem, rather like the agent is running out of memory and loses communication. Question is, what is it in this pull request that affected the build? |
Mhm, there are only two changed which could have an effect:
to
But I now believe this adjustment was not correct, even it should not affect Ubuntu build. I believed
|
if(UNIX OR APPLE)
set(CUDA_NVCC_FLAGS ${CUDA_NVCC_FLAGS} "-Xcompiler;-fPIC;")
endif()
if(NOT UNIX) # Removed APPLE, because if NOT UNIX is already true, value of APPLE, WIN32, ... doesn't matter
add_definitions(-DPCLAPI_EXPORTS)
endif() Are you sure that |
Generally, I don't have a good feeling about this PR in it's current state. We need to have absolutely clear separation between commits that only change indentation, commits that change variable names, and commits that (potentially) alter the logic. Otherwise, if a problem is discovered later on, we will need to skim through 5K lines trying to identify if we have some "innocent fix" that was smuggled together with indentation change. |
I have reverted logic change to this (see last commit), so this PR should just adjust nesting and indentation (except the one thing with |
Last entries on log before crash:
But I don't see any big CMake adjustments in test/registration/CMakeFiles. Can you rerun build of last successful build (ba0a6a6), so we can see, if it is not any other issue? |
Let's see: https://dev.azure.com/PointCloudLibrary/pcl/_build/results?buildId=499 Edit: maybe we should consider splitting |
Found an issue by comparing resulting Makefile before and after my change. Now they are equal :) |
Old code: pcl/test/surface/CMakeLists.txt Lines 11 to 12 in f3dac94
New code: if(NOT (build OR (BUILD_io AND BUILD_features)))
return()
endif() This is not equivalent. Where does |
8db53ee
to
df99a0a
Compare
You are right. Fixed. |
Failed too, so it seems a issue not related to this PR. |
We need to resolve a conflict and to rebase here as well, then can merge if the pipelines succeed. |
…ion parameter exists
df99a0a
to
acaab2d
Compare
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 was going through the PR one last time and noticed this change in NSIS. Please revert it and then I'll merge.
Reduce unnecessary nesting in CMakeLists.txt in case global deactivation parameter exists.
Example:
Old:
new:
PS @whoever is reviewing this: I hope you are not using GitHub diff view to check this PR. A diff view where you can ignore whitespace changes is much better here ;)