On Fri, 2 Apr 2021, Florian Klämpfl via fpc-devel wrote:
Am 02.04.2021 um 16:21 schrieb Michael Ring via fpc-devel
:
Florian, it seems you missed a comment on that topic I wrote a while ago.
You are right. The controller unit is written now like:
Seems
> Am 02.04.2021 um 16:21 schrieb Michael Ring via fpc-devel
> :
>
> Florian, it seems you missed a comment on that topic I wrote a while ago.
>
>
You are right. The controller unit is written now like:
___
fpc-d
Florian, it seems you missed a comment on that topic I wrote a while ago.
There is also the need to have a tuple that matches controllertype to
controllerunit to get rid of a big peace of duplicated code from
cpuinfo.pas in lazarus.
Lazarus needs to know which unit to include so that codetool
On Fri, 2 Apr 2021, Florian Klämpfl via fpc-devel wrote:
Am 07.03.2021 um 15:12 schrieb Florian Klämpfl via fpc-devel
:
Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel:
Hello,
As a follow-up on a Lazarus feature request.
Among other applications, Lazarus uses some hard-coded list that
> Am 07.03.2021 um 15:12 schrieb Florian Klämpfl via fpc-devel
> :
>
> Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel:
>> Hello,
>> As a follow-up on a Lazarus feature request.
>> Among other applications, Lazarus uses some hard-coded list that represent
>> FPC features. Like supported MCU
On Tue, 9 Mar 2021, Michael Van Canneyt via fpc-devel wrote:
On Tue, 9 Mar 2021, Florian Klämpfl via fpc-devel wrote:
Since we write the resource strings in JSON, and XML is meanwhile all but
replaced by JSON, I think it would be much better to write JSON ?
The compiler writes the node
On Tue, 9 Mar 2021, Florian Klämpfl via fpc-devel wrote:
Since we write the resource strings in JSON, and XML is meanwhile all but
replaced by JSON, I think it would be much better to write JSON ?
The compiler writes the node tree already as XML, so I thought XML might
be the better choice
Am 08.03.21 um 10:46 schrieb Michael Van Canneyt via fpc-devel:
On Sun, 7 Mar 2021, Florian Klämpfl via fpc-devel wrote:
Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel:
Hello,
As a follow-up on a Lazarus feature request.
Among other applications, Lazarus uses some hard-coded list that
On Sun, 7 Mar 2021, Florian Klämpfl via fpc-devel wrote:
Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel:
Hello,
As a follow-up on a Lazarus feature request.
Among other applications, Lazarus uses some hard-coded list that
represent FPC features. Like supported MCU and boards. It would b
for this command:
~/fpcupdeluxe-embedded/fpc/bin/aarch64-darwin/fpc -Tembedded -Parm
-WpDISCOVERYF411VE -ix
it would be good to also get back the controllerunitstr that belongs to
DISCOVERYF411VE
or, when size does not matter much include the unit already in the more
generalized call:
~
Looks good. Thanks. My conclusion: we need more of this !
No kidding. This XML output is very useful. And, naturally, I would like
to ask for more.
If more is given, the use of a scheme would make it very convenient
(easy) to add new content and to read this new content.
But anyhow, this output
Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel:
Hello,
As a follow-up on a Lazarus feature request.
Among other applications, Lazarus uses some hard-coded list that
represent FPC features. Like supported MCU and boards. It would be
(much) more convenient to parse the FPC output itself to s
Hello,
As a follow-up on a Lazarus feature request.
Among other applications, Lazarus uses some hard-coded list that
represent FPC features. Like supported MCU and boards. It would be
(much) more convenient to parse the FPC output itself to supply this
info. And that could be made easy by usi
13 matches
Mail list logo
