Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Update: Forum Guidelines & Code of Conduct


    Qt World Summit: Early-Bird Tickets

    Unsolved qDesktopSearch on github

    Announcements
    qdesktopsearch github clucene jvm
    2
    7
    2035
    Loading More Posts
    • 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.
    • P
      privet last edited by

      Started qDesktopSearch, an app using the JVM and CLucene to index & search the files of the local machine:
      https://github.com/privet56/qDesktopSearch
      I would love to get help & improvement hints!

      1 Reply Last reply Reply Quote 0
      • SGaist
        SGaist Lifetime Qt Champion last edited by

        Hi,

        One thing you can do to make thing cleaner is to create a .pri file per dependencies you have and include them in your main .pro file. That way you keep thing clearly separated and you avoid having 200 files listed there.

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        P 1 Reply Last reply Reply Quote 1
        • P
          privet @SGaist last edited by

          @SGaist Cool idea! Thanks!
          I did it this way:
          https://github.com/privet56/qDesktopSearch/blob/master/qDesktopSearch_3rdparty.pri

          with the result, that

          1. the .pro file is much more clear
            AND
          2. the folder structure within Qt Creator is more clear
          1 Reply Last reply Reply Quote 0
          • SGaist
            SGaist Lifetime Qt Champion last edited by

            In the absolute, I would have split also the content per 3rd party.

            so that qDesktopSearch_3rdparty.pri would look like:

            include(zlib/zlib.pri)
            include(boost/boost.pri)
            etc.
            

            That way each 3rd party is responsible for providing its own informations.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            P 1 Reply Last reply Reply Quote 1
            • P
              privet @SGaist last edited by

              @SGaist
              Yeah, I see your point... now I implemented this way:

              include(qDesktopSearch_3rdparty_clucene.pri)
              include(qDesktopSearch_3rdparty_qt-solutions.pri)

              because:

              1. the referenced zlib & boost are part of the CLucene distri, that's why I put them in one pri (see https://sourceforge.net/p/clucene/code/ci/e8e3d20f20da5ee3e37d347207b01890829a5475/tree/src/ext/ )

              2. now I also need QtSingleApplication, and I put the lib for that in an extra pri

              Thanks for the hint!

              1 Reply Last reply Reply Quote 0
              • SGaist
                SGaist Lifetime Qt Champion last edited by

                Doesn't QtSingleApplication come with it's own .pri ?

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                P 1 Reply Last reply Reply Quote 1
                • P
                  privet @SGaist last edited by

                  @SGaist Very good remark!
                  Yes, you're right: there is a pri to be included;
                  however, I decided for the moment to include the necessary files explicitly
                  without the 'magic' of 'qtsingleapplication.pri'
                  (I'm still playing around with the best settings...)

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post