Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Building Qt 5 from source with MinGW - wrong headers being used
QtWS25 Last Chance

Building Qt 5 from source with MinGW - wrong headers being used

Scheduled Pinned Locked Moved Installation and Deployment
1 Posts 1 Posters 1.3k 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.
  • T Offline
    T Offline
    t3685
    wrote on last edited by
    #1

    Hi,

    I'm trying to build Qt 5 from source for testing purposes using MinGW. However I have Visual Studio 6.0 still installed to maintain older projects.

    I set up my path as follows:

    @PATH=C:\Perl\site\bin;C:\Perl\bin;C:\MinGW\bin@

    In the qtbase folder I use the following command to configure the build

    @configure.bat -developer-build -opensource -confirm-license -nomake demos -nomake examples -nomake tests -opengl desktop@

    and then I run mingw32-make

    However I get the following error:

    @mingw32-make[4]: *** [.obj/release_shared/qlatincodec.o] Error 1
    mingw32-make[3]: *** [release] Error 2
    mingw32-make[2]: *** [sub-tools-bootstrap-make_first] Error 2
    mingw32-make[1]: *** [sub-tools-make_first] Error 2
    mingw32-make: *** [sub-src-make_first] Error 2@

    and I get many errors similar to this:

    @C:\Program Files (x86)\Microsoft Visual Studio\VC98\Include/xstring:86:28: error
    : '_Len' was not declared in this scope
    C:\Program Files (x86)\Microsoft Visual Studio\VC98\Include/xstring:87:15: error
    : '_Ptr' was not declared in this scope
    C:\Program Files (x86)\Microsoft Visual Studio\VC98\Include/xstring:88:11: error
    : there are no arguments to '_Eos' that depend on a template parameter, so a dec
    laration of '_Eos' must be available [-fpermissive]@

    Now I assume that the configuration/build is somehow using the wrong headers and I was wondering what I can do to avoid this.

    Thanks!

    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