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
CMake: Search for windows message compiler #3677
Conversation
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
Actually, looking at the appveyor build, I see it failed due to:
@dnakamura Is this a path setup issue? |
Don't just assume that its on the path Signed-off-by: Devin Nakamura <devinn@ca.ibm.com>
@DanHeidinga The issue was that when cmake was run, |
@genie-omr build win xlinux |
set(kit_dir "${kit_dir}/bin/x86") | ||
endif() | ||
# find the message compiler | ||
find_program(CMAKE_MC_COMPILER mc.exe HINTS "${kit_dir}") |
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.
Could the kit_dir
be some call that a user could specify if they have it installed in a random location that they do not want to have on their path?
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.
no matter where they install it, the location should still be stored in the registry (which is where we pull kit_dir
from). If for whatever reason its not in the registry you could still specify -DCMAKE_MC_COMPILER=xxxx
on the command line.
Don't just assume that its on the path
Signed-off-by: Devin Nakamura devinn@ca.ibm.com