News on Krusader for Mac

324 views
Skip to first unread message

Jonas Bähr

unread,
Dec 21, 2008, 5:09:55 PM12/21/08
to krusade...@googlegroups.com
Hi,

My first attempts for making Krusader available for Mac OS X where
based on fink [1], which was quite complicated and involved a lot of
manual steps.
Recently I tried out MacPorts [2] which I like much more. It is
inspired by the BSD port system and provides i.e. package variants
like the gentoo's portage USE-flags and can be used to create binary
installers for every package. Some weeks ago, Portfiles for kde4 have
been added and the installation is now as easy as

$ sudo port install kdebase4-runtime

Well, at least that's the theory. I created some patches for the kde4
portfiles, containing mainly missing dependencies. These have been
already included by the maintainer so it should be fine now. The last
stumbling block is that Qt4 has to be installed with the ssl variant,
else kdelibs4 fail to compile.
So, now you can either add "+ssl" to the default variants in /opt/
local/etc/macports/variants.conf, or simply install Qt with this
variant before kde4

$ sudo port install qt4-mac +ssl
$ sudo port install kdebase4-runtime

I've also created a Portfile for Krusader [3] with the goal that at
the time of releasing the final Krusader-2.0.0, the installation on
Mac OS X consists only in

$ sudo port install krusader

(after having installed MacPorts, obviously)

[1] http://www.finkproject.org
[2] http://www.macports.org/
[3] http://trac.macports.org/ticket/17731

bye,
Jonas

Jonas Bähr

unread,
Jan 6, 2009, 2:49:07 PM1/6/09
to krusade...@googlegroups.com
Hi,

You can now find the Portfile for beta2 at http://trac.macports.org/ticket/17731

bye,
Jonas

Ionut

unread,
Jan 26, 2009, 3:59:02 PM1/26/09
to krusader-devel
Hi,
I'm not sure what to understand from this post.. Is krusader already
available ? Or do I need to wait until the 2.0 version becomes
available ?

When I give this command:

sudo port install krusader

I'm receiving:

Error: Port krusader not found


Thank you.


On Jan 6, 9:49 pm, Jonas Bähr <jonas.ba...@web.de> wrote:
> Hi,
>
> You can now find the Portfile for beta2 athttp://trac.macports.org/ticket/17731

Jonas Bähr

unread,
Jan 26, 2009, 5:57:25 PM1/26/09
to krusade...@googlegroups.com
Hi,

Am 26.01.2009 um 21:59 schrieb Ionut:

>
> Hi,
> I'm not sure what to understand from this post.. Is krusader already
> available ? Or do I need to wait until the 2.0 version becomes
> available ?

The Portfile is not yet in the official tree. However, I gained
macports commit rights recently and "sudo port install krusader" will
work from the moment we released 2.0

Till then you either have to download the Portfile manually from http://trac.macports.org/ticket/17731
or "sudo port install kdebase4-runtime" and then compile Krusader
yourself. The above command should pull in all the dependencies and
you can get a more recent version of Krusader via SVN.

bye,
Jonas

andrabr

unread,
Feb 10, 2009, 9:20:54 PM2/10/09
to krusader-devel
Jonas,

It appears that the problem from Ticket #17789 ("can't find qmake-
mac") http://trac.macports.org/ticket/17789 is back in the Portfile
for Beta2 - I get the same error: " 1485 (MESSAGE): Qt qmake not
found!".

Manually applying the changes from Changeset 44375 (
http://trac.macports.org/changeset/44375 ) seems to fix the problem.

Another problem manifests itself though and makes me wonder if I am
supposed to be applying your CMakeLists.txt patch. It is clearly
designated " for the krusader-2.0.0-beta1 Portfile ", So I am holding
off till you tell me that it's the way to go.

You probably want to issue a new release of Beta2 Portfile with all
the improvements - not everybody gets excited about applying
patches ;-)

Either way, MANY THANKS for keeping this going - I can't wait to
reunite with krusader on my Mac!

~Andrey

On Jan 6, 11:49 am, Jonas Bähr <jonas.ba...@web.de> wrote:
> Hi,
>
> You can now find the Portfile for beta2 athttp://trac.macports.org/ticket/17731

andrabr

unread,
Mar 6, 2009, 12:12:41 AM3/6/09
to krusader-devel
Followup:

I took a look at CmakeLists.txt and it looks like the patch from Beta1
has already been applied.

Still, there seems to be a problem (see output below):
==============================================================

---> Configuring krusader-devel
Error: Target org.macports.configure returned: configure failure:
shell command " cd "/opt/local/var/macports/build/
_Users_andrabr_MacPorts_kde_krusader-devel/work/build" && cmake --
prefix=/opt/local ../krusader-2.0.0-beta2 -DCMAKE_VERBOSE_MAKEFILE=ON -
DCMAKE_BUILD_TYPE=Release -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr"
-DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_OSX_SYSROOT=/Developer/SDKs/
MacOSX10.5.sdk -DQT_QMAKE_EXECUTABLE=/opt/local/libexec/qt4-mac/bin/
qmake -Wno-dev " returned error 1
Command output: CMake Internal Error (please report a bug) in
CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__kdeui


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__kio


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__solid


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__kdecore


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__kdeui


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__kio


CMake Internal Error (please report a bug) in CMakeLists.txt:
GetLibraryNamesInternal called on imported target: KDE4__solid


-- Generating done
-- Build files have been written to: /opt/local/var/macports/build/
_Users_andrabr_MacPorts_kde_krusader-devel/work/build

Error: Status 1 encountered during processing.

Jonas Bähr

unread,
Apr 19, 2009, 6:20:20 PM4/19/09
to krusade...@googlegroups.com
FYI
Krusader is now part of macports: http://trac.macports.org/changeset/49908

The installation on Mac OS X should now be as easy as `sudo port
install krusader`
After the installation of macports, of course. All dependencies should
be pulled automatically. Since it's a source distribution, the first
installation can take some time since Qt4 and kdelibs4 have to be
compiled. However, the result is a 100% native Krusader on Mac ;-)

bye,
Jonas

Christophe Mourette

unread,
Jun 5, 2012, 9:03:08 AM6/5/12
to krusade...@googlegroups.com
after  sudo port install krusader

i had this error :

:info:build   "Solid::StorageAccess::teardown()", referenced from:
:info:build       KMountMan::unmount(QString, bool)in libMountMan.a(kmountman.o)
:info:build       MediaButton::umount(QString)      in libGUI.a(mediabutton.o)
:info:build   "Solid::StorageAccess::setup()", referenced from:
:info:build       KMountMan::mount(QString, bool)in libMountMan.a(kmountman.o)
:info:build       MediaButton::mount(QString, bool, bool)in libGUI.a(mediabutton.o)
:info:build ld: symbol(s) not found for architecture x86_64
:info:build collect2: ld returned 1 exit status
:info:build make[2]: *** [krusader/krusader.app/Contents/MacOS/krusader] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build'
:info:build make[1]: *** [krusader/CMakeFiles/krusader.dir/all] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build" && /usr/bin/make -j8 -w all 
:info:build Exit code: 2
:error:build org.macports.build for port krusader returned: command execution failed
:debug:build Error code: CHILDSTATUS 42447 2
:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: targets not executed for krusader: org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Please see the log file for port krusader for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/main.log
Reply all
Reply to author
Forward
0 new messages