Quickfix and Visual Studio and cygwin

Previous Tip • Next Tip

Tip: #345 - Quickfix and Visual Studio and cygwin

Created: October 15, 2002 15:13 Complexity: basic Author: Brian K Version: 5.7 Karma: 2/2 Imported from: Tip#345

I run gvim inside a cygwin XFree86 session running WindowMaker. Because I'm inside cygwin-XFree86, I can't use the useful VisVim plugin to step through Visual Studio compiler errors. To work around this limitation, I wrote a Bash/Perl script that munges nmake output into something that has cygwin compliant path and is parseable by the default quickfix errorformat setting .

Here's what to do:

1. install the following from cygwin:

• perl
• cygutils
• bash

2. Set up Visual Studio to support command line compiles. Basically this involves adding paths to the PATH, INCLUDE, and LIB environment variables. See vcvars32.bat in the Visual Studio VC98/bin directory for guidelines.

3. Export a makefile for your dsp project file via the Visual Studio "Project - Export Makefile..."

4. Create the cygwin shell script defined below. Put the script in '/bin/dovcmake'

---begin cut-----

#!/bin/bash 
# This script takes output from 
# Visual Studio's nmake and reformats 
# it so that it can be parsed by 
# cygwin's vim default errorformat 
# setting 
nmake /F $1 2>&1

Comments

You should look at the errorformat variable. This may solve your problem without perl.

Anonymous , October 16, 2002 1:09

---

I needed to use perl because I needed to convert windows paths from nmake's output to cygwin paths. Otherwise I would have used errorformat

Brian K , October 16, 2002 13:47

---

You could use Cygwin's cygpath to translate between Cygwin (posix) and windows paths instead of Perl.

Anonymous , December 2, 2002 6:54

---

I am using cygpath within the perl script to translate the paths, but the perl script does more that just translate paths. It also filters extraneous nmake output , such as the MS copyright info that nmake generates.

Brian K , December 3, 2002 11:21

---

Instead of using cygpath, you may want to look at whether cyg-wrapper.sh will help you. It handles a lot of the tricky path conversion issues between cygwin and Windows.

--> http://hermitte.free.fr/cygwin/#Win32

Anonymous , October 21, 2004 17:21

---