Using MSVC++ 4.0 Command Line tools to compile in emacs

Frederic Corne frederic.corne@erli.fr
Mon Jul 7 23:50:00 GMT 1997


arifi_koseoglu@karmaint.com writes:

>      Hi!
>      
>      I am using the Cygnus Win32 Emacs distribution and first of all, wish 
>      to thank everybody who put a bit of work into it with all my heart !
>      
>      Here at work it is almost mandatory to use MSVC++ for development, but 
>      after five years of working with gnu tools under Unix I just detest 
>      the idea. What I am trying to do is to keep the project structure only 
>      in teh MSVC environment, use it to generate a Makefile, and then use 
>      this Makefile to compile from within emacs using the command-line 
>      compiler etc.
>      
>      Now, I have tried to use the ProjectName.mak file as the makefile, but 
>      does not really seem to work - or at least nmake does not like being 
>      fed this file as a Makefile. What do I need to do ?

MSDEV use its internal nmake which differ from nmake.exe in some points. So
a makefile generated by MSDEV don't always works with nmake.exe ... (in
particular with c++)

>      I cannot create a 
>      custom Makefile from scratch because people insist in letting MSVC++ 
>      do all of parameter handling etc. They would not accept my manually 
>      edited makefile.

Show them that MSDEV store the letter of the drive in the project space,
thus a file  which is on a disk  on the network mounted as drive K: must
always be on drive K:  

It is stupid. 

cl.exe and nmake.exe accept network drive as \\host\foo\bar ... so there are
not problems with makefiles "hand-made".


FC

-- 

--- Frederic Corne --- ERLI --- frederic.corne@erli.fr ---

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".



More information about the Cygwin mailing list