This suggestion addresses the potential that the TARGET environment might be
able to utilize the feature.
Just because I can compile code for a hypothetical target machine, there is no
guarantee that the actual target machine will have the necessary features.
I recognize that most compilations h
I was not aware that the export of ANY of the additional information had ever
been implemented.
${CMAKE_HOST_HAS_} was just my suggestion for a possible naming
convention.
Richard
On Mar 26, 2010, at 8:25 PM, Alexander Tarasov wrote:
> First of all the ${CMAKE_HOST_HAS_} does not seem to work
First of all the ${CMAKE_HOST_HAS_} does not seem to work.
Also I've looked through the patch submitted in the context of bug
#7273. It looks like it implements (fixes) the CPU features retrieval
but it does not export them to the cmake user.
As far as I understand the only way to export a cm
You can use the "Try_Compile()" function with a source file that has
specific SSE and MMX code. If the file compiles correctly then you
have SSE/MMX.
This is what I used:
# --- Begin
set (SSE_COMPILE_FLAGS "")
option(AIM_USE_SSE "Use SSE2/3 Instructions where possible." OFF)
if (AIM_U
Hi All,
Is there a clean way to find out if host CPU supports MMX & SSE2 extensions?
As far as I know this stuff is analyzed by cmake (am I wrong?). However
I've did not find any way this info can be used in CMakeLists.txt.
Best regards,
Alexander.
