Re: KDE/kdevelop

On 23.04.07 17:49:39, David Nolden wrote:
> boost-serialization -- is used for the whole messaging
system, is far superior 
> to qt's serialization-stuff, so it cannot be replaced.
The only problem, that 
> still has to be worked on, is that it creates very big
executables when 
> compiled in debug-mode.

Wow, 15 Meg is really big (that is libnetwork as static
lib).

Is the slow compilation of the actual plugin files related
to this big
library? Those files seem to compile much slower than any
other files in
kdevelop/trunk that use Qt/KDE code.

Also I just did a wc -l on the headers/cpp files: 38000
lines, that is a
really huge component. Even if I don't count the network and
dynamictext
libs its still 18000 lines.

Andreas

-- 
Keep it short for pithy sake.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 25.04.07 18:48:16, Andreas Pakulat wrote:
> On 23.04.07 17:49:39, David Nolden wrote:
> > boost-serialization -- is used for the whole
messaging system, is far superior 
> > to qt's serialization-stuff, so it cannot be
replaced. The only problem, that 
> > still has to be worked on, is that it creates very
big executables when 
> > compiled in debug-mode.
> 
> Wow, 15 Meg is really big (that is libnetwork as static
lib).

I'd like to add that linking the teamwork plugin is even
worse than
linking C++ support in KDev3 here. This is a serious
problem, are there
any options apart from building the library without debug
symbols? Is it
a gcc, boost problem? Or a problem that we can fix
ourselves?

Andreas

-- 
It's a very *__UN*lucky week in which to be took dead.
		-- Churchy La Femme

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 25.04.07 18:48:16, Andreas Pakulat wrote:
> On 23.04.07 17:49:39, David Nolden wrote:
> > boost-serialization -- is used for the whole
messaging system, is far superior 
> > to qt's serialization-stuff, so it cannot be
replaced. The only problem, that 
> > still has to be worked on, is that it creates very
big executables when 
> > compiled in debug-mode.
> 
> Wow, 15 Meg is really big (that is libnetwork as static
lib).

Well, as one can see from the commits I turned the whole
plugin to
release mode. Now it links within seconds, before it would
take >30
minutes, even if the 3 libs are built in release mode.

This way there's no chance of debugging the teamwork plugin,
so I'd like
to know how long it takes for others to link after removing
the SET
calls in the CMakeLists.txt and using BUILD_TYPE=debugfull.

Andreas

-- 
Keep it short for pithy sake.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Apr 25, 2007, at 11:48 AM, Andreas Pakulat wrote:

> On 23.04.07 17:49:39, David Nolden wrote:
>> boost-serialization -- is used for the whole
messaging system, is  
>> far superior
>> to qt's serialization-stuff, so it cannot be
replaced. The only  
>> problem, that
>> still has to be worked on, is that it creates very
big executables  
>> when
>> compiled in debug-mode.
>
> Wow, 15 Meg is really big (that is libnetwork as static
lib).
>
> Is the slow compilation of the actual plugin files
related to this big
> library? Those files seem to compile much slower than
any other  
> files in
> kdevelop/trunk that use Qt/KDE code.
>
> Also I just did a wc -l on the headers/cpp files: 38000
lines, that  
> is a
> really huge component. Even if I don't count the
network and  
> dynamictext
> libs its still 18000 lines.
>
> Andreas
>

I guarantee you that CMake support will approach 30+
thousand lines  
of code, so this is not all that big.
--
Matt



_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel