<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-9"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 2010-07-18 11:41, Mattias Gaertner wrote:
<blockquote cite="mid:20100718104145.61778621@limapholos.matom.wg"
type="cite">
<pre wrap="">/usr/lib/fpc/2.4.1/units/i386
Translate this to some windows paths you like and adapt your fpc.cfg.
</pre>
</blockquote>
Quick question. I took a look at 'Installing Lazarus' [
<a class="moz-txt-link-freetext" href="http://wiki.lazarus.freepascal.org/Installing_Lazarus">http://wiki.lazarus.freepascal.org/Installing_Lazarus</a> ] and all the
examples for paths have no spaces in them.<br>
<br>
Indeed, in my fpc.cfg, all paths are spaceless, such as
'c:\Lazarus\fpc\2.4.3/units/$FPCTARGET/'<br>
<br>
There's also a special warning against them in the FAQ: "3. Check if
the compiler <b>installation path has spaces</b> in it. <b>Make
sure it doesn't!</b>" [
<a class="moz-txt-link-freetext" href="http://wiki.lazarus.freepascal.org/Lazarus_Faq#I_can.27t_compile_Lazarus">http://wiki.lazarus.freepascal.org/Lazarus_Faq#I_can.27t_compile_Lazarus</a>
]<br>
<br>
Is there a fundamental (still valid) reason for not being able to
have it something like "c:\Program
Files\Lazarus\fpc\2.4.3/units/$FPCTARGET/" at least under Windows?<br>
<br>
It goes against everything we're accustomed to these days.<br>
<br>
What would it take to remove that limitation, I wonder?<br>
<blockquote cite="mid:20100718104145.61778621@limapholos.matom.wg"
type="cite">
<pre wrap="">Keep in mind that Lazarus and FPC are separate things and that only the
windows installer puts fpc in a sub directory of the lazarus
directory.
</pre>
</blockquote>
OK. I usually do my development under Windows and when I have to
compile on Linux, I install Lazarus/FPC from a package and not worry
about its internals.<br>
<blockquote cite="mid:20100718104145.61778621@limapholos.matom.wg"
type="cite">
<pre wrap="">You can easily use one lazarus with several fpcs and they can share
the same fpc source directory.
</pre>
</blockquote>
I am assuming this is optional. I.e., you can alson opt not to share
a common source directory as well.<br>
<blockquote cite="mid:20100718104145.61778621@limapholos.matom.wg"
type="cite">
<blockquote type="cite">
<pre wrap="">I think the reason why they didn't is because both installations share
the same data folder i.e. C:\Users\$username\AppData\Local\lazarus
Hence, both the x86 and x64 versions share the information stored under
that folder --which screws up things.
A better solution, IMO, would be to use both the patform and version
numbers; so that workdirs become:
C:\Users\$username\AppData\Local\lazarus\0.9.29\win32\2.4.0
C:\Users\$username\AppData\Local\lazarus\0.9.29\win32\2.4.3
C:\Users\$username\AppData\Local\lazarus\0.9.29\win64\2.4.0
C:\Users\$username\AppData\Local\lazarus\0.9.29\win64\2.4.3
etc.
This way, I can have several different versions live under the same
$username.
</pre>
</blockquote>
<pre wrap="">Feel free to do so.
</pre>
</blockquote>
But, that would mean also altering how Lazarus behaves (under
Windows at least). I doubt if I could get past the inertia.<br>
Not knowing who to talk to is immensely discouraging.<br>
<blockquote cite="mid:20100718104145.61778621@limapholos.matom.wg"
type="cite">
<blockquote type="cite">
<pre wrap="">One more thing: Lazarus, when uninstalled, removes neither its install
folder, nor its workdir; which it should.
</pre>
</blockquote>
<pre wrap="">
I don't know the internals of the windows installer.
Maybe Vincent knows.
</pre>
</blockquote>
My ideal installer would also be able to download only the sources
and build them locally --instead of downloading a much bigger binary
package.<br>
<br>
I wonder if this would be possible. or even generally desirable.<br>
</body>
</html>