User forums > Help

Codeblocks on MAC OS Catalina

<< < (2/3) > >>

anb:
I have now managed to successfully build and run the latest C::B from trunk on Mojave, so thank you very much.  It has only just finished building, and it runs.  I haven't really done anything else beyond that yet so will use it properly tomorrow.

If all goes well then I will look at putting together a proper Mac app for it tomorrow.  I guess it would be useful for many others if I share this somehow.  Any suggestions?  I have my own website(s) I could use.

Miguel Gimenez:
Very few users have MAC OS, and most developers do not use it. Any help of a skilled user would be a benefit. User Xaviou creates nightlies for MAC OS, but I have seen little feedback from users. See http://forums.codeblocks.org/index.php/topic,23973.msg163511.html#msg163511 for more details on this.

From http://www.codeblocks.org/downloads/binaries:

--- Quote ---Code::Blocks 20.03 for Mac is currently not available due to issues caused by Apple hardening their install packages and lack of Mac developers. We could use an extra Mac developer to work on these issues.
--- End quote ---

oBFusCATed:
Shipping a version for mac requires Paid Apple developer account. Without it we cannot apply the new hardening required in the latest OS.
But this is the least of our concerns, we need someone to use this software on a daily basis and fix the problems which are macOS specific.
I use it from time to time, but I don't plan to spend too much fixing macOS issues.

Using the latest wx dev release and the latest code from trunk should work fine. If it doesn't please post the build steps/commands you're using and the build log. I'll try to help you.

anb:

--- Quote from: oBFusCATed on September 16, 2020, 08:23:08 pm ---Shipping a version for mac requires Paid Apple developer account. Without it we cannot apply the new hardening required in the latest OS.

--- End quote ---

Yes, that is a pain.  My work need to port some Windows apps to Mac and it is proving to be a painful process.

Our development environment for the Mac is on Mojave.  It's a long story.  So I am fine running the builds from Xaviou.


--- Quote from: oBFusCATed on September 16, 2020, 08:23:08 pm ---But this is the least of our concerns, we need someone to use this software on a daily basis and fix the problems which are macOS specific.
I use it from time to time, but I don't plan to spend too much fixing macOS issues.

--- End quote ---

I'll be pretty much the same, to be honest.  I just need to use it to port our Windows apps and libraries to the Mac.  But I imagine we'll end up doing more and more work on the Mac as time passes.

I can certainly report issues, etc.


--- Quote from: oBFusCATed on September 16, 2020, 08:23:08 pm ---Using the latest wx dev release and the latest code from trunk should work fine. If it doesn't please post the build steps/commands you're using and the build log. I'll try to help you.

--- End quote ---

As I said yesterday, it built fine and ran fine.  Although, when I came to use it this morning it wouldn't open a project.  It moaned about turning off the compiler, or something like that.  I built C::B with no plugins so I assumed that was the cause so tried to build it with all plugins but that failed to build.  At that point I saw your post about Xaviou builds so I downloaded one of those and that is working fine so far.

If issues do crop up then I may be able to look in to them but it depends if I have time.  I spent far too long messing with this yesterday that I had to find another app.  I ended up using CodeLite but that is nowhere near as good as C::B, but at least it wasn't crashing constantly for me.

My configure command line is:


--- Quote ---./configure --prefix=/Volumes/Mac_USB_2TB/MacStuff/CodeBlock_Trunk/ --enable-unicode --enable-debug --disable-shared --disable-mediactrl

--- End quote ---

With this, it builds fine and runs but I can't open any project.  It also never asks me about compilers when launching.

anb:
Whilst build 12198 is running and I can happily edit files, and it seems far more stable, I unfortunately cannot build/compile anything.  When I do so the command line appears in t he Build Log window but then nothing happens, and C::B thinks it is still building.  I cannot abort it either.  I have to completely kill the app.

Copying and pasting the command line to a Terminal runs fine, so the command line is correct.

This is happening on every file I try to build.  Any ideas?

If we can get my source building correctly then I can at least look in to some of these issues.  I can also use the very latest code too (12201).

Navigation

[0] Message Index

[#] Next page

[*] Previous page