[KDE/Mac] binary compatibility
meik michalke
Meik.Michalke at uni-duesseldorf.de
Thu Mar 5 13:58:44 UTC 2015
hi rené,
tnaks for the quick resonse!
Am Donnerstag, 5. März 2015, 12:56:16 schrieb René J.V. Bertin:
> A question to start: do you have a way to build RKWard so that it simply
> installs into MacPorts, without trying to bundle all dependencies?
yes, there is an official portfile in MacPorts:
https://trac.macports.org/browser/trunk/dports/kde/rkward/Portfile
that will install 0.6.2 with MacPorts' R, though. actually, i hope it will
still fetch the sources, as we've only just recently moved the project from
sourceforge's svn to KDE's git (but 0.6.2 should still do). up-to-date
portfiles can be found in RKWard's git repo:
http://quickgit.kde.org/?p=rkward.git&a=tree&f=macports
(in the kde folder)
you can add that locally, as outlined here:
https://rkward.kde.org/RKWard_on_Mac#Pre-Requirements
MacPorts doesn't want official portfiles to use libraries outside the MacPorts
universe, so there's the portfile called "rkward" which is supposed to replace
the 0.6.2 one on MacPorts soon. then there's the portfile "rkward-devel",
providing three additional variants of the port ("rkward-devel", "rkward-
binary" and "rkward-devel-binary"); "*-binary" builds against preinstalled
binaries of R, and "*-devel" fetches the bleeding endge sources from git.
> I might be interested to check out the GUI (and see what R knowledge comes
> back after a couple of years of not using it :))
ha, you can try RKWard's dialogs and hit the "code" button to see what R code
is going to be run, to get up to speed again ;-)
> > QIODevice::setTextModeEnabled: The device is not open
>
> That's a message I've seen on 10.9 also (when running in a VM?); it doesn't
> seem to be of any consequence.
ok, then we can probably just ignore it.
> > Dynamic session lookup supported but failed: launchd did not provide a
> > socket path, verify that org.freedesktop.dbus-session.plist is loaded!
> > rkward(576)/kdeui (kdelibs): Session bus not found
> >
> > while that .plist is in the LaunchDaemons directory and appears to be
> > running (he reported).
>
> Did he show output from ps or similar, showing that the dbus is indeed
> running? Can he run standard KDE applications from MacPorts?
the postinstall script in the bundle should take care of this, but i'll try to
get more information on this.
> One more thought: I don't see any evidence of it in the port files, but
> port:dbus may install differently on 10.7 and 10.10 if you build it from
> source. If so, it's likely not to function correctly even if it runs.
if we could we'd simply build the bundle on 10.9 or 10.10 and check if that
does the trick. there are some differences between 10.7 and 10.9 which could
have an impact here (no XQuartz, different R binary package, latest XCode
version...), but we're currently stuck with 10.7. i'm tempted to install
GNU/linux on the iMac and run OS X in a virtual machine on that hardware, to
be more flexible on that side.
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: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20150305/972a9e60/attachment.sig>
More information about the kde-mac
mailing list