Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
QtWorkbench plugin
yop:
--- Quote from: MortenMacFly on April 10, 2006, 01:18:10 pm ---Now that you say this: Yes! That character I had to remove, too. Anyway: Within the archive I've uploaded in this forum thread this character was already removed. Which version did you use for compiling? The same question I'd like to ask to yop...?!
With regards, Morten.
--- End quote ---
Version of what?
--- Quote from: lgarrido on April 10, 2006, 01:29:05 pm ---I took it from the first posting of this thread.
Hmm, how do I add non-Qt libraries? Out of CB I include them in the .pro file, adding lines like
...
As I see in your sources, you just fire up the qmake project generator, which is ok for pure Qt but doesn't cut it for more complex projects. You could take information like this from the CB project and add it to the qmake command line so it will include it in the project file like this:
--- End quote ---
The plugin includes (or at least is supposed to) the settings from your C::B project, just add your custom settings to the Project->Build Options dialog and the plugin will generate a .pro file with your settings. I don't just fire and forget qmake, I provide a .pro file instead that "describes" the build process. I 've tested it with projects without Qt and it works just fine (though it adds -lqt in your link options but that's just something you have to live with if you use a trolltech product ;))
--- Quote from: tiwag on April 10, 2006, 02:21:53 pm ---* Run Menu QtWorkbench->Qmake-Clean, same as above, also the qt1.pro file does still exist, which i would expect to be deleted.
--- End quote ---
No it shouldn't be deleted (it would be like deleting foo.cbp from codeblocks project foo when cleaning)
--- Quote from: tiwag on April 10, 2006, 02:21:53 pm ---from what i've read in the first posting of this thread from yop , i would expect, that when running QtWorkbench->Qmake-Build
after building the *.pro file qmake would be invoked to build the makefile and afterwards running make ?? am i wrong ?
--- End quote ---
Yeap that's it, qmake is just a makefile generator that takes a configuration file as input (the .pro file). QTDIR I 'm afraid is getting outdated, I should change that (it is still there in Qt 4.x but it's not needed for the actual build process).
--- Quote from: mandrav on April 10, 2006, 03:13:06 pm --- As a sidenote, do not use wxMessageBox inside C::B and plugins. Use cbMessageBox instead which places the dialog on the correct screen for multi-head systems.
--- End quote ---
I won't don't worry :)
MortenMacFly:
--- Quote from: yop on April 10, 2006, 10:54:51 pm ---Version of what?
--- End quote ---
Version of the QTWorkspace plugin. Basically if it's the one of the first post to the thread or the one I posted. It was to see whether the XRC error is still raised allthough I've removed this NUL character. If you were able to compile and had no troubles you can safely ignore this question... which was actually intended as a hint... ;-)
With regards, Morten.
yop:
--- Quote from: MortenMacFly on April 10, 2006, 11:15:11 pm ---
--- Quote from: yop on April 10, 2006, 10:54:51 pm ---Version of what?
--- End quote ---
Version of the QTWorkspace plugin. Basically if it's the one of the first post to the thread or the one I posted. It was to see whether the XRC error is still raised allthough I've removed this NUL character. If you were able to compile and had no troubles you can safely ignore this question... which was actually intended as a hint... ;-)
With regards, Morten.
--- End quote ---
Hmm, no I haven't tried to build the one you uploaded. When i was asked some questions about the plugin I remember downloading the exact same zip file from the first post and built it without any problems.
I 'll check it out anyway thanks :)
lgarrido:
--- Quote ---The plugin includes (or at least is supposed to) the settings from your C::B project, just add your custom settings to the Project->Build Options dialog and the plugin will generate a .pro file with your settings.
--- End quote ---
That would be great! Then I must be missing something. My project depends on /usr/lib/liblrdf.so. I added "lrdf" to "Build Options | Linker | Link libraries" but this has no influence on the .pro file and the build thus fails. The "include" dirs and the "defines" do appear, though.
Luis
briahn06:
I just want to say that this plugin is awesome. As I said in a previous post, I built it, but hadn't tested it yet. I tested it, and it works flawlessly. I built it on Windows, CB (4/9).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version