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. How to include a macOS .framework file in Qt creator "qmake"
Forum Updated to NodeBB v4.3 + New Features

How to include a macOS .framework file in Qt creator "qmake"

Scheduled Pinned Locked Moved Unsolved General and Desktop
14 Posts 3 Posters 3.1k 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.
  • SGaistS SGaist

    Hi,

    What exact issues are you having ?

    The usual combo for additional frameworks if you use qmake is

    LIBS += -F/path/to/framework -framework NameOfFramework
    

    If it's a release issue, then as @hskoglund suggested, macdpeloyqt should be able to do the job.

    U Offline
    U Offline
    UbiMiles
    wrote on last edited by
    #4

    @SGaist said in How to include a macOS .framework file in Qt creator "qmake":

    I did so , my includes are marked as errors and my builds fail with no useful information on the output,
    I am trying to include a framework called pylon located in "/Library/Frameworks/pylon.framework"
    it's tested on windows and It does work, as for macOS using Xcode with the framework gives the same functionality as the windows sdk, so it also shouldn't be an issue , yet seems I'm having a problem with including the framework in the Mac App

    1 Reply Last reply
    0
    • hskoglundH Offline
      hskoglundH Offline
      hskoglund
      wrote on last edited by
      #5

      Hi, for pylon it should be as @SGaist says:

      INCLUDEPATH += "/Library/Frameworks/pylon.framework"
      LIBS += -F"/Library/Frameworks/" -framework pylon
      
      U 1 Reply Last reply
      1
      • hskoglundH hskoglund

        Hi, for pylon it should be as @SGaist says:

        INCLUDEPATH += "/Library/Frameworks/pylon.framework"
        LIBS += -F"/Library/Frameworks/" -framework pylon
        
        U Offline
        U Offline
        UbiMiles
        wrote on last edited by
        #6

        @hskoglund
        it still doesn't seem to work :(
        a464817e-39a5-44d0-b7d1-78f0dad453e5-image.png

        U 1 Reply Last reply
        0
        • U UbiMiles

          @hskoglund
          it still doesn't seem to work :(
          a464817e-39a5-44d0-b7d1-78f0dad453e5-image.png

          U Offline
          U Offline
          UbiMiles
          wrote on last edited by
          #7

          @UbiMiles
          the headers are usually included as <pylon/header.h>
          in case that requires any changes, there isn't a pylon directory however and the headers are inside pylon.framework in a folder called Headers

          1 Reply Last reply
          0
          • hskoglundH Offline
            hskoglundH Offline
            hskoglund
            wrote on last edited by
            #8

            Ok, try adding these as well:

            INCLUDEPATH += "/Library/Frameworks/pylon.framework/Headers/"
            INCLUDEPATH += "/Library/Frameworks/"
            
            U 1 Reply Last reply
            0
            • hskoglundH hskoglund

              Ok, try adding these as well:

              INCLUDEPATH += "/Library/Frameworks/pylon.framework/Headers/"
              INCLUDEPATH += "/Library/Frameworks/"
              
              U Offline
              U Offline
              UbiMiles
              wrote on last edited by
              #9

              @hskoglund
              sadly it is still the same
              would a sample of the build settings for a project with the framework in Xcode be of any help?
              I am quite since I am not too experienced with Building Qt apps for MacOS

              1 Reply Last reply
              0
              • hskoglundH Offline
                hskoglundH Offline
                hskoglund
                wrote on last edited by
                #10

                I suppose you already checked some old posts like this one: https://imaginghub.com/forum/posts/702-using-basler-pylon-sdk-on-mac-with-qt ?
                (he manages to build it successfully with some warnings)

                U 1 Reply Last reply
                1
                • hskoglundH hskoglund

                  I suppose you already checked some old posts like this one: https://imaginghub.com/forum/posts/702-using-basler-pylon-sdk-on-mac-with-qt ?
                  (he manages to build it successfully with some warnings)

                  U Offline
                  U Offline
                  UbiMiles
                  wrote on last edited by
                  #11

                  @hskoglund
                  I didn't come across this page but trying their pro file settings it's still throwing errors not recognizing any members in the headers

                  U 1 Reply Last reply
                  0
                  • U UbiMiles

                    @hskoglund
                    I didn't come across this page but trying their pro file settings it's still throwing errors not recognizing any members in the headers

                    U Offline
                    U Offline
                    UbiMiles
                    wrote on last edited by
                    #12

                    @UbiMiles
                    I also found this and the op of the thread seems to have gotten it working
                    https://forum.qt.io/topic/105593/undefined-symbols-for-architecture-x86_64-pylon-cpylonimagewindow-close

                    U 1 Reply Last reply
                    0
                    • U UbiMiles

                      @UbiMiles
                      I also found this and the op of the thread seems to have gotten it working
                      https://forum.qt.io/topic/105593/undefined-symbols-for-architecture-x86_64-pylon-cpylonimagewindow-close

                      U Offline
                      U Offline
                      UbiMiles
                      wrote on last edited by
                      #13

                      @UbiMiles
                      it seems to me he recomposed the Headers folder into /temp directory in the order they originally are
                      I should try that out

                      1 Reply Last reply
                      0
                      • U Offline
                        U Offline
                        UbiMiles
                        wrote on last edited by
                        #14

                        I think my issue is not with linking the library itself and I apologize for that.
                        the question that would solve my problem is, what is the equivalent of xocde's "Runpath Search Path" for qmake?

                        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