Bug 690989 - gs can't compile with MSVC when SYSDRIVE != c:
Summary: gs can't compile with MSVC when SYSDRIVE != c:
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Build Process (show other bugs)
Version: 0.00
Hardware: PC Windows NT
: P4 normal
Assignee: Robin Watts
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-13 07:09 UTC by Leonardo
Modified: 2020-12-27 19:18 UTC (History)
2 users (show)

See Also:
Customer:
Word Size: ---

Attachments
msvc32.mak (24.56 KB, text/plain)
2009-12-13 07:13 UTC, Leonardo 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo 2009-12-13 07:09:07 UTC 
gs/psi/msvc32.mak hardcodes C:, so it can't find the build tools when Windows 
is installed to another drive. Tested with Vista, but imho it's true for any 
Windows version and any MSVC version.
Comment 1 Leonardo 2009-12-13 07:13:22 UTC 
Created attachment 5763 [details]
msvc32.mak

A suggested changed mak file against gs8_70. Sorry I have no proper diff nor
HEAD here.
Comment 2 Hin-Tak Leung 2010-01-17 16:45:41 UTC 
The submitted mak file is quite wrong. The correct solution should auto-detect
the location of the microsoft dev tools from the variables its installation sets
(such as MSSDK). See my comments in:
http://bugs.ghostscript.com/show_bug.cgi?id=691062

Perhaps it is more useful to the discussion if the reporter actually posts what
variables his installation sets. (just type "set" in the dev tool prompt).
Comment 3 Robin Watts 2010-01-28 17:24:35 UTC 
Reassigning to new email address.
Comment 4 Peter Cherepanov 2020-12-27 19:18:04 UTC 
Current build system for MS Windows works just fine.