Opened 8 weeks ago

Last modified 7 weeks ago

#11413 new defect

Enable all command line parameters also for daily builds

Reported by: lwcorp Owned by:
Priority: normal Component: Port: Win64
Keywords: Cc:

Description (last modified by lwcorp)

The first instruction in is to use a daily build first.
The second instruction is to report ScummVM version (scummvm -v).

But turns out "-v" and most other command line parameters simply don't work (luckily, --conf does work) in daily builds. If you try to run them, nothing happens as if you clicked nothing.
In matter of version, this leads to another related issue.

So please make sure all command line parameters work in all situations.

Change History (4)

comment:1 by lwcorp, 8 weeks ago

Description: modified (diff)

comment:2 by lwcorp, 8 weeks ago

Description: modified (diff)

comment:3 by lwcorp, 8 weeks ago

Component: --Unset--Port: Win64

comment:4 by criezy, 7 weeks ago

This is an issue that has been reported many times (see for example tickets #11317, #10809, #9804, or #6907). From what I understand the issue is only when printing the result (so any command line parameter that does not print something, such as --config, will work properly). And this seems related to the way the application is built. From #11317 I understand that the daily builds from buildbot are compiled as a GUI application and exhibit the issue, while those directly linked at might be compiled as a console application and work properly.

I would be tempted to close this ticket (as the other ones have been closed), but since this is something that comes back now and then, I am wondering if buildbot should be changed to build a console Windows application as well, or if there is a good reason to build a GUI one. Also I am not a Window user myself and I am not sure I actually understand what the issue really is and what the implications are.

Note: See TracTickets for help on using tickets.