Mac Binaries

[Pecan]

In the wiki "Compiling Code::Blocks in Mac OS X" it states
that the user has to install Xcode Tools from http://developer.apple.com/tools/.

Yet I can find no xtools to download that will run on any system other than
OS X 10.4. It states that Xtools 2.2 will run on no earlier OS X system. And,
evidently, apple has hidden any earlier versions of the tools.

Yet the wiki also says that this (wiki) system has been tested on OS X 10.3.

To follow these instructions, where can we find a version of Xtools
(or the necessary apple tools) that will work on OS X earlier than 10.4 (tiger)
and allow us to build CB?

thanks
pecan

[afb]

In the wiki "Compiling Code::Blocks in Mac OS X" it states
that the user has to install Xcode Tools from http://developer.apple.com/tools/.

Yet I can find no xtools to download that will run on any system other than
OS X 10.4. It states that Xtools 2.2 will run on no earlier OS X system. And,
evidently, apple has hidden any earlier versions of the tools.

Apple pulled all the old links in order to promote Mac OS X 10.4, but all the
old developer tools can be downloaded from ADC at http://connect.apple.com/

You need a (free) developer registration with Apple first, in order to log in there.
For Mac OS X 10.3, you want Xcode 1.5. For Mac OS X 10.1-10.2, latest Dev Tools.

[Pecan]

Apple pulled all the old links in order to promote Mac OS X 10.4, but all the
old developer tools can be downloaded from ADC at http://connect.apple.com/

You need a (free) developer registration with Apple first, in order to log in there.
For Mac OS X 10.3, you want Xcode 1.5. For Mac OS X 10.1-10.2, latest Dev Tools.

Thanks, getting it!

I'm off to downloading at 48k/sec light speed for 31 hrs.
Half the time of the Ubunto download though.

thanks
pecan

[Mithos]

I did made a Mac OS version also. But since I made a full package including many things (basicaly many things not needed) It it too big to distribute right now. But it is the last svn source and has not many visual bugs that I could find. The only major problem is the debugger witch isn´t working yet.

[afb]

I did made a Mac OS version also. But since I made a full package including many things (basicaly many things not needed) It it too big to distribute right now. But it is the last svn source and has not many visual bugs that I could find. The only major problem is the debugger witch isn´t working yet.

Sounds good! (you could always post a screenshot?)

Did you have to make many new modifications ?
And which version of wxWidgets were you using ?

Trying to build the 2341 revision here right now.

[Mithos]

Version 2.6.3

Not big modifications but I had to suffer a little to get all the right libs on 10.3 witch is my os.

Screen Shots I could post if I had installed any image manipulation programs in this machine. I will fix this in the next days and post one

[Mithos]

HA I made the compiler work .... hehehehehe just a small adjustment was needed (mac gdb needs run instead of start) and now it works...

Well haven´t checked all windows in compiler but at least the basic works. Code blocks running smooth in MacOS :-)

[mandrav]

Code blocks running smooth in MacOS :-)

Great!
And the patch is... where? :lol:

[Mithos]

Bascialy what you need is this change in src/plugins/debuggergdb/gdb_driver.cpp

change

Code Select Expand

#ifdef __WXMSW__
    m_BreakOnEntry = false;
    m_ManualBreakOnEntry = false;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("run")));
#else
    m_BreakOnEntry = breakOnEntry;
    m_ManualBreakOnEntry = true;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("start")));
#endif



for this

Code Select Expand

#ifdef __WXMSW__
    m_BreakOnEntry = false;
    m_ManualBreakOnEntry = false;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("run")));
#else

#ifdef __WXMAC__
    m_BreakOnEntry = false;
    m_ManualBreakOnEntry = false;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("run")));
#else
    m_BreakOnEntry = breakOnEntry;
    m_ManualBreakOnEntry = true;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("start")));
#endif
#endif


[Mithos]

I can distribute my CodeBlocks.app but it is too big right now. I think because I must have compiled things with -g on.

Wen I have some spare time I can see if I re-compile it for size reduction. I´m also planing a plugin to create mac aplications directly with default Structure because without it doesn´t work well. But this should be simple after I study a little the framework for this.

[takeshimiya]

Reduced ver.:

Code Select Expand

#if defined (__WXMSW__) || defined (__WXMAC__)
    m_BreakOnEntry = false;
    m_ManualBreakOnEntry = false;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("run")));
#else
    m_BreakOnEntry = breakOnEntry;
    m_ManualBreakOnEntry = true;
    // start the process
    QueueCommand(new DebuggerCmd(this, _T("start")));
#endif

[mandrav]

Bascialy what you need is this change in src/plugins/debuggergdb/gdb_driver.cpp

I wasn't asking about the debugger, but about anything else you had to do to make it work. According to afb's posts, C::B had layout problems in MAC. Have you solved them? Did you do anything special? That's the patch I 'm talking about

[Mithos]

Well I had lot´s of problems to make autoconf and automake works right. But wat I did was basicaly folow what is described on this link and use wxwidgets 2.6.3.


There was some problems with libtool. But basicaly what you need to do is use dynamic libs.


There are some minor problems like the stats on the windows not refreshing right. Those I will try to look better latter but apears to be wxwindows bugs.

It took me something like 3 days to make it work like I wanted. I should have donne somthing like a walk trought with all that was needed. Well if can help anyone latter I will

[afb]

Well I had lot´s of problems to make autoconf and automake works right. But wat I did was basicaly folow what is described on this link and use wxwidgets 2.6.3.

It still looks "bad" in wx 2.6.1, so I will try upgrading to 2.6.3...

What problems did you have with autoconf/automake/glibtool ?
Beyond the need for a newer version, I didn't have any of those.

[Mithos]

They didn´t reconized some installed features and I had a problem making them build the right dynlib

But just some configuration paramters. And needing to upgrade wasn´t so funny :-)