-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Wish: accept *.obj on par with *.o for non-Windows targets #4733
Comments
For linking? I assume you can just pass the object files as linker flags then - |
Can you be more specific? What is "this" case? |
Yes
CMake build system does this by different way. (Actually, I am faced with this issue when building
Clang accepts object files for linking with name
I came across the fact that for Also, tested right now - when building for Linux Clang uses same approach |
At the moment, such targets strictly require files with
.o
extensionThis leads to issues with CMake - CMake produces
.obj
files for non-Unix && non-Windows targets. As result, this forces to use in CMake scripts additional config file (it must be a separate file) in a such manner:set_o_output_extension.cmake
:Clang accepts both variants in this case.
Do we have any reason to stay on the existing scheme?
The text was updated successfully, but these errors were encountered: