-
Notifications
You must be signed in to change notification settings - Fork 54
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
custom implementation of MSVC NMAKE #117
Comments
No plans, CMake is great, and Make is great too. You can take a look at this project. |
just to give you a bit of background on the reason for the request. i've used llvm-mingw https://github.com/mstorsjo/llvm-mingw to cross compile llvm-msvc to armv7 -nvidia tegra arm32 microsoft surface rt 1/2. in order to have a msvc compatible compiler on windows 10 arm32, since microsoft never released vs for this platform. using codeblocks port as an ide, it can be configured for a vs 2010 profile, but this profile expects the use of nmake to build. using x86node (x86 emulator) microsoft nmake runs fine. using the windows 10 sdk files imported into the built llvm-msvc include/lib folders, using clang-cl and lld-link, llvm-msvc toolchain successfully compiles win32gui applications targeting the armv7 architecture using the msvc command line arguments that codeblocks ide sends it. llvm-msvc has been very useful in this regard. the ultimate goal here is to be able to produce msvc compatible libraries compiled on the armv7 hardware. that then can be used in vs to cross compile llvm. since llvm itself has a load of msvc related errors when cross compiling with the msvc toolchain for arm32, errors that clang doesn't have. - llvm/llvm-project#49261 |
I understand your needs, but this is relatively niche, and there are currently no plans for it. In this AI era, you can ask GPT, Claude, or Gemini to help you solve your problem. I will not close this issue and will wait for other people or AI agent to fix it. |
any plans to build a replacement for msvc nmake ?
The text was updated successfully, but these errors were encountered: