Re: [Development] Issues with latest Qt6 snapshot on Windows
On Fri, Jul 24, 2020 at 6:58 AM Alexandru Croitor wrote: > > > > > On 24. Jul 2020, at 05:59, Sandro Andrade wrote: > > > > Hi there, > > Hi! > > > > > I'm trying the latest Qt6 snapshot provided by the official installer > > on Windows 10 with MSVC 2019. > > Thanks for providing feedback! > > > > > I've noticed that QMake builds work fine only in Release mode. > > Building in Debug mode generates a: > > > > qtmaind.lib(qtmain_win.cpp.obj) : warning LNK4099: PDB 'WinMain.pdb' > > was not found with 'qtmaind.lib(qtmain_win.cpp.obj)' or at > > 'C:\Users\Sandro S. > > Andrade\Documents\build-teste3-Desktop_Qt_6_0_0_MSVC2019_64bit-Debug\debug\WinMain.pdb'; > > linking object as if no debug info > > qtmaind.lib(qtmain_win.cpp.obj) : error LNK2019: unresolved external > > symbol __imp_CommandLineToArgvW referenced in function WinMain > > > > Does such snapshot support only Release builds or am I missing > > something in my setup? > > The snapshot should have supported Debug builds as well. It's a bug that it > doesn't. > I can reproduce the issue. > > > > > Also, CMake builds with many errors like: > > > > CMake Error at CMakeLists.txt:44 (target_link_libraries): > > Error evaluating generator expression: > > $ > > Target "Vulkan::Vulkan" not found. > > I can reproduce this particular issue also. > > > > > Do I need to install Angle, Direct3D, or Vulkan to fix this or is > > CMake support with Qt6 on Windows not ready yet? > > I'm not sure yet if installing Vulkan will help, but you can try. > > The snapshot is just a development snapshot, so it's expected to find issues. > > Many issues were already fixed since the snapshot was released, but these > apparently haven't been. > > You can track the issues at https://bugreports.qt.io/browse/QTBUG-85240 Thanks for replying. I'll watch the bug and try to build new snapshots from sources. Sandro > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Issues with latest Qt6 snapshot on Windows
Hi there, I'm trying the latest Qt6 snapshot provided by the official installer on Windows 10 with MSVC 2019. I've noticed that QMake builds work fine only in Release mode. Building in Debug mode generates a: qtmaind.lib(qtmain_win.cpp.obj) : warning LNK4099: PDB 'WinMain.pdb' was not found with 'qtmaind.lib(qtmain_win.cpp.obj)' or at 'C:\Users\Sandro S. Andrade\Documents\build-teste3-Desktop_Qt_6_0_0_MSVC2019_64bit-Debug\debug\WinMain.pdb'; linking object as if no debug info qtmaind.lib(qtmain_win.cpp.obj) : error LNK2019: unresolved external symbol __imp_CommandLineToArgvW referenced in function WinMain Does such snapshot support only Release builds or am I missing something in my setup? Also, CMake builds with many errors like: CMake Error at CMakeLists.txt:44 (target_link_libraries): Error evaluating generator expression: $ Target "Vulkan::Vulkan" not found. Do I need to install Angle, Direct3D, or Vulkan to fix this or is CMake support with Qt6 on Windows not ready yet? Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] QtModeling - the last mile
On Wed, Apr 29, 2015 at 6:08 PM, Sandro Andrade sandroandr...@kde.org wrote: On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt ritt...@gmail.com wrote: Any links/code/docs?) Yes, sorry :) Wiki page: http://wiki.qt.io/QtModeling Git repository: http://www.gitorious.org/qt/qtmodeling DuSE-MT (QtModeling-based tool) website: http://duse.sourceforge.net/ DuSE-MT repository: www.gitorious.org/duse-mt/duse-mt Some posts about QtModeling: https://liveblue.wordpress.com/2012/12/11/call-for-arms-qtmofqtuml/ https://liveblue.wordpress.com/2013/01/21/qtmofqtuml-xmi-serialization-and-metamodel-plugins/ https://liveblue.wordpress.com/2013/11/18/how-cute-can-modeling-be/ Cheers, Sandro So, anyone ? Let's put this baby out :) I'll present a talk about QtModeling at Akademy this year. If any of you guys is also heading there, we might schedule a chat. Cheers, Sandro Konstantin 2015-04-30 0:26 GMT+04:00 Sandro Andrade sandroandr...@kde.org: Hi there, Some time ago, I started the development of QtModeling : a qt add-on aimed at providing metamodeling features and the basic infrastructure for dealing with software models. It already has a lot of interesting features and now I have the available time to making it good enough to be released. There are, however, some design choices I would like to discuss and get some feedback from some of you guys. Implementing the UML metamodel, for example, requires a considerable time investiment. Part of this is already done, but I would like to set up a plan to incrementally release such features. So, would anyone be willing to provide some guidance and keep up with QtModeling to its release ? Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QtModeling - the last mile
Hi there, Some time ago, I started the development of QtModeling : a qt add-on aimed at providing metamodeling features and the basic infrastructure for dealing with software models. It already has a lot of interesting features and now I have the available time to making it good enough to be released. There are, however, some design choices I would like to discuss and get some feedback from some of you guys. Implementing the UML metamodel, for example, requires a considerable time investiment. Part of this is already done, but I would like to set up a plan to incrementally release such features. So, would anyone be willing to provide some guidance and keep up with QtModeling to its release ? Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtModeling - the last mile
On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt ritt...@gmail.com wrote: Any links/code/docs?) Yes, sorry :) Wiki page: http://wiki.qt.io/QtModeling Git repository: http://www.gitorious.org/qt/qtmodeling DuSE-MT (QtModeling-based tool) website: http://duse.sourceforge.net/ DuSE-MT repository: www.gitorious.org/duse-mt/duse-mt Some posts about QtModeling: https://liveblue.wordpress.com/2012/12/11/call-for-arms-qtmofqtuml/ https://liveblue.wordpress.com/2013/01/21/qtmofqtuml-xmi-serialization-and-metamodel-plugins/ https://liveblue.wordpress.com/2013/11/18/how-cute-can-modeling-be/ Cheers, Sandro Konstantin 2015-04-30 0:26 GMT+04:00 Sandro Andrade sandroandr...@kde.org: Hi there, Some time ago, I started the development of QtModeling : a qt add-on aimed at providing metamodeling features and the basic infrastructure for dealing with software models. It already has a lot of interesting features and now I have the available time to making it good enough to be released. There are, however, some design choices I would like to discuss and get some feedback from some of you guys. Implementing the UML metamodel, for example, requires a considerable time investiment. Part of this is already done, but I would like to set up a plan to incrementally release such features. So, would anyone be willing to provide some guidance and keep up with QtModeling to its release ? Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] NOTE: Gerrit / Codereview upgrade – Service unavailable Friday June 13, 7:00 – 10:00 CEST
On Mon, Jun 16, 2014 at 5:00 AM, Haataja Ismo ismo.haat...@digia.com wrote: Hi, I had a change integrated and merged nearly 12 hours ago (https://codereview.qt-project.org/#/c/87431/) but it hasn't been replicated in gitorious (https://qt.gitorious.org/qt/qtmodeling/activities) up to now. Is it expected that such replication occurs automatically as before or am I missing something ? Thanks in advance, Sandro Yes, replication should happen automatically. For some reason it looks like this one was not replicated in first place. But you have managed to trigger the replication with another change. And what I looked now with some other changes, replication seems to be working. We'll follow the situation. Ok, it seems things are fine now. Thanks for replying, Sandro BR, Ismo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] NOTE: Gerrit / Codereview upgrade – Service unavailable Friday June 13, 7:00 – 10:00 CEST
On Sat, Jun 14, 2014 at 8:55 AM, Haataja Ismo ismo.haat...@digia.com wrote: Yes, we are having some performance issues but are working with that. Right now everything works smoothly again. We’ll keep following the situation. Hi there, I had a change integrated and merged nearly 12 hours ago (https://codereview.qt-project.org/#/c/87431/) but it hasn't been replicated in gitorious (https://qt.gitorious.org/qt/qtmodeling/activities) up to now. Is it expected that such replication occurs automatically as before or am I missing something ? Thanks in advance, Sandro BR, Ismo From: Oleg Shparber [mailto:troll...@gmail.com] Sent: 14. kesäkuuta 2014 3:05 To: Haataja Ismo Cc: development@qt-project.org Subject: Re: [Development] NOTE: Gerrit / Codereview upgrade – Service unavailable Friday June 13, 7:00 – 10:00 CEST Gerrit has become terribly slow, I cannot view pull requests or files. It fails with 502 gateway error sometimes. Thanks, Oleg On Fri, Jun 13, 2014 at 12:44 AM, Haataja Ismo ismo.haat...@digia.com wrote: Hi, Deployment was successful, thanks for your patience. If you find any problems, please let me know as soon as possible! Best Regards, Ismo From: development-bounces+ismo.haataja=digia@qt-project.org [mailto:development-bounces+ismo.haataja=digia@qt-project.org] On Behalf Of Haataja Ismo Sent: 12. kesäkuuta 2014 16:12 To: development@qt-project.org Subject: [Development] NOTE: Gerrit / Codereview upgrade – Service unavailable Friday June 13, 7:00 – 10:00 CEST Just to remind this will happen tomorrow morning. Hi, Gerrit (https://codereview.qt-project.org/) will be unavailable while we deploy a new version. The upgrade takes the current v2.2.1 based version to v2.7 based. Most of our customized features stay: staging system for CI, one page review and deferred changes. The topic review feature, very little used and not functioning properly, is dropped. The user experience should stay pretty much the same. There are some UI improvements, though, and of course a lot of bug fixes. Full history of how Gerrit itself has evolved between these versions can be read from Gerrit release notes (https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/index.html). Some usability related picks here. * search operators are suggested as the user types the query in the search panel * commit message can be edited from the change screen * patch sets having unpublished draft comments are highlighted with an icon There is plenty of new stuff, one needs to read the documentation for deeper knowledge. I’ll send out a follow-up once the service is online again. Regards, Ismo -- Ismo Haataja Senior Software Specialist - Digia, Qt ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtMof playground repository renaming and CI activation ?
On Fri, Mar 15, 2013 at 2:24 PM, Sandro Andrade sandroandr...@kde.org wrote: On Fri, Mar 15, 2013 at 12:37 PM, Oswald Buddenhagen oswald.buddenha...@digia.com wrote: On Fri, Mar 15, 2013 at 12:03:43PM -0300, Sandro Andrade wrote: I'm not sure whether this request is actually feasible but would we have too much impact if we rename qtmof playground repository to qtmodeling ? i have it figured out now, so actually renaming it is trivial and lossless. however, consider that there is an impact on all existing users of the repository, as they need to adjust the remote. That wouldn't generate too much noise since I'm currently the only maintainer, one other person has been testing it, and there is only one clone in gitorious. I can contact it directly whether clones aren't automatically updated. also, our new policy is to put the module in its final destination and represent its maturity via external means (wiki, etc.) (though these means are not actually implemented yet, i think). so where do you envison this repository to end up? IIRC, that's intended to become a Qt Add-On, but it still in playground. Oswald, if everything is fine could you or Sergio do the repository renaming ? Thanks, Sandro Thanks, Sandro Also, could we have CI running on it ? that's for someone else to comment on ... regards ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QtMof playground repository renaming and CI activation ?
Hi there, I'm not sure whether this request is actually feasible but would we have too much impact if we rename qtmof playground repository to qtmodeling ? If that would demand too much work to keep history consistent than I can stick with qtmof until it eventually graduates to qt repo. The reason is that qtmof have become a little bit wider, not being restricted only to MOF/UML models. Also, could we have CI running on it ? I make some sporadic integration on Windows using mingw and msvc but that is really a burden :) QtUml module is a particularly large one because of too much classes in UML meta-model. Perhaps a preliminary analysis of building impact on CI should be carried out. Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtMof playground repository renaming and CI activation ?
On Fri, Mar 15, 2013 at 12:37 PM, Oswald Buddenhagen oswald.buddenha...@digia.com wrote: On Fri, Mar 15, 2013 at 12:03:43PM -0300, Sandro Andrade wrote: I'm not sure whether this request is actually feasible but would we have too much impact if we rename qtmof playground repository to qtmodeling ? i have it figured out now, so actually renaming it is trivial and lossless. however, consider that there is an impact on all existing users of the repository, as they need to adjust the remote. That wouldn't generate too much noise since I'm currently the only maintainer, one other person has been testing it, and there is only one clone in gitorious. I can contact it directly whether clones aren't automatically updated. also, our new policy is to put the module in its final destination and represent its maturity via external means (wiki, etc.) (though these means are not actually implemented yet, i think). so where do you envison this repository to end up? IIRC, that's intended to become a Qt Add-On, but it still in playground. Thanks, Sandro Also, could we have CI running on it ? that's for someone else to comment on ... regards ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Nested namespaces and syncqt
Hi there, any suggestion about that ? Thanks, -- Sandro On Wed, Sep 19, 2012 at 3:27 PM, Sandro Andrade sandroandr...@kde.org wrote: Hi, I'm developing a qt-based implementation of an OMG specification with defines a number of classes in different (nested) namespaces. I'd be nice to have the implementation as close as possible to the spec. For that purpose, headers would be included like: #include QtMyModule/Outernamespace/Innernamespace/QMyClass Module's .pro just defines headers in a dir structure that mimics namespaces: TARGET = QtMyModule HEADERS += \ Outernamespace/Innernamespace/qmyclass.h SOURCES += \ Outernamespace/Innernamespace/qmyclass.cpp So, the questions are :) 1) It seems there are no qt modules currently using nested namespaces. Would that make my module looks somehow non qt-ish ? It'd be nice if we could have a more direct mapping between spec and implementation. 2) Provided nested namespaces are fine, how do I instruct syncqt to generate iheaders preserving original sources dir structure ? Currently iheaders are all generated in qtbase/ include/QtMyModule/, regardless their original place in source's dir structure. I have no INSTALLS directives in my .pro file. Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Nested namespaces and syncqt
Hi, I'm developing a qt-based implementation of an OMG specification with defines a number of classes in different (nested) namespaces. I'd be nice to have the implementation as close as possible to the spec. For that purpose, headers would be included like: #include QtMyModule/Outernamespace/Innernamespace/QMyClass Module's .pro just defines headers in a dir structure that mimics namespaces: TARGET = QtMyModule HEADERS += \ Outernamespace/Innernamespace/qmyclass.h SOURCES += \ Outernamespace/Innernamespace/qmyclass.cpp So, the questions are :) 1) It seems there are no qt modules currently using nested namespaces. Would that make my module looks somehow non qt-ish ? It'd be nice if we could have a more direct mapping between spec and implementation. 2) Provided nested namespaces are fine, how do I instruct syncqt to generate iheaders preserving original sources dir structure ? Currently iheaders are all generated in qtbase/ include/QtMyModule/, regardless their original place in source's dir structure. I have no INSTALLS directives in my .pro file. Thanks in advance, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Playground project request
Hi there, I'm starting the development of a Qt-based implementation of OMG's MOF specification, as part of my phd project. As far as I know there is no C++/Qt implementation of MOF, only the Java ones based on Eclipse Modelling Framework (which uses ecore instead of pure MOF). IMO, that could be useful in the future to support some model-driven capabilities in Qt Creator like automatic code generation from UML, early architectural analysis (my current focus), etc. I'd like to work upstream in Qt5 instead of providing a separate library. In addition, Qt MOF (or whatever it get named) could also be the foundation for a UML2.4.1 supporting version of Umbrello or other tools interested in model-driven approaches. So, what do you think ? Thanks, -- Sandro ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Extending QML flickable element
Hi there, I'm trying to extend QML flickable element to provide a new QML view. Building occurs fine but the generated library have some missing symbols. Any chance for building and linking against qt private headers outside qt source folders ? TIA, Sandro linux-gate.so.1 = (0xb78a3000) libgraph.so.5 = /usr/lib/libgraph.so.5 (0xb7878000) libgvc.so.6 = /usr/lib/libgvc.so.6 (0xb7802000) libQtDeclarative.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtDeclarative.so.4 (0xb748c000) libQtScript.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtScript.so.4 (0xb7206000) libQtSvg.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtSvg.so.4 (0xb71af000) libQtSql.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtSql.so.4 (0xb717) libQtXmlPatterns.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtXmlPatterns.so.4 (0xb6d7) libQtGui.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtGui.so.4 (0xb62a4000) libQtNetwork.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtNetwork.so.4 (0xb6167000) libQtCore.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtCore.so.4 (0xb5ec1000) libpthread.so.0 = /lib/libpthread.so.0 (0xb5ea6000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0xb5db7000) libm.so.6 = /lib/libm.so.6 (0xb5d8d000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb5d7) libc.so.6 = /lib/libc.so.6 (0xb5bf4000) libcdt.so.5 = /usr/lib/libcdt.so.5 (0xb5bed000) libltdl.so.7 = /usr/lib/libltdl.so.7 (0xb5be2000) libdl.so.2 = /lib/libdl.so.2 (0xb5bdd000) libxdot.so.4 = /usr/lib/libxdot.so.4 (0xb5bd9000) libpathplan.so.4 = /usr/lib/libpathplan.so.4 (0xb5bd1000) libexpat.so.1 = /usr/lib/libexpat.so.1 (0xb5ba6000) libz.so.1 = /usr/lib/libz.so.1 (0xb5b8e000) librt.so.1 = /lib/librt.so.1 (0xb5b85000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0xb5b7f000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0xb5a87000) libpng14.so.14 = /usr/lib/libpng14.so.14 (0xb5a5b000) libfreetype.so.6 = /usr/lib/libfreetype.so.6 (0xb59bf000) libgobject-2.0.so.0 = /usr/lib/libgobject-2.0.so.0 (0xb597) libSM.so.6 = /usr/lib/libSM.so.6 (0xb5969000) libICE.so.6 = /usr/lib/libICE.so.6 (0xb5952000) libXrender.so.1 = /usr/lib/libXrender.so.1 (0xb594a000) libfontconfig.so.1 = /usr/lib/libfontconfig.so.1 (0xb591b000) libXext.so.6 = /usr/lib/libXext.so.6 (0xb5909000) libX11.so.6 = /usr/lib/libX11.so.6 (0xb57d3000) /lib/ld-linux.so.2 (0xb78a4000) libpcre.so.0 = /lib/libpcre.so.0 (0xb5773000) libbz2.so.1.0 = /lib/libbz2.so.1.0 (0xb5762000) libffi.so.5 = /usr/lib/libffi.so.5 (0xb575b000) libuuid.so.1 = /lib/libuuid.so.1 (0xb5755000) libxcb.so.1 = /usr/lib/libxcb.so.1 (0xb5737000) libXau.so.6 = /usr/lib/libXau.so.6 (0xb5734000) libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0xb572e000) undefined symbol: _ZN21QDeclarativeFlickable10timerEventEP11QTimerEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable10sceneEventEP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable15geometryChangedERK6QRectFS2_ (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable11setContentXEd (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable11setContentYEd (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable16sceneEventFilterEP13QGraphicsItemP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable15mousePressEventEP24QGraphicsSceneMouseEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable14mouseMoveEventEP24QGraphicsSceneMouseEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable17mouseReleaseEventEP24QGraphicsSceneMouseEvent(./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable10wheelEventEP24QGraphicsSceneWheelEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable6tickedEv (./libqmlgraphvizplugin.so) undefined symbol: _ZNK21QDeclarativeFlickable10minXExtentEv (./libqmlgraphvizplugin.so) undefined symbol: _ZNK21QDeclarativeFlickable10minYExtentEv (./libqmlgraphvizplugin.so) undefined symbol: _ZNK21QDeclarativeFlickable10maxXExtentEv (./libqmlgraphvizplugin.so) undefined symbol: _ZNK21QDeclarativeFlickable10maxYExtentEv (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable13viewportMovedEv (./libqmlgraphvizplugin.so) undefined symbol: _ZThn8_N21QDeclarativeFlickable16sceneEventFilterEP13QGraphicsItemP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZThn8_N21QDeclarativeFlickable10sceneEventEP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZThn8_N21QDeclarativeFlickable15mousePressEventEP24QGraphicsSceneMouseEvent
Re: [Development] Extending QML flickable element
Nice, but even if I build qt with -developer-build is it a correct and reasonable way to create my flickable extended qml component ? -- Sandro On Mon, Nov 21, 2011 at 10:04 AM, shane.kea...@accenture.com wrote: class Q_AUTOTEST_EXPORT QDeclarativeFlickable The Q_AUTOTEST_EXPORT means the symbols are only available when Qt is configured as a developer build. They are exported for the unit tests to use, but not exported in a normal build. -Original Message- From: development-bounces+shane.kearns=accenture@qt-project.org [mailto:development-bounces+shane.kearns=accenture@qt-project.org] On Behalf Of Sandro Andrade Sent: Monday, November 21, 2011 11:57 To: development@qt-project.org Subject: [Development] Extending QML flickable element Hi there, I'm trying to extend QML flickable element to provide a new QML view. Building occurs fine but the generated library have some missing symbols. Any chance for building and linking against qt private headers outside qt source folders ? TIA, Sandro linux-gate.so.1 = (0xb78a3000) libgraph.so.5 = /usr/lib/libgraph.so.5 (0xb7878000) libgvc.so.6 = /usr/lib/libgvc.so.6 (0xb7802000) libQtDeclarative.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtDeclarative.so.4 (0xb748c000) libQtScript.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtScript.so.4 (0xb7206000) libQtSvg.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtSvg.so.4 (0xb71af000) libQtSql.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtSql.so.4 (0xb717) libQtXmlPatterns.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtXmlPatterns.so.4 (0xb6d7) libQtGui.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtGui.so.4 (0xb62a4000) libQtNetwork.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtNetwork.so.4 (0xb6167000) libQtCore.so.4 = /usr/local/Trolltech/Qt-4.7.4/lib/libQtCore.so.4 (0xb5ec1000) libpthread.so.0 = /lib/libpthread.so.0 (0xb5ea6000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0xb5db7000) libm.so.6 = /lib/libm.so.6 (0xb5d8d000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb5d7) libc.so.6 = /lib/libc.so.6 (0xb5bf4000) libcdt.so.5 = /usr/lib/libcdt.so.5 (0xb5bed000) libltdl.so.7 = /usr/lib/libltdl.so.7 (0xb5be2000) libdl.so.2 = /lib/libdl.so.2 (0xb5bdd000) libxdot.so.4 = /usr/lib/libxdot.so.4 (0xb5bd9000) libpathplan.so.4 = /usr/lib/libpathplan.so.4 (0xb5bd1000) libexpat.so.1 = /usr/lib/libexpat.so.1 (0xb5ba6000) libz.so.1 = /usr/lib/libz.so.1 (0xb5b8e000) librt.so.1 = /lib/librt.so.1 (0xb5b85000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0xb5b7f000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0xb5a87000) libpng14.so.14 = /usr/lib/libpng14.so.14 (0xb5a5b000) libfreetype.so.6 = /usr/lib/libfreetype.so.6 (0xb59bf000) libgobject-2.0.so.0 = /usr/lib/libgobject-2.0.so.0 (0xb597) libSM.so.6 = /usr/lib/libSM.so.6 (0xb5969000) libICE.so.6 = /usr/lib/libICE.so.6 (0xb5952000) libXrender.so.1 = /usr/lib/libXrender.so.1 (0xb594a000) libfontconfig.so.1 = /usr/lib/libfontconfig.so.1 (0xb591b000) libXext.so.6 = /usr/lib/libXext.so.6 (0xb5909000) libX11.so.6 = /usr/lib/libX11.so.6 (0xb57d3000) /lib/ld-linux.so.2 (0xb78a4000) libpcre.so.0 = /lib/libpcre.so.0 (0xb5773000) libbz2.so.1.0 = /lib/libbz2.so.1.0 (0xb5762000) libffi.so.5 = /usr/lib/libffi.so.5 (0xb575b000) libuuid.so.1 = /lib/libuuid.so.1 (0xb5755000) libxcb.so.1 = /usr/lib/libxcb.so.1 (0xb5737000) libXau.so.6 = /usr/lib/libXau.so.6 (0xb5734000) libXdmcp.so.6 = /usr/lib/libXdmcp.so.6 (0xb572e000) undefined symbol: _ZN21QDeclarativeFlickable10timerEventEP11QTimerEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable10sceneEventEP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable15geometryChangedERK6QRectFS2_ (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable11setContentXEd (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable11setContentYEd (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable16sceneEventFilterEP13QGraphicsItemP6QEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable15mousePressEventEP24QGraphicsSceneMouseEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable14mouseMoveEventEP24QGraphicsSceneMouseEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable17mouseReleaseEventEP24QGraphicsSceneMouseEven t(./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable10wheelEventEP24QGraphicsSceneWheelEvent (./libqmlgraphvizplugin.so) undefined symbol: _ZN21QDeclarativeFlickable6tickedEv (./libqmlgraphvizplugin.so) undefined symbol
