List Info

Thread: Removing some things from C++ parser




Re: Removing some things from C++ parser
user name
2007-07-26 10:53:07
On 26.07.07 10:33:04, Matthew Woehlke wrote:
> Andreas Pakulat wrote:
> > On 25.07.07 23:29:57, Matt Rogers wrote:
> >> I'd recommend having a shared library that
contains all the parser  
> >> stuff which the tests can link against rather
than pulling in the  
> >> sources for the particular things to test. You
would also be able to  
> >> link the plugin against the shared library as
well. There's nothing  
> >> saying that any installed shared library has
to have public headers,  
> >> so we can just not install those and be ok.
> > 
> > This is not just about the parser lib, but a
general problem. The thing
> > with installing a shared library is that whenever
somebody changes the
> > code in a BIC manner the version has to be
increased (AFAIK at least),
> > which might be forgotten easily. 
> 
> Even when the only thing linking against it is always
distributed at the 
> same time?

I'm not sure. I think that when a shared library (wether
used or not)
breaks ABI it needs to increas its soversion. But I'm really
no expert
on this.

> > I'm wondering wether there's a way to
> > tell cmake to not recompile the sources for the
tests, which IMHO is the
> > only benefit of using a shared lib for the parts
of the plugin.
> 
> The "convenience library" thing comes up
frequently, last I checked 
> there is no easy way to do it (so said the wiki
anyway). Is it possible 
> to make a static library instead? (Only the plugin and
test apps use it, 
> right? In which case the increased code size is not an
issue.)

No, static libs are a no-go - AFAIK. It needs -fPIC on 64bit
systems in
various places... Tried that for the python plugin, didn't
work very
well.

Andreas

-- 
This life is yours.  Some of it was given to you; the rest,
you made yourself.

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

Re: Removing some things from C++ parser
user name
2007-07-26 11:21:15
On 26.07.07 11:01:27, Matthew Woehlke wrote:
> Andreas Pakulat wrote:
> > On 26.07.07 10:33:04, Matthew Woehlke wrote:
> >> The "convenience library" thing
comes up frequently, last I checked 
> >> there is no easy way to do it (so said the
wiki anyway). Is it possible 
> >> to make a static library instead? (Only the
plugin and test apps use it, 
> >> right? In which case the increased code size
is not an issue.)
> > 
> > No, static libs are a no-go - AFAIK. It needs
-fPIC on 64bit systems in
> > various places... Tried that for the python
plugin, didn't work very
> > well.
> 
> Well obviously it needs -fPIC, you're putting it into a
shared library 
> ultimately . What was
the problem with using -fPIC?

I don't really know why, I guess you'd have to ask on
kde-devel or
-core-devel.

Andreas

-- 
Communicate!  It can't make things any worse.

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

Re: Removing some things from C++ parser
user name
2007-07-26 21:18:18
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jul 26, 2007, at 12:07 PM, Andreas Pakulat wrote:

> On 26.07.07 11:51:10, Matt Rogers wrote:
>> On Jul 26, 2007, at 5:14 AM, Andreas Pakulat
wrote:
>>> This is not just about the parser lib, but a
general problem. The
>>> thing
>>> with installing a shared library is that
whenever somebody  
>>> changes the
>>> code in a BIC manner the version has to be
increased (AFAIK at  
>>> least),
>>> which might be forgotten easily. I'm wondering
wether there's a  
>>> way to
>>> tell cmake to not recompile the sources for the
tests, which IMHO
>>> is the
>>> only benefit of using a shared lib for the
parts of the plugin.
>>>
>>> Andreas
>>
>> You don't have to version shared libraries.
Especially ones that are
>> internal to KDevelop anyways.
>
> So always use soversion=0? Or do you mean setting no
soversion at all?
> What will come out of that?
>
> /me is still no lib-guru 
>
> Andreas
>
> -- 

don't set an so version. In doing so, you'll always have a
library  
called libfoo.so (for example).
- --
Matt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFGqVXrA6Vv5rghv0cRAgesAJ0U68jc5401Y6WF817w1F6SyKAhqgCd
EyA/
wXkexcjFBmh9GJxlGUlrDFM=
=iBn3
-----END PGP SIGNATURE-----

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

[1-10] [11-13]

about | contact  Other archives ( Real Estate discussion Medical topics )