Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qscintilla: get rid 'Not relevant classes found' messages from build log #322

Merged
merged 1 commit into from
May 20, 2015

Conversation

schdub
Copy link
Contributor

@schdub schdub commented May 20, 2015

While building of qscintilla library using CMake in build log there are many notes, something like:

[  1%] Generating __/src/moc_XPM.cxx
/home/jsbot/src/github/sqlitebrowser/libs/qscintilla/src/XPM.h:0: Note: No relevant classes found. No output generated.

That's because XPM class, for example, not inherited from QObject and does not require processing with Qt Meta Object Compiler.

Possible solution is to move these classes from QSCINTILLA_MOC_HDR into QSCINTILLA_HDR in file CMakeLists.txt

@MKleusberg, what you think about this?

@justinclift justinclift added the enhancement Feature requests. label May 20, 2015
@MKleusberg
Copy link
Member

Oh yeah, this makes a lot of sense. The only reason why it's all in the QSCINTILLA_MOC_HDR list is that when I included the QScintilla library I wanted it to build quickly in order to start coding as soon as possible. But then I never cleaned up the build files 😃

As it builds without any issues using Qt4 as well as Qt5 I'll go ahead and just merge this. Good job, by the way, with paying this much attention to detail 👍

MKleusberg added a commit that referenced this pull request May 20, 2015
qscintilla: get rid 'Not relevant classes found' messages from build log
@MKleusberg MKleusberg merged commit bd0df70 into sqlitebrowser:master May 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants