[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Setting GS_LIB_DEFAULT and other paths on Windows
From: |
John Brown |
Subject: |
Re: Setting GS_LIB_DEFAULT and other paths on Windows |
Date: |
Sat, 26 Jan 2013 10:43:15 -0800 (PST) |
In case anyone is interested in this, I have not solved it yet,
but I now have more insight.
I downloaded the official Windows binary and compared it with mine.
According to strings, the correct internal representation on
Windows is "Full-path1;Full-path2". The difference in display
(
official - %rom%Resource/Init/ ; %rom%lib/ ; c:/gs/gs9.06/Resource/Init ;
c:/gs/gs9.06/lib ; c:/gs/gs9.06/Resource/Font ; c:/gs/fonts
mine - %rom%Resource/Init/ : %rom%lib/ : c :
/mingw/local/share/ghostscript/9.06/Resource/Init;c :
/mingw/local/share/ghostscript/9.06/lib;c :
/mingw/local/share/ghostscript/9.06/Resource/Font;c :
/mingw/local/share/ghostscript/fonts;C : /Windows/Fonts
)
with a gap between the drive letter and the colon (:) seems
to be because of const char gp_file_name_list_separator, which
is defined a ';' or ':' depending on the platform-specific
file that is selected.
It seems that the unix files such as base/gp_unix.c and
base/gp_unifs.c are linked into the executable. Is there a
simple way to replace these with the appropriate files for
Windows? In Makefile.in, I see:
include $(GLSRCDIR)/unixhead.mak
...
include $(GLSRCDIR)/unix-aux.mak
include $(GLSRCDIR)/unixlink.mak
include $(GLSRCDIR)/unix-dll.mak
include $(GLSRCDIR)/unix-end.mak
include $(GLSRCDIR)/unixinst.mak
Does a corresponding set of Windows files exist, or
would I have to create them?
Regards,
John Brown.