On 2/20/06, Vin Shelton <acs(a)xemacs.org> wrote:
On 2/20/06, Michael Sperber
<sperber(a)informatik.uni-tuebingen.de> wrote:
> Yeah, but it seems you're compiling your own private package path into
> the executable, which might surprise users. (And via the now obsolete
> package-path setting, too.) Is that necessary?
That just comes for free. :-) Take a look at nt/config.inc.samp for
a configuration file for Windows. When one is building on windows,
one copies nt/config.inc.samp into nt/config.inc and makes
modifications.
Michael,
It had never occurred to me to omit PACKAGE_PREFIX from config.inc
when building under Windows. I just did this and the build succeeded,
but according to the Installation file, the executable ended up with a
default value of:
Package path is "~\\.xemacs;;c:\\Program
Files\\XEmacs\\site-packages;c:\\Program
Files\\XEmacs\\xemacs-packages".
Just FYI. It looks like the current windows native configuration code
forces a value for PACKAGE_PREFIX into the build process.
Any thoughts?
Thank you,
Vin