<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 09-08-2011 15:53, Geoffrey Barton wrote:
<blockquote
cite="mid:40E9FD80-9104-4348-965F-A8A240F36FDC@periphon.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<base href="x-msg://47/"><br>
<div>
<div>On 9 Aug 2011, at 14:14, John Clymer wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Verdana;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; ">
<div>
<div style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font-family:
'times new roman', 'new york', times, serif; font-size:
12pt; ">
<div style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">I was thinking
more of a generic controller class, including a
memory.def (or whatever one wants to name it) file.
That would be easiest as it would only effect the
t_embed.pas file (and cpuinfo.pas file to add the
generic type.)<br>
<br>
Haven't looked into possibly a compiler option (and
may easily be more trouble than a command line
option):<br>
{$ARM_FLASH_START xxxxxxxx}<br>
{$ARM_FLASH_LENGTH xxxxxxxx}<br>
</div>
<div style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font-family:
'times new roman', 'new york', times, serif;
font-size: 12pt; ">{$ARM_SRAM_START xxxxxxxx}<br>
{$ARM_SRAM_LENGTH xxxxxxxx}<br>
<br>
But, I still think a static memory definition file
would require the least amount of code changes. And
would only effect only the ARM related files.<br>
</div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
The compiler option works well when you have conditional options
for different target builds using ifdefs, which I do I lot. It
makes it very easy to see if it is in the source file as it can
be locked to other options and you only need to select it in one
place.</div>
<div><br>
</div>
<div>A separate linker file starts to make FPC handle like any
other compiler :( instead of the joy to use it is :)</div>
</blockquote>
I agree. Keeping the configurations in code is easier to manage,
compared to the spiderweb of magically named files of other embedded
compilers<br>
<br>
I think that maybe creating an abstract class hierachy of chip
families, instead of the current solution of a single large case
statement, would be a better solution in the long run<br>
<blockquote
cite="mid:40E9FD80-9104-4348-965F-A8A240F36FDC@periphon.net"
type="cite">
<div>Geoffrey</div>
</blockquote>
<br>
</body>
</html>