View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001464

CMake

public

2005-01-10 18:35

2005-01-28 09:08

Reporter

Chris Scharver

Assigned To

Bill Hoffman

Priority

low

Severity

minor

Reproducibility

always

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001464: nmake doesn't specify full 'link.exe' path

Description

I have encountered a problem using nmake with Visual Studio 7 .NET 2003 and cygwin. I typically do everything in cygwin since, well, I need bash rather than the DOS shell. I just upgraded to VS7, and I noticed that I'm having problems with nmake not specifying the path to link.exe. This causes a unique problem since cygwin sets the PATH such that /usr/bin/link.exe is picked up. Relying on the order of entries within the PATH variable might be risky. Perhaps the nmake generator should encode the full path to the link command within the Makefile?

Tags

No tags attached.

Attached Files

Relationships

Notes
(0001916) Bill Hoffman (manager) 2005-01-13 13:27	It is assumed when cmake is run that the compiler environment is correct for running the c/c++ compiler from the command line. There are many other environment variables required to run cl from the command line correctly. MS provides a shell to do this, so using a full path for one of the components would not really fix the problem.

(0001947) Chris Scharver (reporter) 2005-01-17 12:53	Okay, it looks like I will jsut have to dig into the path setups a bit more. Tracking down all the required changes between VS6 and VS.NET just creates some headaches I was hoping to avoid. Thanks for the feedback.

(0001985) Bill Hoffman (manager) 2005-01-28 09:08	Please see the discussion on the cygwin mailing list: or google link.exe cygwin http://sources.redhat.com/ml/cygwin/2005-01/msg00134.html [^]

Issue History
Date Modified	Username	Field	Change