Adrian Aichner wrote:
Matthew> COMPLETE! But who the hell screwed up the references to
Matthew, don't you think you're a bit offensive in your choice of
language?
Yep. uncalled for. I think someone else complained about same thing with
less offensiveness a week earlier.
What is your current directory when you run
nmake ... -f ...xemacs.mak?
nt subdirectory
What is the exact command line you use?
nmake install -f xemacs.mak
Matthew> i.exe? How difficult could it be to replace
Matthew> XEMACS=.. with the real damn path so that no references
Matthew> are relative and dependent on where you've cd'ed to?
Too difficult for you to send a patch, maybe?
Ohh, I must have been in a seriously bad mood that night, but for other
reasons. Time to start saving to draft and re-reading the next day
before hitting the send button.
Actually, I was thinking that a patch would be either:
1)The config script has a macro FULL_XEMACS_SRC path
2)Have the makefile figure it out.
One problem I'm having is trying to figure out the equivilent of 'pwd'
in NT or how to fake it.
The true crux of the problem is that you need to quote programs with
spaces in the name or path. When the macro $(FOO) is "..\With
Space\i.exe", then adding judicical ..\ (like so: ..\$(FOO)) won't
work; you get ..\"..\With Space\i.exe".
Come to think of it, FULL_XEMACS_SRC may not work either. If the
definition is like "C:\With Spaces\xemacs". then you have the same
problem adding subdirs to the front as adding ..\ to the rear - they get
added outside the quotes.
So, to answer my own question, it can be very difficult to replace
XEMACS=..
Any one have any crow? Or an old hat they don't need? I just got rather
hungry.
:=(
--
Matthew O. Persico
"If you were supposed to understand it,
we wouldn't call it code." - FedEx
____________NetZero Free Internet Access and Email_________
Download Now
http://www.netzero.net/download/index.html
Request a CDROM 1-800-333-3633
___________________________________________________________