[Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows

[Peter Shute]

I've used the same paths as on the instruction page, so at least I won't have that problem.

How do I capture all the output?

Emerge digikam > out.txt
doesn't get it all, and
Emerge digikam > out.txt 2>&1
gave an strange error. Sorry I can't remember what it was, maybe something about a file being open.

I ran it at work, so I'll have to set it all up here at home and try again if I want to do anything more with it before Wednesday.


--------------------------
Sent using BlackBerry

----- Original Message -----
From: Andrew Goodbody <ajg02 at elfringham.co.uk>
To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users at kde.org>
Sent: Sat Jan 16 03:08:57 2010
Subject: Re: [Digikam-users] Compiling digiKam with emerge - was Compiling 1.0.0 for KDE 4.3.4 for Windows

Peter Shute wrote:
>> I set my path empty before calling kdeenv.bat just to avoid any
>> possibility of rogue tools in the path. 
> 
> I just tried that, with the same result.  I'm not sure what to try next.
> The files that are giving arrors are:
> moc.cpp
> preprocessor.cpp
> generator.cpp
> parser.cpp
> main.cpp
> I don't know what these are, but they sound important.

Can you paste into an email to the list at least part of your build 
output, starting before the first compilation error and just a bit 
after? I can only guess that you had a partial download leaving you with 
an incomplete tree. There should be some clue in the page or so before 
the first compilation error.

> Did your compilation finish successfully?  If so, how long did it take?

Yes it did finish successfully, although I have not tried it yet. I 
don't know how long it took. I kept leaving it overnight or while I was 
at work and came back to firewall popups and one time I had a bogus 
failure complaining about a file that was in use (it wasn't). It 
certainly took several hours, possibly double figures but my machine is 
not particularly quick. I also had one failure, in webkit, due to my 
%KDEROOT% being too long.

I would try:-

  emerge --unmerge qt

Then delete %KDEROOT%\download\svn-src\qt and try again. That should 
fetch qt from scratch and give you a completely fresh start.

> Just fooling around trying things, I ran "emerge digikam-support".  It fails because it can't find http://saroengels.net/kde-windows/gnuwin32/digikam-support-0.2.0.tar.bz2.  It appears that in saroengels.net/kde-windows the directory gnuwin32 doesn't exist.  I don't know if this is related to the compilation problem.

That fails for me as well so cannot be related.

BTW the build also failed for me when I had the download directory 
outside of %KDEROOT% as some Makefiles ended up with some incorrect 
relative paths in them instead of absolute paths.

Andrew
_______________________________________________
Digikam-users mailing list
Digikam-users at kde.org
https://mail.kde.org/mailman/listinfo/digikam-users