Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: "Suhaib M. Siddiqi" To: Subject: Re: Using Visual C++ under Cygwin build system Date: Mon, 9 Oct 2000 20:39:06 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal This is a bit late, but might be of interest to you and others. From OpenDx CVS at http://www.research.ibm.com/dx get dx/windows directory. Greg, one of the IBM's OpenDX developer, wrote some wrapers, which could allow you to use MSVC from Cygwin bash shell, and execute GNU configure scripts to generate Makefiles. The wrappers uses MSVC, instead of GCC. Suhaib -------------------------------------------------------- --- Chad Loder wrote: > Hello. I am developing a build system using Cygwin (GNU make, bash, > etc.) on Windows 2000. > You might just want to use automake, autoconf and libtool. AFAIK, they are supporting VC++ syntax. > 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. > You should be able to use c:/foo/bar.c as a path name. You may also want to check the -win32 switch to the make command. Cheers, ===== Earnie Boyd mailto:earnie_boyd@yahoo.com --- --- --- Cygwin: POSIX on Windows --- --- Minimalist GNU for Windows --- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com