On Sun, Mar 16, 2014 at 10:02 PM, <mk-li...@email.de> wrote:

> Hi devs,
>
> after having installed kdesdk4 successfully MacPorts needed only about 30s
> to install the residual handful of ports required by KDevelop.
>
>         Now there is KDevelop 1.6.0 up and running. :)
>
> Well, before going further with questions I wonder whether I should
> address them to KDevelop’s mailing list (which seems to be quite dead) or
> rather stay here on KDE-DEVEL for the moment, since I am not sure whether
> it is a Mac specific issue or not.
>
> What I did was that I set up a project via “Project/New From
> Template…/Project Type/Graphical”.
> After running into a little issue with the temlate [1] I was able build
> the generated code with some warnings, but without a real error. :-)
>
> When I now start the application from the built app package I
> unfortunately get an error:
> —
> $ ./testgraphical
> file:///Users/marko/projects/TestGraphical/build/src/testgraphical.app/Contents/MacOS/:
> File not found
> Killed: 9
> —
>
> I am surprised to see a message like this on the console. What does this
> mean? Which file does the app try to load and why does it fail to do so?
>
> KDevelop doesn’t allow me to step through the code in debug mode, so that
> I cannot say where exactly the issue occurred.
>
> I could imagine that the app tries to access its configuration which is
> stored on MacOSX in ~/Library/Preferences/KDE :
> —
> $ pwd
> /Users/marko/Library/Preferences/KDE/share/apps
> $ ls -1
> RecentDocuments
> desktoptheme
> dolphin
> Kate
> kdenlive
> kdevappwizard
> kdevelop
> kfileplaces
> khelpcenter
> kssl
> plasma
> remoteview
> —
> As one can see, kdevelop itself already stores its stuff in there.
>
> I am clueless right now about how to further proceed. Hope you can push me
> into the right direction.
>
> Greets,
> Marko
>
>
>
> [1] https://bugs.kde.org/show_bug.cgi?id=329392
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>

Hi Marko,
First of all, KDevelop mailing lists are not dead, we did change our
mailing list to kde.org infrastructure, you might have looked at the wrong
place [1].

We have some people already using KDevelop through homebrew on Mac OS X
[2], maybe using the same tools Alexander used will help, at least with the
first bug.

Regarding the second one, it clearly seems like it's a bug in the cmake
integration. It hasn't been tested on Mac before so it can be just as well
that you're the first person trying that. Some further investigation will
be very much welcome. I would suggest following up in the kdevelop-devel
mailing list would be the best.

Cheers!
Aleix

[1] http://kdevelop.org/mailinglists
[2] https://github.com/adymo/homebrew-kde
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to