Trouble with setting up KDE build environment

[Paul Manners]

Hi Patrick,

Thanks for your reply.

I've managed to get emerge running under the kde-4.13 git branch and the
master branch.  The web docs indicated ".\kdeenv.ps1" instead of ".
.\kdeenv.ps1" as you suggested.  I copied across and modified both the
kdesettings.ini (from 4.13 branch) and kdesettings-example.bat ->
.\etc\kdesettings.bat files.  Running in the powershell, it worked first
time. For the master branch there was no kdesettings-example.bat file to
copy so I didn't use one. Easy.

KDE-4.13 was the last base that was used for the SC.  If I want to build
the lastest stable version of an existing KDE application, should I be
looking to use the master branch?  I understand that KDE/4.14 is the latest
stable release, is this correct?

Following the "Getting Started" guide again, I tried running "emerge qt" to
start bootstrapping my environment.  I did this with the master branch and
the kde-4.13 branch and the results where the same: "ERROR: The system was
unable to find the specified registry key or value. 'mt' is not recognized
as an internal or external command, operable program or batch file. emerge
error: fatal error: package gnuwin32/patch all failed".   It seems as
though this is a dependency problem - I thought emerge was supposed to deal
with all dependencies?  I have installed cmake, git, vsc2013express and of
course python so far.

Note I did make sure that I didn't mix any of the build files from
different branches - cleaned out all the directories between runs.

cheers
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-windows/attachments/20141119/ecf33d01/attachment.html>