build instructions

[René J.V. Bertin]

On Friday May 12 2017 11:58:49 meik michalke wrote:

>> latter and you don't care about having all-inclusive standalone app bundles
>
>but i do ;-)

Then I can't help you much.

Can RKWard be built without a (fully functional) R install present? It sounds like something I might want to add to my ports collection, but I no longer have any personal use for R and don't particularly care for spending lots of time and energy on otherwise pointless dependencies.

>no, it's not there.
>> >  * The installation package was faulty and contained
>yes, it's there.
>
>does that mean the Qt installation is somehow messed up?

I'd say so. I do have the framework in my 5.9 RC stock install.
I don't think the 5.9 release is going to take a lot of time so you could just use the RC instead of 5.8.0 (there won't be 5.8.1).
Unless you want to support OS X 10.9 .

>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?

I guess they are but they're probably not kept up-to-date. As far as I'm concerned you cannot get a feature-complete KDE experience with stock Qt on Mac so I use a patched Qt5 that has a QStandardPaths class that returns the familiar XDG-compliant standard locations plus a bunch of other tweaks. What I care for is KDE applications that work as much as possible as they do under Linux, that use shared resources and that support configurable look-and-feel.
If it weren't for that I'd probably have been able to update those instructions.

>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):

It looks like craft assumes that not running on Linux means you must be running MS Windows ...

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

OK.

R.