-
Notifications
You must be signed in to change notification settings - Fork 676
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
CMake improvements and compiler warning fixes #810
Conversation
recheck |
Newer versions of cmake do not set install_name, so we need to do it ourselves. FindDPDK module did not properly handle version range before, this change fixes this. Also made boost a system dependency to suppress compiler warnings from it.
Some minor formatting, spaces etc
This change fixes a few annoying compiler warnings. Mostly, those are related to unused variables which are simply suppressed. Also fixes a missing virtual destructor which could have resulted in memory issues.
rebased just now. |
Sorry, that was for the CLA checker bot (I did some upgrades to fix that). You already signed the cla on #679, so you don't need to do that again, but I was hoping the CLA checker bot would automatically figure that out. |
Also, thanks for rebasing, and thanks for re-submitting this in the first place (after we had dealt with just the example portion of #679). We're finally in a good spot to review this and merge it. We might cherry-pick some changes and leave out others, though. |
What's your compiler? |
- Added missing override specifiers - Specified CMake policy for FindBoost - Reintroduced capture of chan variable
Reintroduced. You are right, probably leftover from an older state.
Currently: AppleClang 16.0.0.16000026 FYI: in |
I'm going to skip the policy change for now (we support an almost too wide range of CMake versions, and I also want to close this PR ASAP, and I don't want to spend time making sure we don't add a warning on some older CMake for now). Other than that, it's good to go. Should be another few days before it hits master, but thanks again! |
When you build this, what does |
I merged this without the changes to FindDPDK and the policy changes for now. It took a while to untangle issues with our internal CI pipelines (older CMake caused an impressive grind-to-halt on our DPDK tests). I think the |
DPDK_INCLUDE_DIRS | ||
DPDK_CFLAGS DPDK_LDFLAGS | ||
DPDK_LIBRARIES | ||
FAIL_MESSAGE "DPDK not found or misconfigured" |
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.
This is declared "not recommended".
What kind of warning do you see without HANDLE_VERSION_RANGE? |
Pull Request Details
I extracted these changes from my other MR that was closed just now (#679) without any changes to the examples. The original changes were made over a year ago and after rebasing a few of the fixes done there have already been committed in other MRs. What remains is rather little, so should hopefully pose no problems to merge
Description
Basically, after rebasing onto the current version of uhd, here's what these changes still entail:
install_name
wasnt manually set in CMake, which caused a warning in newer CMake versions due to breaking policy changesHANDLE_VERSION_RANGE
flagWhich devices/areas does this affect?
Minor changes to the build system and the host library.
Testing Done
Since this affects mainly the build system, testing was building and verifying that CMake and compiler warnings were fixed.
Checklist
I have added tests to cover my changes, andall previous tests pass.MPM compat, noc_shell, specific RFNoC block, ...)