-
Notifications
You must be signed in to change notification settings - Fork 375
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 when including XNNPACK using FetchContent #5669
Comments
Thanks for the report! That is very much not expected — sorry about that! I’ll try to get out a PR asap to fix that. Out of curiosity, does changing it to |
Replacing all the CMAKE_PROJECT_NAME usages with PROJECT_NAME in CMakeLists.txt works for the Config.cmake.in filename but I get errors about the install. I don't actually need/want to install but I don't think there's an option to disable that.
|
Can you try with 0da379f (the commit after the one you used in your original post) or newer? It looks like my change was reverted since then. Let me know if that works and I'll submit a PR to re-land my changes and tag you to ask you to review to ensure there's no breakage. Again, sorry about this! |
No issues with that commit. I tried with the changes in #5676 applied to the latest master but still get the export errors. If I comment out these lines I can avoid that (but that's probably expected).
|
If I include XNNPACK as a checksummed archive for security reasons using FetchContent
e.g.
the recent change in #5031 results in the build breaking as CMAKE_PROJECT_NAME is set to my project's name and
cmake/<my arbitrary project name>Config.cmake.in
does not exist:XNNPACK/CMakeLists.txt
Line 958 in 21df17d
@ConnorBaker Is this expected?
The text was updated successfully, but these errors were encountered: