Microsoft KB Archive/168387: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 12: Line 12:
<div id="TitleRow">
<div id="TitleRow">


= <span id="KB168387"></span>FIX: Exported Makefile May Be Useless if Custom Build Uses &quot;CD&quot; =
= <span id="KB168387"></span>FIX: Exported Makefile May Be Useless if Custom Build Uses "CD" =




Line 45: Line 45:
== SYMPTOMS ==
== SYMPTOMS ==


If a custom build step uses the command &quot;CD,&quot; the exported makefile does not work.
If a custom build step uses the command "CD," the exported makefile does not work.


</div>
</div>
Line 52: Line 52:
== CAUSE ==
== CAUSE ==


Makefiles are exported assuming that file paths are relative to the directory with the project file. If a custom build step changes the current directory, the relative file names will not be valid. Developer Studio does not automatically insert a &quot;CD&quot; command to change back to the directory containing the project file after a custom build rule.
Makefiles are exported assuming that file paths are relative to the directory with the project file. If a custom build step changes the current directory, the relative file names will not be valid. Developer Studio does not automatically insert a "CD" command to change back to the directory containing the project file after a custom build rule.


</div>
</div>

Latest revision as of 11:03, 21 July 2020

Knowledge Base


FIX: Exported Makefile May Be Useless if Custom Build Uses "CD"

Article ID: 168387

Article Last Modified on 10/17/2003



APPLIES TO

  • Microsoft Visual C++ 5.0 Enterprise Edition
  • Microsoft Visual C++ 5.0 Professional Edition



This article was previously published under Q168387

SYMPTOMS

If a custom build step uses the command "CD," the exported makefile does not work.

CAUSE

Makefiles are exported assuming that file paths are relative to the directory with the project file. If a custom build step changes the current directory, the relative file names will not be valid. Developer Studio does not automatically insert a "CD" command to change back to the directory containing the project file after a custom build rule.

RESOLUTION

If you need to change the current directory in a custom build step and use an exported makefile, make sure that you change the current directory back to the project directory.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Visual C++, version 6.0.


Additional query words: nmake

Keywords: kbbug kbfix kbide kbvc600fix KB168387