Qt 5.6.0 building on Windows 7 and MSVC 2013 issue



  • Hi all,

    I am trying to build the sources (as in a topic). My configuration is as follows:

    configure -confirm-license -prefix %QT_DIST% -icu -nomake tests -opensource -opengl desktop -developer-build
    

    At some point during the build I got these error messages:

    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_authentication_dialog_controller_cpp_77b3603f3e0b4538e38cc
    350a4bda9c0..rsp e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: location_provider_qt.moc_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_location_provider_qt_moc_77b3603f3e0b4538e38cc350a4bda9c0..rsp
     e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: moc_clipboard_qt.cpp_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_clipboard_qt_cpp_77b3603f3e0b4538e38cc350a4bda9c0..rsp e:/
    qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: web_engine_settings.moc_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_web_engine_settings_moc_77b3603f3e0b4538e38cc350a4bda9c0..rsp
    e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: moc_javascript_dialog_controller.cpp_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_javascript_dialog_controller_cpp_77b3603f3e0b4538e38cc350a
    4bda9c0..rsp e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: moc_file_picker_controller.cpp_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_file_picker_controller_cpp_77b3603f3e0b4538e38cc350a4bda9c
    0..rsp e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: moc_url_request_custom_job_delegate.cpp_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_url_request_custom_job_delegate_cpp_77b3603f3e0b4538e38cc3
    50a4bda9c0..rsp e:/qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    [11953/12030] ACTION QtWebEngineCore: moc_gl_context_qt.cpp_77b3603f3e0b4538e38cc350a4bda9c0
    FAILED: C:\Python27\python.exe gyp-win-tool action-wrapper environment.x86 QtWebEngineCore_target_moc_gl_context_qt_cpp_77b3603f3e0b4538e38cc350a4bda9c0..rsp e:
    /qt/qt-everywhere-opensource-src-5.6.0/qtwebengine\src\core
    moc: Cannot open options file specified with @
    QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
    
    ninja: build stopped: subcommand failed.
    NMAKE : fatal error U1077: 'E:\Qt\build-5.6.0-msvc2013_x86\qtwebengine\src\3rdparty\ninja\ninja.exe' : return code '0x1'
    Stop.
    NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\nmake.exe"' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: '(' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    

    I am not really sure what is wrong. Building the same with MSVC 2010 works like a charm.

    Is there anyone who can share some thoughts on this one, please ?

    Thanks in advance



  • @enmaniac said:

    moc: Cannot open options file specified with @

    Same problem here with VS2015 64bits build.



  • same problem here, building Qt 5.6 on Windows 7 64bit with Visual Studio 2015 Update 1



  • Same for me. Windows 7 64 bit, VS2015 Update 1 and 32 bit build (shadow build). :(



  • I have created bug report for this. Hopefully, it will be resolved.

    https://bugreports.qt.io/browse/QTBUG-52225



  • @enmaniac

    I asked on the dev mailing list. There is already a bug report:

    https://bugreports.qt.io/browse/QTBUG-51847

    Apparently, it works if you compile from git, the zip is badly packaged and some files have the wrong line ending.

    I'll verify that in the next few hours.



  • @sandy.martel23

    Yeah, I have noticed they closed my ticket as duplicate.
    I have never tried to build QT from GIT before.

    Is it preferred way of compiling sources ?


  • Lifetime Qt Champion

    Hi,

    No need to compile Qt completely, just clone the module from code.qt.io and use the usual combo: qmake/make/make install



  • @SGaist Thx I will give it a try.

    I am closing it as solved since the issue has been reported for bug-fixing and there are other options to make it work.



Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.