Skip to content
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

Build error - Target "CpuFeatures::cpu_features" not found. #629

Closed
ashley-b opened this issue Sep 14, 2023 · 3 comments · Fixed by #631
Closed

Build error - Target "CpuFeatures::cpu_features" not found. #629

ashley-b opened this issue Sep 14, 2023 · 3 comments · Fixed by #631

Comments

@ashley-b
Copy link
Contributor

ashley-b commented Sep 14, 2023

CMake Error at lib/CMakeLists.txt:524 (target_include_directories):
  Error evaluating generator expression:

    $<TARGET_PROPERTY:CpuFeatures::cpu_features,INTERFACE_INCLUDE_DIRECTORIES>

  Target "CpuFeatures::cpu_features" not found.

This CpuFeatures::cpu_features should be CpuFeature::cpu_features

Also this if/else block seem redundant to me, in both branches it is including cpu_features far as I can tell
https://github.com/gnuradio/volk/blob/efa2220e6f0b50724618b006457f97eb748327e7/lib/CMakeLists.txt#L523C1-L531C10

@ashley-b ashley-b changed the title Build error Build error - Target "CpuFeatures::cpu_features" not found. Sep 14, 2023
@ashley-b
Copy link
Contributor Author

As a back story I have been trying to link volk to an external version of cpu_features.

I have dug into cpu_feature and think I have found an issue with it.
When it is built separately it exports a target name CpuFeatures but when it is built as a sub-project it uses CpuFeature

For reference
google/cpu_features#333

@jdemel
Copy link
Contributor

jdemel commented Sep 14, 2023

Ah! Thanks for reporting this. And also for opening the upstream issue.

We need to monitor this and update the git submodule pointer accordingly. I hope this will be fixed soon.

@jdemel
Copy link
Contributor

jdemel commented Sep 15, 2023

The upstream issue is fixed:
google/cpu_features@982ae38
This was the corresponding PR: google/cpu_features#334

For us, this implies that we update the submodule pointer and fix the 2 lines that were updated in #603.

Since none of this is part of a release yet, I assume we don't need to worry about any backwards compatibility.

@jdemel jdemel linked a pull request Sep 19, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants