Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Create 32 and 64bit Kits on windows
Forum Updated to NodeBB v4.3 + New Features

Create 32 and 64bit Kits on windows

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
64-bit32bitkitwindows
3 Posts 2 Posters 4.9k 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.
  • D Offline
    D Offline
    davecotter
    wrote on last edited by davecotter
    #1
    • Windows 10 (Pro) (64bit) with latest updates
    • Visual Studio 2017 Community (do i even need that? does Qt rely on it?)
    • Qt Creator 4.3.1, Based on Qt 5.9.1 (MSVC 2015, 32 bit) (how'd that happen? i assumed it would install 64bit?)

    I need to create a .pro that can target both a 32bit and a 64bit build, using "win32" APIs, not UWP.

    in the installer, do i specify Qt install "msvc2015" both 32 and 64?
    i picked 2015 cuz there's no 2017 32bit ( i want parity), and i understand they are ABI compatible with 2017?
    and why is there no 2017 32bit?

    in Kits
    for 32bit i have picked MSVC++15 x86, though the debugger is set to 64bit (Does that matter?)
    for 64bit i have picked MSVC++15 amd64 (not: amd64_x86, not x86_amd64) (is that right??)
    but the warnings say "the msvc2015 might not produce code compatible with the msvc2017", is that safe to ignore?

    i need this BECAUSE i'm porting this project from another platform from 32 to 64, i need 32 running to create unit tests for 64. and because legacy.

    am i doing this right? or any advice?

    VRoninV 1 Reply Last reply
    0
    • D Offline
      D Offline
      davecotter
      wrote on last edited by
      #3

      yes, specify 32 and 64 for msvc2015
      i was able to ignore the warnings
      the kits i picked worked

      1 Reply Last reply
      0
      • D davecotter
        • Windows 10 (Pro) (64bit) with latest updates
        • Visual Studio 2017 Community (do i even need that? does Qt rely on it?)
        • Qt Creator 4.3.1, Based on Qt 5.9.1 (MSVC 2015, 32 bit) (how'd that happen? i assumed it would install 64bit?)

        I need to create a .pro that can target both a 32bit and a 64bit build, using "win32" APIs, not UWP.

        in the installer, do i specify Qt install "msvc2015" both 32 and 64?
        i picked 2015 cuz there's no 2017 32bit ( i want parity), and i understand they are ABI compatible with 2017?
        and why is there no 2017 32bit?

        in Kits
        for 32bit i have picked MSVC++15 x86, though the debugger is set to 64bit (Does that matter?)
        for 64bit i have picked MSVC++15 amd64 (not: amd64_x86, not x86_amd64) (is that right??)
        but the warnings say "the msvc2015 might not produce code compatible with the msvc2017", is that safe to ignore?

        i need this BECAUSE i'm porting this project from another platform from 32 to 64, i need 32 running to create unit tests for 64. and because legacy.

        am i doing this right? or any advice?

        VRoninV Offline
        VRoninV Offline
        VRonin
        wrote on last edited by VRonin
        #2

        @davecotter said in Create 32 and 64bit Kits on windows:

        (MSVC 2015, 32 bit) (how'd that happen? i assumed it would install 64bit?)

        No, what was used to build Qt Creator is irrelevant

        @davecotter said in Create 32 and 64bit Kits on windows:

        Visual Studio 2017 Community (do i even need that? does Qt rely on it?)

        Yes unless you use a different compiler but probably Qt is not MSVC2017 ready yet so you should use Visual Studio 2015 or the VS Bulid Tools

        @davecotter said in Create 32 and 64bit Kits on windows:

        I need to create a .pro that can target both a 32bit and a 64bit build

        Generally any .pro file can do both with no special changes

        The only difference between a 32 bit and 64 bit build with qmake/nmake is the argument you pass vcvarsall.bat (from visual studio)

        "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
        ~Napoleon Bonaparte

        On a crusade to banish setIndexWidget() from the holy land of Qt

        1 Reply Last reply
        1
        • D Offline
          D Offline
          davecotter
          wrote on last edited by
          #3

          yes, specify 32 and 64 for msvc2015
          i was able to ignore the warnings
          the kits i picked worked

          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