You can try using that file as a starting point for constructing a real Windows makefile, for whichever compiler target you choose. Back before I knew what I was supposed to do, I simply renamed Makefile.in to Makefile and got pretty far. All you have to do is specify the path to the target compilecommands.json file in settings.json, like this: 'pileCommandsPath': '.vscode/compilecommands.
Makefile.in will contain the basics of the final makefile. With this latest release of the Makefile Tools extension, you can generate a compilecommands.json file for your project. Even under Cygwin, you can expect to have to make a few changes to the source code if it hasn’t been written with Windows in mind. In the end, the package you’ve downloaded might not really be compilable on Windows. Makefile.in is one of the inputs to the configure script, which will construct the real makefile and maybe a header or two that are specific to your environment, based on tests that configure runs. Then run nmake.īut if you only have files named Makefile.in and Makefile.am, then you don’t yet have a makable environment. Look for a Visual C++ makefile it’s usually named Makefile.mak.
#IS THERE MAKEFILE FOR WINDOWS HOW TO#
If you just give the file name without -f, then make will interpret it as the target that it should figure out how to make.Ī lot of tools that only come as source assume that you’ll use Visual C++ to build on Windows, even if they assume you’ll use G++ everywhere else.
If the makefile has some other name, use the -f option. If you just type make, it will find that file automatically. The make utility expects to use a file named Makefile.