Using Visual C++ under Cygwin build system

Using Visual C++ under Cygwin build system

[Chad Loder]

Hello. I am developing a build system using Cygwin (GNU make, bash,
etc.) on Windows 2000.

Some of our subsystems must be built using Visual C++. Obviously
Visual C++ will not understand paths like "/c/foo/bar.c" (where
/c is the Cygwin mounted C: drive). However, since GNU make will
be producing targets and processing prerequisites with precisely
those kinds of paths, I foresee problems.

Has anyone dealt with this problem before? Any suggestions
(or examples)?

Thanks,
	Chad


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Using Visual C++ under Cygwin build system

[Matthew Smith]

> Hello. I am developing a build system using Cygwin (GNU make, bash,
> etc.) on Windows 2000.
>
> Some of our subsystems must be built using Visual C++. Obviously
> Visual C++ will not understand paths like "/c/foo/bar.c" (where
> /c is the Cygwin mounted C: drive). However, since GNU make will
> be producing targets and processing prerequisites with precisely
> those kinds of paths, I foresee problems.

Use the 'cygpath' program included with cygwin.  It will convert back and
forth between cygwin and windows paths.  An example of using this in a make
file would be like this:

RES_FILE := $(shell cygpath -w $(OBJ_DIR)/resource.o)

cheers,
-Matt Smith



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Cygpath, backslashes, and sh.exe

[Chad Loder]

Hi all. Thanks for your help with cygpath (I *did* look in 
the FAQ, I just didn't know what to look for). :)

cygpath *seems* to be doing the right thing (it's hard
to tell), but there is some sort of problem with
backslashes. I have a rule like this:

%.obj : %.cpp
	$(CC) $(CPPFLAGS) $(shell cygpath -w $<)

The idea is that this will invoke sh.exe with something like:

 /c/VC98/bin/cl.exe /Fo:globref.obj c:\r7\jni\src\globref.cpp

But instead it seems to do:

 /c/VC98/bin/cl.exe /Fo:globref.obj c:r7jnisrcglobref.cpp

which causes the compiler to bomb out with:

 fatal error C1083: Cannot open source file: 'c:r7jnisrcglobref.cpp': No
such file or  directory

I figured I need to escape the backslashes before passing them
to a shell command. So I tried things like:

%.obj : %.cpp
	$(CC) $(CPPFLAGS) $(subst,\\,\\\\,$(shell cygpath -w $<))

but the subst function seems to just return an empty string (this
happens even when I use something without backslashes,
like $(subst,a,b,whatever).

Has anyone run into this?

Thanks,
	c

	c

At 05:50 PM 10/3/2000 -0500, you wrote:
>Chad:
>
>    Hey, no problem.  Let me know if you run into other problems.  My
>company uses it's own make system under cygwin as well.  We also use Visual
>C++ as the compiler.
>
>cheers,
>-Matt



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Cygpath, backslashes, and sh.exe

[DJ Delorie]

> %.obj : %.cpp
> 	$(CC) $(CPPFLAGS) $(shell cygpath -w $<)

Try this:

%.obj : %.cpp
	$(CC) $(CPPFLAGS) '$(shell cygpath -w $<)'

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Cygpath, backslashes, and sh.exe

[Chad Loder]

That did the trick! Now on to the next problem.

"Is life always this hard, or just when you're
 a kid?" :)

Thanks,
	c	

At 08:56 PM 10/3/2000 -0400, you wrote:
>
>> %.obj : %.cpp
>> 	$(CC) $(CPPFLAGS) $(shell cygpath -w $<)
>
>Try this:
>
>%.obj : %.cpp
>	$(CC) $(CPPFLAGS) '$(shell cygpath -w $<)'
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Cygpath, backslashes, and sh.exe

[Scott Carter]

I don't know if you tried to use it this way, or if you just typed it
incorrectly in your email, but the syntax of the subst function is
incorrect. There should not be a comma immediately after subst.

wrong: $(subst,\\,\\\\,$(shell cygpath -w $<))
right: $(subst \\,\\\\,$(shell cygpath -w $<))

Scott Carter

-----Original Message-----
From: Chad Loder [ mailto:cloder@acm.org ]
Sent: Tuesday, October 03, 2000 06:55 PM
To: cygwin@sourceware.cygnus.com
Subject: Cygpath, backslashes, and sh.exe


Hi all. Thanks for your help with cygpath (I *did* look in 
the FAQ, I just didn't know what to look for). :)

cygpath *seems* to be doing the right thing (it's hard
to tell), but there is some sort of problem with
backslashes. I have a rule like this:

%.obj : %.cpp
	$(CC) $(CPPFLAGS) $(shell cygpath -w $<)

The idea is that this will invoke sh.exe with something like:

 /c/VC98/bin/cl.exe /Fo:globref.obj c:\r7\jni\src\globref.cpp

But instead it seems to do:

 /c/VC98/bin/cl.exe /Fo:globref.obj c:r7jnisrcglobref.cpp

which causes the compiler to bomb out with:

 fatal error C1083: Cannot open source file: 'c:r7jnisrcglobref.cpp': No
such file or  directory

I figured I need to escape the backslashes before passing them
to a shell command. So I tried things like:

%.obj : %.cpp
	$(CC) $(CPPFLAGS) $(subst,\\,\\\\,$(shell cygpath -w $<))

but the subst function seems to just return an empty string (this
happens even when I use something without backslashes,
like $(subst,a,b,whatever).

Has anyone run into this?

Thanks,
	c

	c

At 05:50 PM 10/3/2000 -0500, you wrote:
>Chad:
>
>    Hey, no problem.  Let me know if you run into other problems.  My
>company uses it's own make system under cygwin as well.  We also use Visual
>C++ as the compiler.
>
>cheers,
>-Matt



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com