[Interest] Qt on windows?

[Jason H]

Thanks for the tip. Moving it out of that cnhzdGF0aW9uX3VpLnppcA== directory made it happy.
I wonder if = is messing it up, even though it is quoted?
Total line is 130 chars. Does CMD have a 128 char limit? I thought that was raised to 32k?




> Sent: Monday, November 11, 2019 at 5:07 PM
> From: "Thiago Macieira" <thiago.macieira at intel.com>
> To: interest at qt-project.org
> Subject: Re: [Interest] Qt on windows?
>
> On Monday, 11 November 2019 13:01:32 PST Jason H wrote:
> > 15:58:59: Starting: "C:\Qt\5.12.5\mingw73_64\bin\qmake.exe"
> > "C:\Users\kevin\Downloads\cnhzdGF0aW9uX3VpLnppcA==\station_ui\station_ui.pr
> > o" -spec win32-g++ "CONFIG+=debug" "CONFIG+=qml_debug"
> > Usage: C:\Qt\5.12.5\mingw73_64\bin\qmake.exe [mode] [options] [files]
>
> Since qmake did not print anything before that "Usage:" line, it can be from
> this return in qmake/options.cpp:
>
>                 if(!handled) {
>                     return Option::QMAKE_CMDLINE_SHOW_USAGE |
> Option::QMAKE_CMDLINE_ERROR;
>                 }
>
> or from here:
>
>             if(Option::mkfile::project_files.isEmpty()) {
>                 usage(argv[0]);
>                 return Option::QMAKE_CMDLINE_ERROR;
>             }
>
> The first one looks impossible to me: it would imply qmake_mode is still
> "generate nothing" and I don't see how that is possible. So it must be the
> second: the list of project files is empty. That means qmake somehow failed to
> see anything in the command-line.
>
> Obviously that is not supposed to happen. Looks like the runtime completely
> failed to parse the GetCommandLineArgsW. Debugging is needed.
>
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel System Software Products
>
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest
>