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. Qt how to specify abi when compiling from source
Forum Updated to NodeBB v4.3 + New Features

Qt how to specify abi when compiling from source

Scheduled Pinned Locked Moved Solved General and Desktop
5 Posts 2 Posters 812 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.
  • S Offline
    S Offline
    Samuel Ives
    wrote on last edited by
    #1

    As I need the 3d features of qt but without using ANGLE, I compiled direct from the source as the tutorial of qt talks, but I noticed that after almost 3H compiling qt with jom it generated a 32bits version which is a problem because I need x64 for this project, so how to specify the abi? I compiled it as follows:

    configure -debug-and-release -platform win32-msvc2017 -shared -opensource -opengl desktop -nomake examples -nomake tests
    
    jom
    
    aha_1980A 1 Reply Last reply
    0
    • S Samuel Ives

      As I need the 3d features of qt but without using ANGLE, I compiled direct from the source as the tutorial of qt talks, but I noticed that after almost 3H compiling qt with jom it generated a 32bits version which is a problem because I need x64 for this project, so how to specify the abi? I compiled it as follows:

      configure -debug-and-release -platform win32-msvc2017 -shared -opensource -opengl desktop -nomake examples -nomake tests
      
      jom
      
      aha_1980A Offline
      aha_1980A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi @Samuel-Ives,

      did you open a 32 bit Visual Studio prompt by chance?

      Regards

      Qt has to stay free or it will die.

      1 Reply Last reply
      2
      • S Offline
        S Offline
        Samuel Ives
        wrote on last edited by
        #3

        Well I think the problem was this, it seems that the visual studio prompt I opened in the start menu was not specified as x86 or x64, it looks like they are in a subfolder called vc, I will try again with an x64 prompt and I will answer here if the problem was this.

        When I run the jom command to compile, will it compile to the abi of the open prompt or will it compile to x64 if I open the prompt for x64?

        1 Reply Last reply
        0
        • aha_1980A Offline
          aha_1980A Offline
          aha_1980
          Lifetime Qt Champion
          wrote on last edited by
          #4

          @Samuel-Ives said in Qt how to specify abi when compiling from source:

          When I run the jom command to compile, will it compile to the abi of the open prompt or will it compile to x64 if I open the prompt for x64?

          I really think that the resulting Qt library only depends on the compiler you are using. So if you have a x86 prompt, you get 32 bit libraries and programs; and for a x64 prompt you get 64 bit ones.

          jom is just a replacement for nmake and calls the compiler and linker specified by the Visual Studio prompt.

          PS: Don't forget to clean your build directory before rebuilding ;)

          Regards

          Qt has to stay free or it will die.

          S 1 Reply Last reply
          2
          • aha_1980A aha_1980

            @Samuel-Ives said in Qt how to specify abi when compiling from source:

            When I run the jom command to compile, will it compile to the abi of the open prompt or will it compile to x64 if I open the prompt for x64?

            I really think that the resulting Qt library only depends on the compiler you are using. So if you have a x86 prompt, you get 32 bit libraries and programs; and for a x64 prompt you get 64 bit ones.

            jom is just a replacement for nmake and calls the compiler and linker specified by the Visual Studio prompt.

            PS: Don't forget to clean your build directory before rebuilding ;)

            Regards

            S Offline
            S Offline
            Samuel Ives
            wrote on last edited by
            #5

            @aha_1980

            x86-windows-msvc2017-pe-64bit
            

            Thanks, it looks like the cause was actually the command prompt.

            1 Reply Last reply
            1

            • Login

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