Regrading compilation of KDE application

[Rohan Prabhu]

Well, yeah, but building without scripted builds does touch a lot. My point
is that there are many first timers to SoK and even GSoC who are actually
unfamiliar with what exactly a 'build process' is, because most of the times
they have worked with single-target setups (or even only single-file setups)
or don't know the build process beyond what their IDE tells them.

So, this can be a welcoming step for newcomers and even others who may like
to know a bit about KDE is structured internally.

2011/5/26 karan pratap singh <wizard.karan at gmail.com>

>
>
> 2011/5/26 tushar mehta <mehtatus at gmail.com>
>
>> I think i took following suggestion in wrong way:
>>
>> 5) now build kde support and then build kdelibs :) but if you want to run
>> trunk then you need to compile kdepim-libs kdebase-apps  konsole
>> kdebase-workspace kdebase-runtime
>>
>>
> I wonder why people do not use the scripted kde builds?
>
> KDE compiles easily most of the time with kdesrc-build , and thus saves all
> the time for actual development, which people otherwise would have wasted in
> compiling each component by hand!
>
> You can easily add the modules to it which you want to build, and it just
> builds them for you :)
>
> Just my 2 cents! based on my previous experience compiling KDE....
>
>
> --
> regards,
> Karan Pratap Singh
> KDE Plasma Educational Desktop
> IRC nick: kps_foo
>
>
> _______________________________________________
> Kde-soc mailing list
> Kde-soc at kde.org
> https://mail.kde.org/mailman/listinfo/kde-soc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-soc/attachments/20110526/6cc2888d/attachment.htm