Re: KDevelop on Apple OS X

2014-03-17 Thread mk-lists
Hi Ian, On 17 Mar 2014, at 01:20 , Ian Wadham wrote: > Alexander Dymo (adymo) is one of two former KDE developers now working on > Homebrew. > And he was one of the original developers of KDevelop. I remember him from > back then. > Do you fancy some "bridge building", Marko? I’ll will contac

Re: KDevelop on Apple OS X

2014-03-17 Thread mk-lists
Hi Aleix, On 17 Mar 2014, at 00:54 , Aleix Pol wrote: > 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]. Oh, I see now. I had realised that they had been moved a while ago. But when check

Re: KDevelop on Apple OS X

2014-03-16 Thread Ian Wadham
Hi Marko, On 17/03/2014, at 10:54 AM, Aleix Pol wrote: > 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],

Re: KDevelop on Apple OS X

2014-03-16 Thread Aleix Pol
On Sun, Mar 16, 2014 at 10:02 PM, 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 questi

Re: KDevelop on Apple OS X

2014-03-16 Thread mk-lists
On 16 Mar 2014, at 22:02 , mk-li...@email.de wrote: > What I did was that I set up a project via “Project/New From > Template…/Project Type/Graphical”. Turns out I was creating a template for a QML application. I just tried a "Graphical C++ KDE” with the same sad result. But when I tried

KDevelop on Apple OS X

2014-03-16 Thread mk-lists
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