-
Notifications
You must be signed in to change notification settings - Fork 765
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
Remove nmake build system #1137
Conversation
|
I tried to do something similar a week ago but never pushed the changes because I realized that our CMake setup can't produce a drop-in replacement for NMake. As far as I can tell from this PR it will also be the case here. I am okay with merging this but we need to make sure that we have a setup that is as close to being a drop-in replacement for users relying on NMake builds. |
|
What is the issue exactly with the cmake build ? |
I failed to create a NMake generator that would output a DLL. I think we need the |
|
How did you configure to build DLL? Have you set https://cmake.org/cmake/help/latest/variable/BUILD_SHARED_LIBS.html |
I didn't do any changes to the CMake files, I just ran a |
|
Typically, to build shared library it takes |
|
There's a dedicated -DBUILD_LIBPROJ_SHARED=ON switch which is used by appveyor.yml to test DLL builds |
|
Maybe things aren't as bad as I thought. I'm probably not the only one who can't find their way around this stuff so maybe we should add something to the install/build instructions on how to do this. |
Any reason to not to switch over to the official variable? I think less custom variables/options the better, self-descriptive, knowledge-transitive setup. |
|
Okay, so to follow up on this, here's what I did in my previous test: which after compilation doesn't createa DLL. Running cmake with |
This was announced as scheduled for PROJ 6.
My ongoing work on the iso19111 branch hasn't updated the makefile.vc stuff and only supports cmake builds for Windows