On 09.11.05 16:04:46, Brian Nelson wrote: > Andreas Pakulat <apaku@gmx.de> writes: > > > today I was struck by designer and release vs. debug built of Qt4. I > > have a Custom Widget which is visible in designer when I have no logic > > in it. But it completely "breaks" designer if I put the real code in it, > > the solution to this is that the widget uses a shared library. This > > library is built in debug mode (the custom widget is built with release > > mode) and that was the cause. Now I have to built the widget in release > > mode, because Qt4 was built using release or the combined release+debug > > building mode (in which case, designer gets built in release mode). > > Designer can thus only load widgets which are built in the same mode as > > designer itself and as you can see all libraries these widgets depend > > upon need to use release built too. > > > > So the conclusion is: Please provide 2 designer packages, one using > > release built and one using a debug-only built of Qt4. I know this means > > building Qt4 twice for each update, but it's not possible to debug any > > custom widget in the current setup due to the missing debug symbols. > > I'd rather wait and see what kind of improvements go into the designer > in Qt4.1. The current version has proven to be very buggy, and this > seems like something that should definitely be supported by a single > designer binary. Ok, I can live with that (as Qt 4.1 shouldn't be too far away) and in the meantime I'll either use self-compiled Qt4 in my $HOME or rebuilt the qt4-package in debug-mode only (changing debian/rules)... Thanks for the fast answer. Andreas -- Live in a world of your own, but always welcome visitors.
Attachment:
pgpgHXJbVF_Dp.pgp
Description: PGP signature