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
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
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
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:
~
