<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/12/14 16:19, J S wrote:<br>
</div>
<blockquote cite="mid:BAY178-W44B8B9CA72A80B3A094E11E5560@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">I have two lazarus installations.<br>
<br>
</div>
</blockquote>
...<br>
<blockquote cite="mid:BAY178-W44B8B9CA72A80B3A094E11E5560@phx.gbl"
type="cite">
<div dir="ltr">In my cursory examination, it appears that lazarus
looks in a hardwired directory for configuration information.</div>
</blockquote>
<br>
It does, but it can be configured different.<br>
<br>
Depending on the OS it follows the conventions used on that OS. That
is usually in the user folder<br>
Linux: /home/USER/.lazarus<br>
And on Win in the appdir local of the current user.<br>
<br>
Lazarus does not save [1] into the installation folder (as OS
dependent this can be read only). But it checks for a lazarus.cfg
file (search wiki) and appends options found inside to the
commandline options. So you can specify in that file:<br>
--primary-config-path=xxx<br>
<br>
[1] if writeable and lazarus is rebuild it may place the new exe
there. If not, then startlazarus will find it. In that case you need
to try out where to put the above config file.<br>
</body>
</html>