Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Error building Qt 5 from Git on Windows
Forum Update on Monday, May 27th 2025

Error building Qt 5 from Git on Windows

Scheduled Pinned Locked Moved General and Desktop
3 Posts 2 Posters 2.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Violet Giraffe
    wrote on 28 Dec 2012, 21:34 last edited by
    #1

    I'm trying to buil Qt 5 with VS2010 and this is what I eventually get:

    (set "PATH=K:\Qt\5\Built\qtbase..\gnuwin32\bin;%PATH%") && python K:/Qt/5/Built/qtwebkit/Source/WebCore/inspector/generate-inspector-protocol-version -o generated\InspectorProtocolVersion.h inspector\Inspector.json
    Self-test failedNMAKE : fatal error U1077: '(set' : return code '0x1'
    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.

    K:\Qt\5\Built\ is the path to my Qt repository.
    I have successfuly compiled it at work with the same configuration and VS2010. No idea what's wrong here.

    1 Reply Last reply
    0
    • D Offline
      D Offline
      deus
      wrote on 6 Feb 2013, 10:20 last edited by
      #2

      I got the exact same output.
      Did you find a solution for this?

      Gnuwin binaries were already manually set in the path, though it seems they were appended in the process.

      I've set the QTDIR and QMKSPEC variables(probably unnecessary but there you go).

      But I've also got the binary installed QT already installed.

      1 Reply Last reply
      0
      • D Offline
        D Offline
        deus
        wrote on 6 Feb 2013, 10:56 last edited by
        #3

        Found the problem, its a bug with python 33.

        Switch to version 27.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved