> However, if I were to hazard a guess, I would surmise that the build machines
> have the path you indicate at the root of the drive they run the build from
(C: > perhaps?). You might
That was the problem. On the server there was a c:\usr\local\build directory,
on my system I mounted directori
On 08/06/2009 12:45 PM, Jake wrote:
Yes, we are using the cygwin make. Our builds all normally happen on unix and
using cygwin works better than wine. On the machines it works on it's sending
stuff like:
cl.exe /I/usr/local/build/release/include
On my system cl.exe doesn't even pick up the /I
On Thu, Aug 06, 2009 at 04:45:24PM +, Jake wrote:
>Larry Hall (Cygwin cygwin.com> writes:
>
>> I'm going to assume you sent this here because you're using a Cygwin version
>> of 'make'. It really doesn't sound like you're using Cygwin in a way it
>> was intended. You are probably better off
Larry Hall (Cygwin cygwin.com> writes:
> I'm going to assume you sent this here because you're using a Cygwin version
> of 'make'. It really doesn't sound like you're using Cygwin in a way it
> was intended. You are probably better off looking at Mingw or some other
> native port of 'make'. St
On 08/05/2009 10:49 PM, Jake wrote:
So we are using regular make files to invoke the ms compiler. I get correct
behavior on the build servers, but not my local system. The compiler isn't
picking up the includes we send it on my system. We use a mount -f -s -b and
that seems to clear up the pos
So we are using regular make files to invoke the ms compiler. I get correct
behavior on the build servers, but not my local system. The compiler isn't
picking up the includes we send it on my system. We use a mount -f -s -b and
that seems to clear up the posix to win32 path issue on the build se
6 matches
Mail list logo
