Community
Participate
Working Groups
Created attachment 226344 [details] Indexer parser log The Indexer is unable to find the QDeclarativeView of Qt apparently. It warns me with: "Symbol 'QDeclarativeView' could not be resolved" here: https://github.com/mana/manamobile/blob/master/qmlapplicationviewer/qmlapplicationviewer.h#L16 The logs says: Unresolved includes (from headers in index): file:/usr/include/QtDeclarative/QDeclarativeView is not indexed Unresolved names: Attempt to use symbol failed: QDeclarativeView in file /home/ablu/mana/manamobile/qmlapplicationviewer/qmlapplicationviewer.h:16 I attached the full log. Regards Erik Schilling
Do you still experience this problem? (In reply to Erik Schilling from comment #0) > The Indexer is unable to find the QDeclarativeView of Qt apparently. It > warns me with: "Symbol 'QDeclarativeView' could not be resolved" here: > https://github.com/mana/manamobile/blob/master/qmlapplicationviewer/ > qmlapplicationviewer.h#L16 This link is broken.
Hi. Eclipse does not seem to autodetect any includes from the build anymore, but it somehow finds the #include. However QDeclarativeView itself is not found. I am not sure wether i configured it correctly though since I was unable to find the old Discovery options in the current version of eclipse (where I had to set an option to Project wide scanner (or somethig similar)). But well it took me quite a while to get the project working this far so I currently do not want to spend more time on it. Since I got a new pc i did not want to go through the hell of getting eclipse configured to work again (sorry guys, but the UI for all this stuff is really unintuitive). So I am happy with qt-creator now (it runs a lot more stable for me and I do not spend hours trying to get it working for each project). In case you want to look into the issue (for me it is no priority anymore) you can check the git at commit https://github.com/mana/manamobile/blob/add8b527258c5852b7dce5f1c8c1a65de4679747/qmlapplicationviewer/qmlapplicationviewer.h#L16. Regards and Happy Easter, Erik Schilling
Thanks Erik, our Qt support is definitely in a preview state at the moment. I'll take a look at this and make sure it's working in case you want to try again. We'll have a more compelling story once we get the QML editors contributed anyway. Just to double check, were you using our Qt plug-ins, org.eclipse.cdt.qt.*, or were you doing this with the plain vanilla CDT?
I was not aware of the Qt plugins until now. So I used plain cdt until then. Also, I cannot find any Qt plugins when i simply search for "Qt" in the plugin browser. Do you have any link to them? Regards, Erik
(In reply to Doug Schaefer from comment #3) > Thanks Erik, our Qt support is definitely in a preview state at the moment. > I'll take a look at this and make sure it's working in case you want to try > again. We'll have a more compelling story once we get the QML editors > contributed anyway. > > Just to double check, were you using our Qt plug-ins, org.eclipse.cdt.qt.*, > or were you doing this with the plain vanilla CDT? Should a plugin be necessary for basic things like resolving includes to work?
(In reply to Nathan Ridge from comment #5) > Should a plugin be necessary for basic things like resolving includes to > work? Not necessary, but the plug-in checks with qmake what the include path is supposed to be which should make it more reliable.
