<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 24/03/2016 20:36, Aradeonas wrote:<br>
</div>
<blockquote
cite="mid:1458851800.1261536.558968114.3D4DB878@webmail.messagingengine.com"
type="cite">
<title></title>
<div>Aha!<br>
</div>
<div>If found the problem!<br>
</div>
<div> </div>
<div>I have a config folder in my Lazarus directory that has every
config xml files like default Lazarus have in Appdata.<br>
</div>
<div>When I open Lazarus forms shortcut like I said there was no
problem but when I add that path to cfg it has problem until I
changed the address to this : <span class="highlight"
style="background-color:rgb(255, 255, 255)"><span
class="colour" style="color:rgb(31, 31, 31)"><span
class="font" style="font-family:'Helvetica Neue', arial,
sans-serif"><span class="size" style="font-size:13px">--primary-config-path=C:\Trunk\lazarus\config
and now it solved and no problem.</span></span></span></span><br>
</div>
</blockquote>
What did you use before? --pcp? If that works on commandline but not
in .cfg, then report a bug please.<br>
<blockquote
cite="mid:1458851800.1261536.558968114.3D4DB878@webmail.messagingengine.com"
type="cite">
<div> </div>
<div>But Im still curios about how GetLazarus version works
without a cfg file and it will be very good if any one can check
that.<br>
</div>
<div> <br>
</div>
</blockquote>
<br>
You need to ask them.<br>
<br>
Just to understand, you can download getlazarus, install the same
version into 2 different folders, and run them and they have
separate config?<br>
<br>
Maybe they changed the code to use a folder inside the install dir?
<br>
The problem with the install dir is that on Linux you can not always
find it easily. E.g. if the lazarus exe is linked (hard linked) to
another location. (In that case the lazarus.cfg can not be found
either). On Windows that is on problem.<br>
<br>
Lazarus stores the config files by default in the location that is
typical for the OS (each OS has guidelines for that). Storing inside
the exe folder is against that rules. It can cause problems if:<br>
- the install folder is read only to the user (the lazarus.cfg file
is part of the install, it does not get changed by lazarus, so no
problem)<br>
- the folder can not be found, because the exe is outside the folder
(hard link on linux). In this case lazarus.cfg will not work either,
but at least a normal install will still work. lazarus.cfg is
optional.<br>
<br>
If the folder can not be found, lazarus will find the install
folder, once it has the config, because the config contains the
location where the lazarus sources are installed.<br>
(Obviously if you get the install folder only from the config, then
it is to late for --pcp)<br>
<br>
And yes an install folder can be write protected (default on many
linux installs), if you rebuild the IDE, then all the new ppu files
are created inside the config folder.<br>
<br>
So there are good reasons why Lazarus does it the way it does.<br>
<br>
</body>
</html>