2011/6/27 Nicolas Alvarez
> I don't know if this is intended behavior, but as far as I can tell,
> kdelibs
> built with and without KDE_NO_DEPRECATED have *incompatible ABIs*. So there
> will be problems if kdelibs is built with it defined and the app without
> it,
> or viceversa.
>
This makes s
JonAnder Peñalba wrote:
> I've been doing some experiments with the KDE_NO_DEPRECATED define and I
> have some doubts.
>
> What is it exactly supposed to mean?
> As I understand it, when compiling with this define, all deprecated code
> should be ignored and the application should work as expected
2011/6/23 Raphael Kubo da Costa
> JonAnder Peñalba writes:
>
> > This is not the result I get. When I compile with this define, I get
> strange
> > results that vary from weird behavior to segfaults.
>
> Are you sure these are related to KDE_NO_DEPRECATED?
>
Pretty sure yes.
For example, this
JonAnder Peñalba writes:
> This is not the result I get. When I compile with this define, I get strange
> results that vary from weird behavior to segfaults.
Are you sure these are related to KDE_NO_DEPRECATED? Do you have some
backtraces, more details about the weird behavior you experience and
Hi,
I've been doing some experiments with the KDE_NO_DEPRECATED define and I
have some doubts.
What is it exactly supposed to mean?
As I understand it, when compiling with this define, all deprecated code
should be ignored and the application should work as expected. So if an
application builds w
