Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

QtWorkbench plugin

<< < (27/44) > >>

Mayler:
that's right... One time user variable didnt worked for me.

bfr:
Cool.  I set up the QTDIR variable and build the default Qt program that Code::Blocks generate.  But, when I tried to build the program I originally was having problems with (which I was told was a problem with MOC not being run), I still get the following errors:


--- Code: ---objReleasemain.o:main.cpp:(.text+0x68):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x6f):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0xdf):: undefined reference to `MainWindow::staticMetaObject'
objReleasemain.o:main.cpp:(.text+0x17f):: undefined reference to `MainWindow::staticMetaObject'
objReleasemain.o:main.cpp:(.text+0x3c8):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x3cf):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x444):: undefined reference to `MainWindow::staticMetaObject'
objReleasemain.o:main.cpp:(.text+0x4ec):: undefined reference to `MainWindow::staticMetaObject'
objReleasemain.o:main.cpp:(.text+0x77e):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x785):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x7e1):: undefined reference to `vtable for MainWindow'
objReleasemain.o:main.cpp:(.text+0x7f5):: undefined reference to `vtable for MainWindow'
:: === Build finished: 12 errors, 0 warnings ===

--- End code ---

Here is a link to the code (and by the way, I'm only building a Release target).

Is there something wrong with my code?  Or is this a problem with QtWorkBench?  Or did I not configure QtWorkBench properly?  In the "Qt Project Options" menu as part of QtWorkBench, I have "Release" checked under "Build Mode" - "Qt" checked under "Requirements" - "Core" and "Gui" checked under "Modules to Load" - and I have C:\Qt\4.2.3\bin as my directory for the moc files, uic files, and rrc files.

Mononofu:
I've also a problem with this plugin. It compiled properly (Linux + C::B from 23. 5.), but when I copy the .zip and the .so file in the share/codeblocks and share/codeblocks/plugin/ directories, I always get this error when starting Code::Blocks:
[11:14:54.724]: ERROR: /home/mononofu/.codeblocks/share/codeblocks/plugins/libqtworkbench.so: not loaded (missing symbols?)

What am I doing wrong?

greets, Mononofu

PS: I used the sources from the SVN.

yop:
Be patient. I hadn't touched the plugin for ages. I 'm changing the parser, adding a configuration dialog and the way that .pro are stored and qmake invoked. It' ll take a few days, but I think it 'll become experimentally usable under all setups. You 'll be even able to debug multiple targets :-). My thoughts:

* Parser that doesn't rely on identifiers. It will be a small simple one to start with
* 1 .pro file per target, saved in the upper level project directory (bloated but will allow debugging multiple targets as it will match to the way c::b expects Makefile based builds to act)
* The build procedure will be invoked by the c::b build menu entries
* You will have to explicitly set the build method to Makefile based

yop:

--- Quote from: Mononofu on May 26, 2007, 11:17:11 am ---[11:14:54.724]: ERROR: /home/mononofu/.codeblocks/share/codeblocks/plugins/libqtworkbench.so: not loaded (missing symbols?)

--- End quote ---
Byo was reported with the same thing some time ago for wxSmith. I don't know how he solved this, I 'll ask when we get there :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page