[lazarus] New Install for Win32 FreePascal
Michael A. Hess
mhess at miraclec.com
Fri Jul 16 17:10:42 EDT 1999
michael at tfdec1.fys.kuleuven.ac.be wrote:
>
> If the linker doesn't support it, the compiler can generate what it
> wants, if the linker doesn't eat it, you're stuck.
If you look at the sample link.res I included before the first couple of
lines are correct it is just the 5th one I think that use the long name.
If the compiler would create that as "progra~1" instead of "program
files" then it links correctly. I manually changed it and everything
linked correctly.
> If you touch autoexec.bat to accomplish this, it won't work on NT.
> (- just a reminder, I have experience with weird setups :( -)
Touch in what way??? All I am doing is adding a directory to the PATH
environment variable. Doesn't NT use this?
> The problem is not FPC, it doesn't mind spaces.
I don't know how FPC GOT the spaces. Everything that was passed to it in
the .cfg and by command line used the short file name (progra~1). This
had to be something that the compiler generates and adds on its own.
> the problem is the linker.
Of this I am fully aware. It is just that the link.res commands for the
linker need to be generated correctly.
> I will see what I can do. Normally, putting a \ in front of a space
> should do the trick. Could you test that please ? I am not under NT at
> the moment, and won't be accessing it till monday. If you test it, I
> can apply a fix tonight !
I'm downloading the files from Cliffs site again to build another
install here in my office and I give it a try at that time. I don't
understand though how a "\" in front of the space helps. Won't the
linker assume that is a subdirectory?
--
==== Programming my first best destiny! ====
Michael A. Hess Miracle Concepts, Inc.
mhess at miraclec.com http://www.miraclec.com
More information about the Lazarus
mailing list