BUG: Exported Makefile May Be Useless if Custom Build Uses "CD"Last reviewed: May 21, 1997Article ID: Q168387 |
The information in this article applies to:
SYMPTOMSIf a custom build step uses the command "CD," the exported makefile does not work.
CAUSEMakefiles 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.
RESOLUTIONIf 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.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: nmake
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |