Ole Christian Eidheim

@junrrein Let me know if you manage to build juCi++ with lldb support on OpenSuse. It seems to be missing the lldb header files. And feel free to add OpenSuse...

Thank you for adding this. I got the following issue however: PATH was not correctly set when starting the application from the OS X search (top right corner of screen)....

I guess we could add /usr/local/bin to PATH when starting juci on OS X. Maybe add a symbolic link, when doing make install, from /usr/local/bin/juci to /usr/local/bin/juCi++.app/Contents/MacOS/juCi++ so it's similar...

At least to me, and many developers on OS X, homebrew is essential. I'm thinking that juCi++ could be installable with `brew install jucipp` someday. However, your changes makes juCi++...

Sorry for being late on this. Still considering what to do here. An OS X package is nice, but it brings extra complexity which may lead to issues in the...

I think CPACK is the way to go on OS X as well: https://cmake.org/Wiki/CMake:CPackPackageGenerators#Bundle_.28OSX_only.29. Then the need of the symbolic link goes away, since a normal `make install` will work...

See https://cmake.org/Wiki/CMake/CPackExample for an simple example (although DEB).

I've added CPack now, and once I figure out how to setup the OS X bundle using CPack I'll merge this most likely (the Info.plist is still needed if I'm...

Could you elaborate please? In which case does autocomplete not work in C/C++ header files?

Not sure if libclang will support this in the future, but I think I read about a couple of alternatives for completing headers last year, but I do not think...