Use devel-package to build KDE apps from source?

[Patrick Spendrin]

Am 12.06.2012 16:45, schrieb Andreas Pakulat:
> Hi,
> 
> On Tue, Jun 12, 2012 at 4:11 PM, Andre Heinecke <aheinecke at intevation.de
> <mailto:aheinecke at intevation.de>> wrote:
> 
>     Hi,
> 
>     On Tuesday 12 June 2012 15:14:56 Andreas Pakulat wrote:
>     > Hi,
>     >
>     > I'm wondering wether it should be possible to install the Devel
>     packages
>     > from kde-win-installer and use the installed stuff to build KDE
>     apps from
>     > source?
>     Theroretically yes. Bit its not practical I do not know of anyone
>     who does
>     this and it is neither documented nor really tested. At least you
>     would also
>     need some dev utils like a compiler or cmake, perl etc. and then you
>     would
>     have to manually set up an environment. Make sure you use the right
>     build
>     options so that everything is found etc. etc.
> 
> 
> Well, I know my way around doing that, in fact I got pretty far without
> much hassle. Most of the problem was that I needed to manually select
> all the dev-packages, seems there are some dependencies missing there.
> The final problem (and why I've written that mail) seems to be that at
> least some of the devel-packages contain non-relocated cmake-code
> setting up CMake variables for libraries. So my nmake makefiles end up
> trying to link my targets against N:\Lib\kdewin.lib (or win32, don't
> know the name off-hand), which doesn't exist (I'm building in C:\KDE).

Try to find all the occurances of N:/ (in cmake files likely below
C:\kde\lib and C:\kde\share) and replace with C:/kde/ that should do the
trick.

>  
> 
>     >
>     > Or does emerge these days support installing a complete KDE
>     development
>     > environment without compiling anything?
>     No Emerge is mostly a source distribution with some binary packages
>     added for
>     convineance. But emerge is the way to go if you want to compile a KDE
>     Application from source. It is specifically designed for the task of
>     setting
>     up a development environment with all necessary tools and the
>     dependencies
>     you need. I even would encourage you to use EMERGE_SOURCE_ONLY=True
>     because
>     the binary packages are often a bit outdated.
> 
> 
> Well, thats sad, since building the whole stack is simply too much work
> upfront and also too much work for administrating if I just want to
> build/hack on a single KDE app.
> 
> I had hoped this has improved in the last 2 years :| (I'm well aware
> that KDE/Windows lacks manpower and time and whatnot, but I cannot
> afford that either beyond getting that one app into a state where I
> could use it).

Well, there are some other issues here: setting up the tools & keeping
the tools up to date is hard too if you do that by hand. Also for your
own projects, you might need to think of further dependencies, which are
not contained in the kdewin-installer (a lot of unstable libraries, etc.)
I think this depends on both projects & users (you can easily tell power
users to replace all occurances of N:/ with C:/KDE, but that is not a
solution for everybody).

> 
> 
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
> 


regards,
Patrick