[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: uic
From:       Reginald Stadlbauer <reggie () trolltech ! com>
Date:       2000-09-10 18:26:00
[Download RAW message or body]

Uic shares some code with the designer (like widgetdatabase). So
it has to be at the same place. Also if you compile uic without
kde support, then kde, then only the designer with kde support,
you still have to recompile uic with kde support too, else the code
generation for forms with kde widgets will fail.

This cross dependencies can't be really solved for this version I
fear. For the next one we have (as mentioned often alredy) plugin
support to dynamically load cusom widgets, so then kde widgets will
just be loaded as a plugin which will make all that easier.

Because of a automatic buildsystem, just do

configure and compile qt without kde support
cd qt/tools/designer/util
make
cd ../uic
make
compile kde
reconfigure qt with kde support
cd qt/tools/designer
make

Or is this not possible? Else just split the package in a way that you can
do it that way (the shared dir of the designer has to be in the uic and
designer package then)

But we will for sure not make a seperate designer tarball. Everybody who
gets Qt should get the designer as well.

On Sun, 10 Sep 2000, Michael Matz wrote:

> Hi,
> 
> On Sun, 10 Sep 2000, Matthias Elter wrote:
> > I know, but uic currently is in the designer subdir. Tell the Trolls that 
> > this is a bad idea. uic should be a part of Qt and designer should be a 
> > standalone tarball.
> 
> Yes Trolls, please (not for separate tarballs, but moving uic out of
> designer subdir).
> 
> > > Hmm, cyclic dependencies in case kdelibs ever contain .ui
> > > files (not right now). Additionally this only is an error when building
> > > for the very first time, and as only kdeui/kdecore are used, it's not
> > > impossible to use .ui files in e.g. kfile even in this case.
> > 
> > Think about building rpms in a self hosting environment. This is a problem. 
> 
> In such an environment you also can't build qt after kdelibs (which would
> be necessary for KDE widgets in designer). Only if you would split up
> designer from libqt. But then you also could have splitted uic into the
> libqt part, and the later kdelibs configure would find it.
> 
> > Ok, thanks, please apply.
> 
> Done.
> 
> 
> Ciao,
> Michael.
> 

[prev in list] [next in list] [prev in thread] [next in thread]