Important: Please read the Qt Code of Conduct -

Qt 5.8 - MSVC 2015 (x64) - Build error

  • Hi all,

    I'm trying to build Qt 5.8 (from qt-everywhere-opensource-src-5.8.0) withe MSVC 2015 (aka vc14) with the x64 toolset.

    My configure is:

    configure -prefix C:\Qt5 -release -opensource -confirm-license -opengl dynamic -nomake tests

    Then with a

    nmake release

    I'm getting this error:


    ninja\ninja.exe -C C:/Projects/qt-everywhere-opensource-src-5.8.0/qtwebengine/s
    ninja: Entering directory `C:/Projects/qt-everywhere-opensource-src-5.8.0/qtwebe
    ninja: error: WriteFile(device_vibration_mojo_bindings_for_blink_target_device_v
    f7c6c280c3.7b3e03a290ae36742187770e8d9b6182.rsp): Unable to create file. No such
    file or directory

    ninja: build stopped: .
    NMAKE : fatal error U1077: 'C:\Projects\qt-everywhere-opensource-src-5.8.0\qtweb
    engine\src\3rdparty\ninja\ninja.exe' : return code '0x1'
    NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0
    \VC\BIN\amd64\nmake.exe"' : return code '0x2'
    NMAKE : fatal error U1077: '(' : return code '0x2'
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    NMAKE : fatal error U1077: 'cd' : return code '0x2'

    Any idea?


  • Hi,
    probably the path is too long for WINDOWS. Please try to build Qt (with Webkit) in "c:\5.8.0"

  • Would this be an alternative to renaming the directory name:

    read this ==>

  • Please pay attention to the fact that so called LFN (Long File Names) are affected not only by length but also by (some) special characters e.g.: 5.8.0 is a LFN so is "5 8 0" with spaces while correct short name will be 5_8_0 or 580

    as you can see from my little test here (original/actual name is the last column and short name - IF PRESENT is in the next to last column)

    C:\TEMP>dir 5* /x
    02/23/2017  10:46 AM    <DIR>          580~1        5 8 0
    02/23/2017  10:44 AM    <DIR>          58D237~1.0   5.8.0
    02/23/2017  10:45 AM    <DIR>                       5_8_0

    Visual Studio (especially C/C++ compilers and linker) are notoriously known to stick to Short File Names (SFN)

    so my suggestion is to use a shorter path and try to keep it (all the way down) all in SFN
    e.g. C:\Projects\qt580.src\webeng\src\3rdparty\

  • Hi, for problems concerning path too long issues, I suggest you to try the new long path tool. This can help you with all kinds of path too long cases.

Log in to reply