<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 15/03/12 13:43, Mattias Gaertner wrote:
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<p style="margin: 0px;">You can use macros in the IDE options. For
example:</p>
<p style="margin: 0px;">export FPC_VER=2.6.1 && ./lazarus</p>
<p style="margin: 0px;">Then you can use the macro $ENV(FPC_VER)
in IDE options. <br>
</p>
</blockquote>
+1<br>
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite"> For relaunching use startlazarus:
<p style="margin: 0px;">/home/me/Programs/lazarus/lazarus-svn/startlazarus
--pcp="/home/me/Programs/lazarus/config-lazarus-svn"</p>
</blockquote>
My bad! It relaunches fine now.<br>
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">Normally you set the compiler path to the fpc
executable.
<p style="margin: 0px;">The IDE will then get the fpc version from
it. So you can use the IDE's FPCVer macro. For example you can
use this macro in the FPC sources directory.</p>
<p style="margin: 0px;">Changing the compiler will automatically
switch the FPC sources.</p>
<p style="margin: 0px;">Changing the target OS of the project
automatically switches compiler and FPC sources. <br>
</p>
</blockquote>
+1.<br>
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> The compiler path of the IDE has already
a history drop down list. <br>
</p>
</blockquote>
I'll stick for the time being to the script as it eliminates the
need to set anything in the IDE options.<br>
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> > - Allow the export of environment
variables such as the PATH in the <br>
</p>
<div style="margin: 5px 0px;"> > IDE's options. </div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Yes, it's a todo to implement run
parameters for the compiler (and the other external tools). <br>
</p>
</blockquote>
Great! Once implemented, the script would be reduced to:<br>
export LIBOVERLAY_SCROLLBAR=0<br>
export FPC_VER=2.6.1<br>
/home/me/Programs/lazarus/lazarus-svn/lazarus
--pcp="/home/me/Programs/lazarus/config-lazarus-svn"
<br>
<br>
<blockquote
cite="mid:329738232.199100.1331811829263.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;"> > <br>
> This will not solve downside #3, as a script is still
needed for the <br>
> --pcp option and the overlay scrollbars issue, but it will
make <br>
> switching FPC versions a breeze. </div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">When you use macros, you only need one pcp
and then you can use the default. <br>
</p>
</blockquote>
I already use one config file (which is the pcp). What default are
you referring to?<br>
<br>
You are a treasure trove of info!<br>
<br>
Stephano<br>
</body>
</html>