With fresh morning head I figured it
Visibility=KINPROJECT_EXPORT
IncludeFiles="kprojectexport.h"
in kcfgc file do the trick. Thanks again.
--
Regards,
Anatoli.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Thanks Thomas,
I thought this macro is more of a compile time rather then linkage time thing,
but apparently not. The reason I actually put a wrapper around was to do the
KDE_EXPORT macro. It did not help. It saw the exported wrapper fine, but
failed to find the insider code. But after your pos
Anatoli,
On Thursday 26 July 2012 12:44:02 Anatoli Gorchetchnikov wrote:
> Hi all,
>
> I have three types of projects my app can handle, so I have three respective
> parts that are loaded depending on the project type. They have some common
> functionality and settings, so these I separated in t
Hi all,
I have three types of projects my app can handle, so I have three respective
parts that are loaded depending on the project type. They have some common
functionality and settings, so these I separated in the base class KProject
derived from KReadWritePart plus some other stuff, put it a
On quinta-feira, 26 de julho de 2012 07.59.35, Carlos Ernesto Alies Fuentes
wrote:
> }The question is about the pointers usage here.cafu
Yes, it's wrong. Feel free to edit the wiki to make it consistent.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect -
Hi All,Greetings my first post, hopefully helpful for someone else besides
myself.I am facing difficulties trying to understand the wiki page
Policies/Binary Compatibility Issues With C++ in the sectionAdding new data
members to classes without d-pointer. I think the docu is wrong (please for
The CMake 2.8.9 release candidate stream continues! You can find the
source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
This email is also available on the Kitware blog:
http://www.kitware.com/blog/home/post/342
Some of the notable changes in this release are:
- the new N
