<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Am 14.11.2015 um 11:20 schrieb Sven
Barth:<br>
</div>
<blockquote
cite="mid:CAFMUeB_0rQX86mV+UV1JKZJfDJvYsLbtUpc93Cz_z4sb24pabA@mail.gmail.com"
type="cite">
<p>Am 14.11.2015 10:57 schrieb "Michael Schnell" <<a
moz-do-not-send="true" href="mailto:mschnell@lumino.de"><a class="moz-txt-link-abbreviated" href="mailto:mschnell@lumino.de">mschnell@lumino.de</a></a>>:<br>
><br>
> On 11/12/2015 09:48 PM, Simon Ameis wrote:<br>
>><br>
>> Hello Georg,<br>
>><br>
>> yes, RTL may be the wrong term, so let us call it PEL
(Pascal Embedded<br>
>> Library)<br>
><br>
> In fact much of this needs to be done by (or at least
better is done by) Device drivers, and hence not in the reach of
fpc.</p>
<p>You are aware that the discussion is about FPC's embedded
target, thus no device drivers available, because there's no OS
running that could host them?</p>
<p>And aside from that it is possible to write device drivers in
FPC if one knows how to do it.</p>
<p>Regards,<br>
Sven</p>
</blockquote>
So will FPC provide the compiler (and maybe an FPC-embedded linker
for ARM) only?<br>
Or would be a reasonable goal to publish "default" device drivers
for embedded targets?<br>
<br>
I think, it would be fine to get a full solution by using FPC and
Lazarus (and GNU binutils atm). This would make it easier to get
into embedded developing because you don't need to the libraries but
can instantly start developing you application.<br>
<br>
Lazarus then could integrate the tools for uploading the compiled
and linked binary to the embedded device.<br>
<br>
Regards<br>
Simon<br>
</body>
</html>