>> I didn't manage to think up anything better than that :-)
> Google for dsp2mak and/or dsp2make.
Well.
The good ol' gawk script dsw2mak is useless here, because:
1. it converts from VS6 solution files, not VS7,
There is a converter VS7 -> VS6 of solution files, called prjconverter
(http://www.c
ontrol we used slm (pronounced slime).
Not sure where that came from. I believe they are using SourceDepot now
which I hear is a port of Perforce.
Thanks,
Nick
From: Krzysztof Nosek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
CC: make-w32@gnu.org
Subject: Re: Don't s
Quoting Krzysztof Nosek <[EMAIL PROTECTED]>:
I didn't manage to think up anything better than that :-)
Google for dsp2mak and/or dsp2make.
Earnie Boyd
http://shop.siebunlimited.com
___
Make-w32 mailing list
Make-w32@gnu.org
http://lists.gnu.or
Eli Zaretskii wrote:
Okay, but then why invoke devenv from Make?
Hmm, I don't quite follow. Suppose I have large heterogenous project (I do
have), which I want to build with make, due to its numerous features and
abilities. However, the project includes several so
> Date: Mon, 11 Sep 2006 17:13:09 +0200
> From: Krzysztof Nosek <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> >> So, these VS files contain (mostly) all information concerning build
> >> issues of
> >> given solution. But it's only devenv who knows how to deal with it.
> >
> > Okay, but then wh
>> of course calling cl.exe, link.exe and all the stuff directly _is_ an option.
>> But, sometimes, when you use such tool as Visual Studio, you want to have
>> projects (.vcproj) and solution files (.sln) configured so that you can
>> build-on-request during development from inside the VS's IDE (o
; Sent: Friday, September 08, 2006 9:28 AM
> To: Krzysztof Nosek
> Cc: [EMAIL PROTECTED]; make-w32@gnu.org
> Subject: Re: Don't see any output to stdout from commands
>
>
> > Date: Fri, 08 Sep 2006 10:34:46 +0200
> > From: Krzysztof Nosek <[EMAIL PROTECTED]>
> Date: Fri, 08 Sep 2006 10:34:46 +0200
> From: Krzysztof Nosek <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> of course calling cl.exe, link.exe and all the stuff directly _is_ an option.
> But, sometimes, when you use such tool as Visual Studio, you want to have
> projects (.vcproj) and solution
> Why does one need to use devenv, anyway? Why not invoke cl.exe
> directly?
Eli,
of course calling cl.exe, link.exe and all the stuff directly _is_ an option.
But, sometimes, when you use such tool as Visual Studio, you want to have
projects (.vcproj) and solution files (.sln) configured so tha
> Date: Thu, 07 Sep 2006 09:40:01 +0200
> From: Krzysztof Nosek <[EMAIL PROTECTED]>
>
> That's definitely not GNU make's fault but MS devenv's. This problem is
> commonly known issue among all those who ever faced building MS Visual Studio
> projects from the command line environment, be it GNU ma
ek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], make-w32@gnu.org
Subject: Re: Don't see any output to stdout from commands
Date: Thu, 07 Sep 2006 09:40:01 +0200
> [...]
> I've just started using GNU make on my Windows machine. Previously I was
> using nmake. The one problem
> [...]
> I've just started using GNU make on my Windows machine. Previously I was
> using nmake. The one problem I noticed thus far is that I don't see any
> output from the commands. For the most part all the commands are the same,
> namely I run devenv.exe to compile a VS.NET project file. Unde
> From: "Nicholas Duane" <[EMAIL PROTECTED]>
> Date: Wed, 06 Sep 2006 07:55:15 -0400
>
> Resending after joining. I was not a member and I think the mail was
> getting discarded.
It shouldn't have been discarded: this list is moderated by humans,
and a message with a subject such as above would
13 matches
Mail list logo