<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 27/03/12 18:44, Mattias Gaertner wrote:
<blockquote
cite="mid:898027272.354392.1332863077348.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<p style="margin: 0pt;"> <span> <span></span> </span> </p>
<div style="margin: 5px 0px;"> <br>
patspiper <a class="moz-txt-link-rfc2396E" href="mailto:patspiper@gmail.com"><patspiper@gmail.com></a> hat am 27. März 2012 um
17:17 geschrieben: <br>
<br>
> This is related to bug 0021580: Feature request: Robust IDE
cross-compiling. <br>
> <br>
> With Lazarus 1.0 being closer than ever, and with the
availability of <br>
> different Linux scripts to compile FPC from source
(including cross <br>
> compilation), maybe the time has come to have an automated
installer <br>
> that does all that, including the compilation of the cross
binutils. </div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">That is one approach. </p>
<p style="margin: 0px;">Another is to use VMs. </p>
<p style="margin: 0px;">VMs are nowadays very easy to setup and
they run almost as fast (sometimes even faster) as the host
system.</p>
<p style="margin: 0px;">Installing/Upgrading all the required libs
in a VM is much simpler than setting up these libs cross
compiled. <br>
</p>
</blockquote>
Not necessarily (assuming you have the right dependencies already
installed). I use 3 scripts that rely on sources (exported from SVN
or a released FPC, plus a tar for binutils). Although not perfect,
these scripts:<br>
<br>
- Make and install FPC for the host platform (given an FPC version
number), based on a starting compiler or an installed FPC<br>
- Make and install the cross binutils for the desired target
platform<br>
- Make and install cross FPC for the desired target platform<br>
<br>
Finally, the Lazarus launcher script exports the required paths
(given the FPC version number) and executes startlazarus.<br>
<br>
As for Lazarus itself, my default build modes allow me to switch
target platforms with minimal effort (using the build modes tool
button)<br>
<br>
The above makes it possible to use FPC SVN and stable releases very
efficiently for normal as well as cross compiling.<br>
<br>
<blockquote
cite="mid:898027272.354392.1332863077348.JavaMail.open-xchange@comcenter.netcologne.de"
type="cite">
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Maybe someone wants to setup VM image for
public download for his favorite distribution with preinstalled
Lazarus and other common development tools.</p>
<p style="margin: 0px;"> </p>
<p>Lazarus projects and packages are made for cross platforms. So
you can simply copy them or use VCS. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;"> > <br>
> The complement for Lazarus would be the ability to
import/export the <br>
> default project options with build modes. </div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">The default project options (compiler
options with build modes) are stored in
~/.lazarus/projectoptions.xml</p>
</blockquote>
Oh..I meant the default project build modes only...my bad!<br>
<br>
Stephano<br>
</body>
</html>