Author
Topic: Installing and Running on MacOS Catalina - So Far So Good (Read 231 times)

I'm experimenting with Code::Blocks with the idea of using it for Raspberry Pi development, and I thought I'd try it out on my Mac first. Since the current version doesn't work well on the Mac I thought I'd give some running commentary on my progress.

1. Starting with the linux build instructions.2. Installed autoconf and automake using Homebrew3. Since wxWidgets isn't installed system-wide, the aclocal path had to be updated -- the wxWidgets .m4 file is in the root of the wxWidgets directory.4. Code::Blocks builds, installs to /usr/local, and runs without a hitch.5a. No project templates. It looks like the Mac build expects plugins to be in ~/Library/Application Support/codeblocks/...5b. Symlinked the Library 'plugins' folder to the one in /usr/local. Now I have project templates.6. Made a simple "Hello World!" console project.7. Code::Blocks runs clang, but generates no output and reports "GetCFStringRef, i is not the right type". On the plus side, it properly created the build directories.

And that's where I am so far. I'll post further developments as I work through problems.

Both GCC and Clang give the same results: it seems the build process is hanging somewhere, which is causing the project settings and whatnot to be disabled. Aborting the build doesn't work, and quitting Code::Blocks requires a force quit, so my guess is something in the compiler plugin is locking up for reasons, potentially related to the "GetCFStringRef, i is not the right type" message.