-
Notifications
You must be signed in to change notification settings - Fork 20
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
Wrong directory name when building for VisualStudio #274
Comments
Try and use the x86 Native Tools Command Prompt for VS2022 from the Start Menu to build from source. |
I used x86 Native Tools Command prompt for VS 2022 and this is what I got :
|
I tried to build admb with this branch and it worked much better. All objects are created well but one last problem remains:
Link was set on admb-win32-cl19.lib but in my "build/lib" directory I have admb-win32-cl.lib (and also admbo-win32-cl.lib, admb-contrib-win32-cl.lib, admb-contribo-win32-cl.lib). |
getting closer…, but there should be a admb-win32-cl19.lib in the build/admb/lib directory. can you rebuild?
then send output of the first 5 calls to cl.exe. also, can you send display output of just using the cl.exe compiler in the command prompt?
??? |
cl.exe compiler:
5 first calls to cl.exe:
|
Okay, please update the dev-13.1 branch, then clean and rebuild it again. |
Thanks, it works perfectly on my side. |
Thanks Jules (@Ash12H) for helping with testing. I am glad it finally works for you. Cheers... |
I tried to build the lattest version of ADMB (13.0) on Windows and an error occured. An object could not be found after the first call to Microsoft compilator (cl version 19.33.31630).
The reason was that the directory used to store the objects was named "win32-cl" instead of "vs-cl". The same error occurred for the
nmake DEBUG=yes
call.After creating
vs-cl
andvs-cl-debug
manually, the installation went through without error.Is it a problem due to a bad manipulation on my part, or an error in the installation process?
Thanks,
Jules
Edit :
I discovered that not all makefiles define OSNAME and CXXVERSION in the same way. finally, I forced the makefiles to define the constants this way:
And the whole construction process was completed correctly.
I forgot to mention that I use Visual Studio 2022 on Windows 10 and cl.exe in version 19.33.31630 for x86.
The text was updated successfully, but these errors were encountered: