Hi, I only have msvc4.0. It can't load the output of msvcmaker.
I suppose I should buy current msvc, or modify msvcmaker myself to output a makefile instead of a project file.
That's an idea... has anyone tried building the conformance tests with cl (i.e. microsoft's compiler's commandline interface)? - Dan
On January 4, 2003 02:12 pm, Dan Kegel wrote:
I suppose I should buy current msvc, or modify msvcmaker myself to output a makefile instead of a project file.
There is a request somewhere (and IIRC Patrik said he'll look into it when he gets a chance) for instrumenting winemaker to convert .dsp files into Makefiles, which is what you want, no? But when will this happen -- I don't know :)
Dimitrie O. Paun wrote:
On January 4, 2003 02:12 pm, Dan Kegel wrote:
I suppose I should buy current msvc, or modify msvcmaker myself to output a makefile instead of a project file.
There is a request somewhere (and IIRC Patrik said he'll look into it when he gets a chance) for instrumenting winemaker to convert .dsp files into Makefiles, which is what you want, no? But when will this happen -- I don't know :)
Since I don't need the .dsp at all, may as well directly create the Makefile... whether a .dsp is also generated doesn't matter for msvc4 users (all three of us).
On Sun, 5 Jan 2003, Dimitrie O. Paun wrote: [...]
There is a request somewhere (and IIRC Patrik said he'll look into it when he gets a chance) for instrumenting winemaker to convert .dsp files into Makefiles, which is what you want, no? But when will this happen -- I don't know :)
The goal of winemaker would be to take a .dsp and generate a Winelib makefile, not an MSVC40 makefile. The two are completely different and incompatible. So thie would not help.