User forums > Help

Code::Blocks on MacOSX

<< < (2/5) > >>

bnilsson:
I was maybe a little too quick to announce total MacOSX success, one remaining issue is wxSmith.
The current version is consuming most of the available memory when opening a .wxs file, this is now a known problem for MacOSX.
As a Mac owner, I have offered byo that I look into it, but due to my very limited experience in wx programming I expect it to take (long) time. If anyone with a Mac and more experience in the subject I would encourage involvement.

afb:

--- Quote from: Takeshi Miya on October 27, 2006, 01:44:38 am ---It would be nice if the afb patches get applied because they often go out-of-sync and can't merge.

--- End quote ---

The important ones is fixing "bootstrap" and "configure", so that they work out of the box on Mac OS X (without patching). This includes allowing to specify different autotools versions, and making the plugin bundles link without missing symbols...

The wxFlatNotebook patch is upstream, so that should be on it's way for like wxFNB 2.2 or something and make it into Code::Blocks that way. The fixes for GTK+ on Darwin would be nice to have, but do I think most people want the Carbon version.

mandrav:

--- Quote ---I was maybe a little too quick to announce total MacOSX success, one remaining issue is wxSmith.
--- End quote ---

wxSmith has issues in other platforms too, so don't worry. Eventually, byo will fix it :).

afb:

--- Quote from: bnilsson on October 27, 2006, 09:08:25 am ---I was maybe a little too quick to announce total MacOSX success, one remaining issue is wxSmith.
--- End quote ---

wxSmith would be nice to have, but I think it can wait until the rest works better...

Ones that I would like to see are:

* Fixing the execute bugs on Intel, so that it doesn't just "hang" the first thing
* Fixing the debugger interaction so that it finds source and doesn't self-destruct
* Double-clicking files in Finder to open them, instead of having to use Open
* Working links on the Start Here page, and it not first showing up as all blank
* Making Run start a new Terminal.app session (by using AppleScript, probably)
* Installation package for wxWidgets development files (I am working on this)
That, and I would also like a pony full support for the D programming language :-)

bnilsson:
This is the bootstrap I use on my Mac, working satisfactory for me.
It requires MacPort autotools.

--- Code: ---# ! / bin / sh

# stolderdized from Ogre3D (www.ogre3d.org)

# Check for proper versions of autotools
# We require:
#  - autoconf 2.50+
#  - automake 1.7+
#  - libtool 1.4+

# Touch revision.m4
if [ -f ./update_revision.sh ]; then
./update_revision.sh;
elif [ ! -f ./revision.m4 ]; then
echo "m4_define([SVN_REVISION], trunk-r0)" > ./revision.m4;
fi

# Deal with some gentoo-specific issues
export WANT_AUTOMAKE='1.7'
export WANT_AUTOCONF='2.5'

## Using prereq in autoconf rather than here, mostly for the debian systems at
## this point
if test -n "`/opt/local/bin/autoconf --version 2>&1|head -n 1|egrep '1.*|2.[0-4]'`"; then
echo "Autoconf 2.50 or above is required. Aborting build...";
    exit 1;
fi

if test -n "`/opt/local/bin/automake --version 2>&1|head -n 1|egrep '1.[0-6]'`"; then
echo "Automake 1.7 or above is required. Aborting build...";
exit 1;
fi

if test -n "`/opt/local/bin/glibtool --version 2>&1|head -n 1|cut -f 4 -d ' '|egrep '1.[0-3]'`"; then
echo "Libtool 1.4 or above is required. Aborting build...";
exit 1;
fi

# clean up files which cause confusion when switch versions of auto*
rm -rf autom4te.cache

# Fire up autotools
/opt/local/bin/glibtoolize --force --copy && \
/opt/local/bin/aclocal $ACLOCAL_FLAGS && \
/opt/local/bin/autoheader && \
/opt/local/bin/automake --include-deps --add-missing --foreign --copy && \
/opt/local/bin/autoconf

--- End code ---

About the debugger: If there are no spaces in the path, it seems to find the source files. Is it more problems than this?

Navigation

[0] Message Index

[#] Next page

[*] Previous page