/1/ the platform is loaded to query its configuration options and unloaded; then,
/2/ the command line, environment and config file are parsed; and finally,
/3/ the platform is loaded using the configuration options.
I guess it ought to be possible to remember the platform chosen in step /1/ and avoid re-scanning the available platform modules.
AIUI that's "as designed".
/1/ the platform is loaded to query its configuration options and unloaded; then,
/2/ the command line, environment and config file are parsed; and finally,
/3/ the platform is loaded using the configuration options.
I guess it ought to be possible to remember the platform chosen in step /1/ and avoid re-scanning the available platform modules.