[fpc-devel] "fpc -h" and "fpc -i"
XHajT03 at hajny.biz
Wed Nov 12 13:35:24 CET 2014
On Wed, November 12, 2014 13:03, Juha Manninen wrote:
> On Sun, Nov 9, 2014 at 4:51 PM, Tomas Hajny <XHajT03 at hajny.biz> wrote:
>> I've finished implementation of solution for easier parsing of
>> supported values for certain options and the solution _does_ match
>> the compiler capabilities because the values come from the particular
>> compiler itself.
> Thanks. I will look at the parser next weekend.
OK. BTW, there's still one thing which came to my mind while looking at it
- the list of supported compilers / platforms (aka options for 'fpc
-P...'). That one is not known in the platform-specific compilers but
rather in the fpc helper which is the reason why I didn't add it yet.
However, I'm willing to have a look at this one too if it is considered
useful (let me know - e.g. by adding a note to the bug report).
> The fact still is that "fpc -h" + a parser in Lazarus requires the
> least amount of maintenance in the long run.
> The help output already listed the vast majority of all options. Most
> new options will be added there, too, even if some were forgotten.
> This is the same discussion we already had with Dmitry and Mattias.
> The external file needs maintenance for all FPC options for the eternal
> Still, it is bad that duplicate work for the options GUI was done,
> considering our limited resources.
> Unfortunately Dmitry proposed his system when I had already
> implemented the parser and GUI in Lazarus trunk and was fixing the
> remaining bugs.
> It was discussed a couple of months before that in our mailing list.
> Is there any way to make a hybrid solution? The linker options indeed
> would bring extra value to it. But, we can discuss it in Lazarus list
> if needed.
Since nobody responded to the other bug report related to options missing
in the list, I'll probably take it as well and ask others about the
information I couldn't find in the sources myself.
More information about the fpc-devel