classes/cmake: Set CMAKE_SYSTEM_PROCESSOR #102
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some CMake scripts access this variable unconditionally, such as
libjpeg-turbo
's. Looking at the official docs they seem to be right in the assumption thatCMAKE_SYSTEM_PROCESSOR
will always be set.Content-wise the variable seems to match the first part of the
AUTOCONF_HOST
triplet for all Unix-ish OSs. I'm not sure how the whole cygwin/mingw-stuff has to be handled here, though, since normally Windows has its own possible settings forCMAKE_SYSTEM_PROCESSOR
likeAMD64
,ARM64
orIA64
. Do we need to take those when compiling via cygwin/mingw or just the same first part of the triplet? I'd say that it'll probably make no difference in the majority of cases but I'd rather provide a correct solution, anyways.