Hi,

I looked at the FPC 2.4.1 output of the 'fpc -h' command and couldn't see any reference to the -W<x> parameter.

Under Linux the following information is missing, yet this information is displayed in the Windows version of FPC.

---------------------------------
-W<x> Target-specific options (targets)
-Wb Create a bundle instead of a library (Darwin) -WB Create a relocatable image (Windows)
-WC Specify console type application (EMX, OS/2, Windows) -WD Use DEFFILE to export functions of DLL or EXE (Windows) -We Use external resources (Darwin)
-WF Specify full-screen type application (EMX, OS/2) -WG Specify graphic type application (EMX, OS/2, Windows) -Wi Use internal resources (Darwin)
-WN Do not generate relocation code, needed for debugging (Windows)
-WR Generate relocation code (Windows)
-WX Enable executable stack (Linux)
---------------------------------

I know most of these options are not related to Linux (though there is one option now), I still think it's appropriate to output this information with the Linux FPC executable, because most FPC projects are cross-platform, so it is handy to see all available help for all platforms.

Regards,
- Graeme -

Graeme Geldenhuys wrote

Under Linux the following information is missing, yet this information is displayed in the Windows version of FPC.

It's unrelated to Linux vs Windows. Those options are enabled/disabled per architecture, and I bet you are using a 32 bit Windows and a 64 bit Linux FPC binary. It's quite possible that some that are not shown for x86-64 while they should be though.

Jonas

At least they're shown for the 32-bit version on linux

Michael.

Jonas Maebe het geskryf:

It's unrelated to Linux vs Windows. Those options are enabled/disabled per architecture, and I bet you are using a 32 bit Windows and a 64 bit Linux FPC binary.

Exactly what I was using. :-)

It's quite possible that some that are not shown for x86-64 while they should be though.

Those parameters are very handy if you are in a rush to create some build script (for various platforms, even though I am currently in 64-bit Linux). A quick 'fpc -h' to find the information without having to hunt through the various FPC PDF docs. That's why I think it will be very handy if parameter information is displayed on all platforms. Just a thought (or maybe it's because I'm lazy searching the PDF's). ;-)

Regards,
- Graeme -

Only options that are valid for the target architecture of the fpc binary should be shown, because showing options that are known not to work or that don't do anything mainly causes confusion.

Jonas

Jonas Maebe wrote

Only options that are valid for the target architecture of the fpc binary should be shown, because showing options that are known not to work or that don't do anything mainly causes confusion.

What about -an which needs extdebug defined before it works? I'd suggest that possibly 'fpc' or 'fpc -?' should display the currently-usable set, but -h which is more likely to be used by people who aren't utter beginners should display everything with [disabled] annotation where necessary.

While on this, I'd suggest that minimally-sensible output in response to --version and --help would be useful since this usage is so common these days.

That's not possible currently. The command line options are stored in a text file and cannot be modified based on conditional defines.

Jonas