Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Special Interest Groups
  3. C++ Gurus
  4. [Solved] Is there a way to decide on the address model used for compilation of Qt

[Solved] Is there a way to decide on the address model used for compilation of Qt

Scheduled Pinned Locked Moved C++ Gurus
2 Posts 1 Posters 1.2k Views 1 Watching
  • 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.
  • K Offline
    K Offline
    koahnig
    wrote on last edited by
    #1

    Finally I decided to do a 64 bit compilation of Qt with MinGW. I have downloaded the "Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit windows" from "MinGWbuilds":http://sourceforge.net/projects/mingwbuilds/
    Personally, I find it a bit puzzling that starting the compiler on a 64 bit system doesn't tell you what the target system is (32 or 64). Using the --version option does tell at least that this version 4.7.2, but no mentioning of dual-target. The same for --help. Quite a bit of digging through google unveiled the information of the memory model switches and the that the default mode is 64 bit.
    Certainly none of those complaints is Qt related. It would be merely a nice gesture of the MinGW guys to give more information when starting the compiler.
    Anyhow I followed "this recipe":http://qt-project.org/wiki/Building_Qt_Desktop_for_Windows_with_MinGW and compiled Qt4.8.4 for the 64 bit target. However, at the end the build is not really distinguishing from any other Qt build. The naming of the root folder is what I have chosen and luckily I did not mess this up.

    But is there a way to tell that this build is for 64 bit targets?

    I guess qmake can. At least it requires libwinpthread-1.dll which is part of the dual-target mingw and not part of 32 bit only MinGW.

    Also the generated dlls. Is there a way to detect which version it is?
    One distinction I found is the sheer size of QtGuid4.dll of almost 500MB. This is doubling the size of the compilation with 32 bit MinGW.

    Vote the answer(s) that helped you to solve your issue(s)

    1 Reply Last reply
    0
    • K Offline
      K Offline
      koahnig
      wrote on last edited by
      #2

      The dependency walker shows with the icon which memory model is used. The right side of the icon shows a column with 64.

      Vote the answer(s) that helped you to solve your issue(s)

      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