Skip to content

Package dependency when building on debian #635

Closed

Description

Hi

I'm currently running on a debian 7.11, cmake version 2.8.9 and tried to compile the package by myself.

I checked https://github.com/sqlitebrowser/sqlitebrowser/blob/master/BUILDING.md and made sure that build-essential, cmake, libqt4-dev and libsqlite3-dev are installed.

I'm building it with USE_QT5=OFF. ccmake shows

ANTLR2_INCLUDE_DIR               ANTLR2_INCLUDE_DIR-NOTFOUND
ANTLR2_LIBRARY                   ANTLR2_LIBRARY-NOTFOUND

Which debian package would satisfy that?

I continued the process and executed make but it stops at

Building CXX object libs/qscintilla/Qt4Qt5/CMakeFiles/qscintilla2.dir/qsciscintilla.cpp.o
In file included from /usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/qsciscintilla.cpp:23:0:
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:98:30: error: ‘ANNOTATION_INDENTED’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:267:28: error: ‘INDIC_FULLBOX’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:285:35: error: ‘INDIC_SQUIGGLEPIXMAP’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:289:37: error: ‘INDIC_COMPOSITIONTHICK’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:293:36: error: ‘INDIC_COMPOSITIONTHIN’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:297:30: error: ‘INDIC_TEXTFORE’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:428:20: error: ‘SC_MARK_BOOKMARK’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:457:26: error: ‘SC_WRAP_WHITESPACE’ was not declared in this scope
/usr/src/sqlitebrowser-3.8.0/libs/qscintilla/Qt4Qt5/Qsci/qsciscintilla.h:2092:5: error: ‘ScintillaBytes’ does not name a type

Is there any other package besides libqt4-dev that is needed there?

Activity

  1. justinclift commented on Jul 8, 2016

    @justinclift
    Member

    Hmmm, that's interesting. The ANTLR2 stuff is part of our source code. We bundle it with the rest of our source here, and it's supposed to be found automatically by cmake.

        https://github.com/sqlitebrowser/sqlitebrowser/tree/master/libs/antlr-2.7.7

    Just as a curiosity thing, what happens if you run qmake instead of cmake?

  2. justinclift commented on Jul 8, 2016

    @justinclift
    Member

    Yeah, it could be a path issue.

    With cmake, it kind of has a macro like language, so the "if(NOT ANTLR2 ..." clause you're talking about here shouldn't trigger, because it's coming after this line here:

    find_package(Antlr2)
    

    That "find_package()" macro runs this code, which seems to be where the problem is:

        https://github.com/sqlitebrowser/sqlitebrowser/blob/master/cmake/FindAntlr2.cmake

    The trick will be figuring out what and why. 😉

  3. justinclift commented on Jul 8, 2016

    @justinclift
    Member

    Btw, with qmake, run it in the main (root) checked out sqlitebrowser git source dir, then run make after it. Like this:

    $ git clone https://github.com/sqlitebrowser/sqlitebrowser.git
    $ cd sqlitebrowser
    $ qmake
    $ make
    [compiling stuff should happen here]
    

    Note that sometimes when compiling this way on OSX it barfs after a while with an error about missing language translation files. Running make again fixes the problem. (yeah, someone needs to look into that, but it's a pretty minor problem)

  4. justinclift commented on Jul 8, 2016

    @justinclift
    Member

    Sure no worries at all. Wonder if this is somehow showing up a weird gcc bug or something?

  5. justinclift commented on Jul 8, 2016

    @justinclift
    Member

    Yeah, that does sound kind of weird. 😦

  6. justinclift commented on Jul 29, 2016

    @justinclift
    Member

    @PSE-AG How did this go?

  7. justinclift commented on Jul 29, 2016

    @justinclift
    Member

    Thanks. Please keep us posted. 😄

  8. 16 remaining items

  9. revolter commented on Sep 19, 2016

    @revolter
    Member

    It looks like you can activate a window using the QWidget::activateWindow function, and we only call it here, but that shouldn't be a problem. So maybe it's an implicit behaviour caused by something else, rather than some explicit call?

  10. MKleusberg commented on Feb 3, 2017

    @MKleusberg
    Member

    Sounds like the focus problem is the same as in #934. But the bi-sected commits mentioned there are from a later date. Maybe it's a connection of multiple things causing this behaviour, I don't know. Either way, if anybody feels like bi-secting this (earlier) problem, please do so 😃

  11. EmperorArthur commented on Sep 27, 2017

    @EmperorArthur

    Hi, I can confirm this issue is still present as of commit 425bfa1.

    -- Could NOT find Antlr2 (missing: ANTLR2_LIBRARIES ANTLR2_INCLUDE_DIRS)

  12. justinclift commented on Sep 27, 2017

    @justinclift
    Member

    @EmperorArthur Try running make afterwards, even though that error shows up. There's some indication that the message there is bogus, and might not really mean anything went wrong after all. 😄

  13. MKleusberg commented on Sep 27, 2017

    @MKleusberg
    Member

    Yep, the error message just means that no Antlr2 development files provided by your distribution were found. In that case we just fall back to the Antlr2 library which is included in our repository. So it's safe to just run make as @justinclift said.

    However, if you have the Antlr2 lib and dev packages installed and you still see that error message, then that's probably a bug in our cmake file which is worth investigating 😄

  14. EmperorArthur commented on Sep 28, 2017

    @EmperorArthur

    The program still compiled, but I spent a bit of time googling around until I found this issue page. If the warning is meant to be ignored, it might be worth it to have the cmake file print out a note.

    We've all been trained to treat these sorts of warnings as important. It's really confusing ignoring it. Especially since all the other dependency warnings will cause compilation issues.

  15. added a commit that references this issue on Sep 30, 2017
  16. MKleusberg commented on Sep 30, 2017

    @MKleusberg
    Member

    I see 😄 I've just changed our cmake script to not print this warning and just silently use the copy of Antlr that's provided in our repository.

  17. justinclift commented on Sep 30, 2017

    @justinclift
    Member

    @EmperorArthur Would you be ok to try compiling again, using the latest git source, to verify the compile process is warning free for you now? 😄

  18. EmperorArthur commented on Oct 8, 2017

    @EmperorArthur

    Confirmed fixed.

    #cmake -Wno-dev .
    -- The C compiler identification is GNU 5.4.0
    -- The CXX compiler identification is GNU 5.4.0
    -- Check for working C compiler: /usr/bin/cc
    -- Check for working C compiler: /usr/bin/cc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Detecting C compile features
    -- Detecting C compile features - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Detecting CXX compile features
    -- Detecting CXX compile features - done
    -- Configuring done
    -- Generating done
    -- Build files have been written to: /home/user/src/sqlitebrowser
    
  19. justinclift commented on Oct 8, 2017

    @justinclift
    Member

    Awesome! Thanks for checking and letting us know @EmperorArthur. 😄

  20. justinclift commented on Oct 12, 2017

    @justinclift
    Member

    @PSE-AG The problem with DB4S being too aggressive with it's focus has likely just been fixed in our source code with #1168.

    Would you have the time/interest to compile and verify it from your point of view? 😄

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions