We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With GCC and Rocky-9 Linux, and cmake 3.26.5, the path for building pufferfish on Arm is not being followed.
Adding a 'message' to dump out the CMAKE_SYSTEM_PROCESSOR shows it to be empty at the point of the if statement in CMakeLists.txt.
According to: https://stackoverflow.com/questions/51024294/cmake-system-processor-seems-to-be-empty-whats-the-best-strategy-for-os-agnost - this value is only set after the project() declaration. However, Pufferfish puts this logic before the "project" declaration.
Fix: move the project("pufferfish") to line 1 of CMakeLists.txt.
The text was updated successfully, but these errors were encountered:
Update CMakeLists.txt to put project declaration first
a38852a
Fixes COMBINE-lab#49.
Successfully merging a pull request may close this issue.
With GCC and Rocky-9 Linux, and cmake 3.26.5, the path for building pufferfish on Arm is not being followed.
Adding a 'message' to dump out the CMAKE_SYSTEM_PROCESSOR shows it to be empty at the point of the if statement in CMakeLists.txt.
According to: https://stackoverflow.com/questions/51024294/cmake-system-processor-seems-to-be-empty-whats-the-best-strategy-for-os-agnost - this value is only set after the project() declaration. However, Pufferfish puts this logic before the "project" declaration.
Fix: move the project("pufferfish") to line 1 of CMakeLists.txt.
The text was updated successfully, but these errors were encountered: