build instructions

[meik michalke]

hi,

Am Freitag, 12. Mai 2017, 10:52:29 CEST schrieb René J.V. Bertin:
> On Thursday May 11 2017 22:13:34 meik michalke wrote:
> >i've just set up a machine with a fresh installation of El Capitan, Xcode
> >8.2>
> >and Qt 5.8. i'm now trying to follow the build instructions given here:
> > https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Mac
> 
> Exactly what is your purpose here?

in the end, build RKWard from our kf5 branch and create a binary bundle 
package from it.

> Do you want to have as-close-to-stock
> builds as possible or do you just want to have KDE applications that
> function as well (and with the largest feature-set) as possible? If the
> latter and you don't care about having all-inclusive standalone app bundles

but i do ;-)

> >CMake Error at /Users/rkward/Qt5.8.0/5.8/clang_64/lib/cmake/Qt5UiPlugin/
> >
> >Qt5UiPluginConfig.cmake:11 (message):
> >  The imported target "Qt5::UiPlugin" references the file
> >  
> >     "/Users/rkward/Qt5.8.0/5.8/clang_64/lib/QtUiPlugin.framework"
> >  
> >  but this file does not exist.  Possible reasons include:
>
> doesn't it?

no, it's not there.

> >  * The installation package was faulty and contained
> >  
> >     "/Users/rkward/Qt5.8.0/5.8/clang_64/lib/cmake/Qt5UiPlugin/
> >
> >Qt5UiPluginConfig.cmake"
> 
> Do you have that file?

yes, it's there.

does that mean the Qt installation is somehow messed up?

> I've never tried to build Phonon against stock Qt but I can assure that I've
> never had anything like that error with my own qt5-kde port (currently at
> Qt 5.8.0; Phonon at 4.9.1).

so far i'm simply trying to follow the instructions from the KDE website, they 
specifically ask for the official Qt installer. aren't those instructions 
supposed to work, then?

> >See also "/Users/rkward/software/kf5/build/qt-libs/phonon/work/mingw-w64-
> >RelWithDebInfo-4.9.1/CMakeFiles/CMakeOutput.log".
> 
> Do I understand correctly that you are using mingw? Doing a cross-build, are
> you?

no, i'm not. but now that you mention it, i was a bit surprised to see it set 
as the KDECOMPILER as the result of ". craft/kdeenv.sh" (as well as the 
windows path for python, but that doesn't seem to have any effect):

KDEROOT     : /Users/rkward/software/kf5
KDECOMPILER : mingw-w64
KDESVNDIR   : /Users/rkward/software/kf5/download/svn
KDEGITDIR   : /Users/rkward/software/kf5/download/git
DOWNLOADDIR : /Users/rkward/software/kf5/download
PYTHONPATH  : C:\ProgramFiles\Python

however, KDECOMPILER is not actually set in the environment, of those 
variables only KDEROOT seems to be present.

> Unless you know exactly what you're doing, do NOT use anything but clang to
> build on Mac.

i didn't try to do that. the configure messages also listed AppleClang as 
compiler.

> >one other thing, craft wasn't able to checkout anything at first, until i
> 
> Does craft use the "kde:" shortcut internally?

looks like it. at least, without these overrides craft failed because it 
couldn't download anything.


viele grüße :: m.eik


-- 
  dipl. psych. meik michalke
  institut f"ur experimentelle psychologie
  abt. f"ur diagnostik und differentielle psychologie
  heinrich-heine-universit"at d-40204 d"usseldorf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20170512/5b0d58d2/attachment.sig>