-
Notifications
You must be signed in to change notification settings - Fork 207
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
Use CpuFeatures target #603
Conversation
"Build static on ubuntu-latest" fails because:
don't know why that happens, but not on the older ubuntus. |
I don't understand either. When I get a break, I was going to try to
recreate the error in a docker container.
…On Wed, Sep 28, 2022, 10:07 AM Marcus Müller ***@***.***> wrote:
"Build static on ubuntu-latest" fails because:
Target "volk_static" links to:
CpuFeatures::cpu_features
but the target was not found.
don't know why that happens, but not on the older ubuntus.
—
Reply to this email directly, view it on GitHub
<#603 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHPWDXF4ORHHJF7KKVYGAGDWARGI5ANCNFSM6AAAAAAQXEB3OE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
hm maybe the others use a directly downloaded cpufeatures and the most current one relies on a ubuntu package? |
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.
LGTM. I was under the impression we would do this everywhere. Also, I assumed cpu_features
is an alias for CpuFeatures::cpu_features
. Do we use the same approach for the dynamic library?
Oops. This change actually breaks on ubuntu-latest
. Also, could you just sign your commit to acknowledge our DCO process. That'd be great.
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.
LGTM after this change
Any chance of this getting merged in ? |
@jsallay I guess @ashley-b 's question is mostly direct at you. I'd like to merge this as soon as all issues are fixed. That would be
|
@jsallay Thanks for the quick follow up, I just tried building it in a ubuntu container and it built with out error lsb_release -a
Also I noticed not all the target_link_librarys for cpu_feature have been changed to use modern CMake targets. and This block does not make sense, since both lines of the if/else seem to do the same thing |
Signed-off-by: John Sallay <jasallay@gmail.com>
823e88a
to
c09d788
Compare
Signed-off-by: John Sallay <jasallay@gmail.com>
Signed-off-by: John Sallay <jasallay@gmail.com>
Looks like |
@jsallay thanks for taking care of this PR. It looks good to me now. All the comments are addressed. Merging. |
The build process is more flexible if we use cmake targets rather than directly linking to libraries. The target is used in other places in the CMakeLists.txt, but was not used in the target_link_libraries command.