Skip to content

Update the Linux build instructions to use qmake #832

Closed

Description

@justinclift

It's been pointed out in private email that CMake is broken for our 3.9.1 tarball builds, while qmake still works fine.

We might as well update the Linux compile instructions in BUILDING.md for Qt5 and qmake.

Activity

  1. justinclift commented on Oct 17, 2016

    @justinclift
    MemberAuthor

    Getting this done will probably address #803 too.

  2. leventelist commented on Oct 17, 2016

    @leventelist

    ...and if you could include package dependencies for a generic Linux system to use QT5, that would be nice too. It now insists on using QT4. This is just a wish.

    Thanks,
    Lev

  3. justinclift commented on Oct 17, 2016

    @justinclift
    MemberAuthor

    Ahhh, interesting. We're just about to switch to Qt5-only, so we'd better get that fixed sooner rather than later. 😄

  4. leventelist commented on Oct 17, 2016

    @leventelist

    Okay. I was too fast typing that wish. I read the documentation again, and there is a package list there. After installing those, it does build fine using QT5. I'm so sorry about the former message.

  5. justinclift commented on Oct 17, 2016

    @justinclift
    MemberAuthor

    Cool, no worries at all. 😄

  6. ergovia-devs commented on Jan 6, 2017

    @ergovia-devs

    An documentation update would be very much welcome. I tried to build sqlitebrowser with sqlcipher support longer that I liked using building.md on a (K)ubuntu 16.04.1. I could not build the master no matter what I used (cmake, make, qmake -> /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:103:5: error: no matching function for call to ‘qHash(const QVector<QSharedPointersqlb::Field >&)’)._ The only combination that worked was to use the v3.9.1 Tag, install qt4-default and use qmake CONFIG+=sqlcipher . and then make.
    Once built sqlitebrowser works flawlessly! Thx for this awesome tool.

  7. justinclift commented on Jan 6, 2017

    @justinclift
    MemberAuthor

    @ergovia-mobile Interesting. Was that just now?

    I got things to compile on Ubuntu MATE 16.10 yesterday using these steps:

        #920 (comment)

    Maybe I should spin up a VM and go through the steps again... 😁

  8. ergovia-devs commented on Jan 6, 2017

    @ergovia-devs

    Jepp, just now. :)

  9. justinclift commented on Jan 6, 2017

    @justinclift
    MemberAuthor

    Cool. I still have the VM, so I'll try it out now. 😄

  10. ergovia-devs commented on Jan 6, 2017

    @ergovia-devs

    Thank you. Good luck!

  11. justinclift commented on Jan 6, 2017

    @justinclift
    MemberAuthor

    k, just updated the VM I was using yesterday with our very latest source code.

    It compiled without issue, so that's good news.

    I'm downloading Kubuntu 16.0.4.1 now. I'll put that in a VM and try out the steps from yesterday on it, and see if I can figure out a proper build process for updating our instructions with. 😄

  12. ergovia-devs commented on Jan 6, 2017

    @ergovia-devs

    That's interesting. Feel free to ask the version number of any package that I have installed. 😄

  13. 28 remaining items

  14. justinclift commented on May 9, 2017

    @justinclift
    MemberAuthor

    An alternative that seems to work is installing Qt 5.6 through this PPA first:

        https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay

    Compiling DB4S works after that, without the above patch.

    If the patch approach is workable though, it's probably better as that'd also give us slightly wider compatibility in general (Qt 5.5).

  15. MKleusberg commented on May 12, 2017

    @MKleusberg
    Member

    @justinclift Hmm, not much to change in these few lines ^^ I've changed the commit to include an #if in order to not break the build for anybody using Qt 5.6 or later and pushed it to master. If there aren't any more problems, building on Qt 5.5 should work now.

  16. justinclift commented on May 12, 2017

    @justinclift
    MemberAuthor

    Awesome. 😄

  17. leventelist commented on May 12, 2017

    @leventelist
  18. baksosapi commented on Dec 13, 2017

    @baksosapi

    I get this 'Segmentation fault' when filled Password field.
    I'm already following your step

    $ cmake -DFORCE_INTERNAL_QSCINTILLA=ON -Dsqlcipher=1
    $ make
    $ sudo make install
    

    Debian Stretch

    Linux sid-tech 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
    

    Qmake

     $  qmake CONFIG+=sqlcipher
     $  make
     $  sudo make install
    

    But still no luck both CMAKE or QMAKE

    Any idea?

  19. user20190106 commented on Jan 6, 2019

    @user20190106

    First of all, many thanks for a great programme!

    I found DB Browser for SQLite when I was searching for a replacement for the Firefox SQLiteManager add-on which is not supported by Firefox any more. And I wish I had found DB Browser for SQLite earlier.

    In particular, the ability to quickly create a plot of the data is really useful. As the zooming feature is not yet included in the released versions, I (after some struggle) managed to build from source - my first ever build!

    For someone who has never compiled C programmes earlier, the most difficult part was to figure out what packages needed to be installed. Therefore I wrote the attached instructions for myself, and I think they might help other build newbies out there. (I wrote them with Markdown syntax, but the md extension was not allowed for attachments).

    DB_Browser_for_SQLite_build_from_source_on_Debian_Stretch.txt

    As to the QScintilla issue, I did not need to use the FORCE_INTERNAL_QSCINTILLA=ON switch. I guess the changes done relating to Issue #1555 have helped.

    Once again, many thanks for a great piece of software,
    user20190106

  20. mgrojo commented on Jan 6, 2019

    @mgrojo
    Member

    Thank you, @user20190106. I think your instructions for building under Debian Stretch could be a good contribution to our wiki.

  21. user20190106 commented on Jan 7, 2019

    @user20190106

    @mgrojo,
    please feel free to use the text as you wish. Or, as I have done some small edits, can I upload the md file somewhere myself or send it to someone for upload?

    BTW, I also managed to build SQLCipher 4.0.1 with OpenSSL 1.1.0 and then build DB Browser for SQLite using it instead of the standard Debian packages, so I can write an instruction on that as well, if you need one.

    However, as reported elsewhere, setting encryption from DB Browser does not work. But using a database that I encrypted with the SQLCipher command line interface works.

  22. mgrojo commented on Jan 7, 2019

    @mgrojo
    Member

    please feel free to use the text as you wish. Or, as I have done some small edits, can I upload the md file somewhere myself or send it to someone for upload?

    I think you can use the "New Page" button in the wiki and copy the content of your file there. I'm not sure, but I think all users have permissions to edit the wiki. If that isn't the case, please upload your last version as attachment and I'll copy it to the wiki.

    BTW, I also managed to build SQLCipher 4.0.1 with OpenSSL 1.1.0 and then build DB Browser for SQLite using it instead of the standard Debian packages, so I can write an instruction on that as well, if you need one.

    That would also be welcome. Sure some users will find that useful.

    However, as reported elsewhere, setting encryption from DB Browser does not work. But using a database that I encrypted with the SQLCipher command line interface works.

    Is that covered in an issue? I couldn't find one.

  23. user20190106 commented on Jan 8, 2019

    @user20190106

    @mgrojo,
    I managed to create 2 new Wiki pages, but I didn't add any links on the main page. I leave it up to the project team.

    The issue with encryption not working is Issue #1690. I added there a comment that I got the same error.

  24. mgrojo commented on Jan 8, 2019

    @mgrojo
    Member

    @user20190106 Thanks again! I've added the necesssary links to your pages to the main page. Great work.

  25. MKleusberg commented on May 22, 2021

    @MKleusberg
    Member

    I'll close this issue mostly because it is quite old and the original problem seems to be covered by now. Additionally it seems like that Qt6 is moving towards using cmake only anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions