I'm trying to compile a Perl source and I can't seem to find a version of nmake that works with Windows 7 64 bit. I've searched all over Microsoft's website and my Googlefu seems to be failing me. Can I use a different compiler- if so suggestions/resources? I'm a native Linux user so pardon my ignorance
To get the 64 bit version of nmake (for Windows 7) you can also install the Windows SDK. It will install nmake.exe to C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin on Windows 7 without prompting for an alternate directory.
You can use chocolatey to install the Visual Studio build tools, or you can just install them yourself from MS downloads. But the critical step is start a cmd shell running the appropriate script so you get nmake in your path.
I went to look for nmake, but I found that provided links to Microsoft download were broken, and that it seems that you have to install some very large package of software to get it. And I am not sure which package.
Based on the info in your post, I'm going to assume that you are using ActiveState's ActivePerl. If you are using the 32-bit version, just use PPM to install MinGW and dmake from ActiveState's repository. Once those are installed, you can then install modules directly from CPAN.
MinGW and dmake are already showing as installed in PPM.[reply]Re: using dmake instead of nmake on Windows
by syphilis (Archbishop) on Oct 06, 2012 at 02:52 UTCIs there some way to force CPAN to use dmake instead?
Specifying MAKE at the 'perl Makefile.PL' step should achieve that:perl Makefile.PL MAKE=dmake[download]Cheers,
Rob[reply]
[d/l]Re: using dmake instead of nmake on Windows
by Anonymous Monk on Oct 05, 2012 at 21:00 UTC It uses perl -V:make by default, but if you install MinGW it ought to try to run dmake ppm install MinGW dmakecpan Net::POP3[download] To force the issue you'd run perl Makefile.PL make=dmake[download] You can configure cpan/cpanp ... see PERL_MM_OPT, PERL_MB_OPT[reply]
[d/l]
[select]Re^2: using dmake instead of nmake on Windows
by fourmajor (Initiate) on Oct 06, 2012 at 14:33 UTCperl Makefile.PL make=dmake
followed by make install did the trick. Thanks![reply]Re: using dmake instead of nmake on Windows
by bulk88 (Priest) on Oct 06, 2012 at 01:09 UTCDownload a copy of the free Platform SDK for a modern MS C compiler and nmake.[reply]Re: using dmake instead of nmake on Windows
by exilepanda (Friar) on Oct 06, 2012 at 08:49 UTCWhich Perl you're using? I can see that my Net::POP3 is located at /lib/, but not /site/lib/ so I think this is bundled when you install Perl at the first place.And what do you mean not available? And are you using ppm GUI or command line? and what errors you've got ?[reply]Back toSeekers of Perl Wisdom
Thanks for your reply. Yes I did try the installer, however it seems not installying the dependencies to the system Python. Im trying to do it on system python so i can be used alongside other python packages we need.
The error you're encountering when trying to install depthai on a Windows machine indicates a problem with CMake being able to invoke nmake. Here are several steps you can take to troubleshoot and resolve this issue:
Visual Studio Build Tools: Ensure that you have the Visual Studio Build Tools installed. nmake is part of these build tools, which are required for compiling C++ code on Windows. It's not sufficient to have just CMake; you need the build tools that CMake will call to compile the code.
Windows SDK: The Windows SDK may indeed be necessary because it includes the compilers and libraries needed to build C++ applications. While it is large, it is often a required component for building native extensions.
I have tried the Windows installer again, the version it carries is quite old, which is v2.20.2, now the latest should be v2.23. I couldn't use it properly for some features as it is dated. Could the team help update the installer quickly.
Hi Huimin
The installer should install 2.21.2.0 version as specified in the requirements.txt. You can edit that one with 2.23.0 to install the newest version.
We currently use 2.21.2 since it's been tested and is less prone to issues - which is better for new users.
Hello,
I have the same issue. The demo works if I use the installer, but I cannot install the library to run my custom application. I have installed the Visual Studio Build Tools. That did not help. I'm a bit hesitant to install Windows SDK as well. Would you still recommend to try that?
Note that the build script might fail if the build directory exists but was not created with the appropriate files by running cmake. Can you try deleting the entire build directory, reverting nmake.bat to the version in the repository, and running it again? (But really this whole discussion should be moved to the github issue tracker.)
I need to be able to compile 7-zip, but I am having a lot of issues. I have MS Visual C++ 2010 Express with the latest Windows SDK. I created a new project based on existing files and brought in all of the C++ files. First there were a number of issues with the compiler not finding the includes, so I altered the paths and that is not an issue now, except for a couple header files that I cannot find at all. But there are so many errors that it won't finish compiling. I looked for a readme file, or some link that states how to compile, but I didn't find anything. I'm not sure what I am doing wrong - any assistance would be greatly appreciated!
I get errors if I try to compile just the dll as well. Is there any documentation or another post on how to compile the whole application? I would prefer command line, but I can import it into the IDE as well.
you don't need visual studio to compile, just download windows sdk 7.1 and install it with all options checked, download 7zip source and extract it, make sure that there is no space in path to extracted source.
then run from start->all programs->Microsoft Windows SDK v7.1->Windows SDK 7.1 Command Prompt
in this command prompt browse to extracted_source\CPP\7zip and type "nmake NEW_COMPILER=1 MY_STATIC_LINK=1" and press enter, everything will be compiled
exe and dll files will be in folders named "O" in projects folders (for example 7zfm.exe will be in CPP\7zip\UI\FileManager\O )
Hello @mpaladin,
Thanks for reply. Yes was full content.
BTW issue is resolved when analyse logs it was not working with TCC prompt but when I launch in windows command prompt build-wrapper had completed successfully .
I extracted that archive into a fresh directory, started the specialized shell,"x64 Native Tools Command Prompt for VS 2022", (via a Start menu shortcut left by the VS 2022 installation), navigated to that fresh directory, and ran "nmake /f Makefile.msc PLATFORM=x64" with no error output and got build products per the default make target.
The effect of running the batch files which get that specialized shell setup is limited to setting the environment. So by examining that, it should be possible to figure out how your pre-build preparation is going awry.
c80f0f1006