Code::Blocks

User forums => Using Code::Blocks => Topic started by: TheWizzard on August 30, 2005, 06:05:24 pm

Title: Compiling on Mac OS X
Post by: TheWizzard on August 30, 2005, 06:05:24 pm
Hi,

I got pretty far with compiling Code::Blocks on Mac OS X, using gcc 3.3 and the bundled wxWidgets 2.5.x by making some changes to the source and makefile, but now I'm stuck. I know that Mac OS X isn't officially supported, but maybe you can help me anyway.

Here's what I get:
Quote

Linking shared library devel/libcodeblocks.so...
ld: Undefined symbols:
__ZTI8wxThread
__ZTI19wxTopLevelWindowMac
__ZTI8wxDialog
__ZN11wxScintilla10BraceMatchEi
__ZN11wxScintilla10GetEOLModeEv
__ZN11wxScintilla10GetStyleAtEi
__ZN11wxScintilla10GetUseTabsEv
__ZN11wxScintilla10InsertTextEiRK8wxString
__ZN11wxScintilla10MarkerNextEii
__ZN11wxScintilla10SetEOLModeEi
__ZN11wxScintilla10SetUseTabsEb
__ZN11wxScintilla10SetViewEOLEb
__ZN11wxScintilla10ToggleFoldEi
__ZN11wxScintilla11ConvertEOLsEi
__ZN11wxScintilla11DelLineLeftEv
__ZN11wxScintilla11GetTabWidthEv
__ZN11wxScintilla11SetEdgeModeEi
__ZN11wxScintilla11SetPropertyERK8wxStringS2_
__ZN11wxScintilla11SetReadOnlyEb
__ZN11wxScintilla11SetTabWidthEi
__ZN11wxScintilla11SetWrapModeEi
__ZN11wxScintilla12DelLineRightEv
__ZN11wxScintilla12GetFoldLevelEi
__ZN11wxScintilla12GetLastChildEii
__ZN11wxScintilla12GetLineCountEv
__ZN11wxScintilla12GetTextRangeEii
__ZN11wxScintilla12MarkerDefineEii
__ZN11wxScintilla12MarkerDeleteEii
__ZN11wxScintilla12ScrollToLineEi
__ZN11wxScintilla12SetFoldFlagsEi
__ZN11wxScintilla12SetSavePointEv
__ZN11wxScintilla12SetSelectionEii
__ZN11wxScintilla12SetTargetEndEi
__ZN11wxScintilla12StyleSetFontEiR6wxFont
__ZN11wxScintilla12ms_classInfoE
__ZN11wxScintilla13BraceBadLightEi
__ZN11wxScintilla13CallTipActiveEv
__ZN11wxScintilla13CallTipCancelEv
__ZN11wxScintilla13EndUndoActionEv
__ZN11wxScintilla13GetCurrentPosEv
__ZN11wxScintilla13ReplaceTargetERK8wxString
__ZN11wxScintilla13SetCurrentPosEi
__ZN11wxScintilla13SetEdgeColourERK8wxColour
__ZN11wxScintilla13SetEdgeColumnEi
__ZN11wxScintilla13SetMarginMaskEii
__ZN11wxScintilla13SetMarginTypeEii
__ZN11wxScintilla13SetTabIndentsEb
__ZN11wxScintilla13StyleClearAllEv
__ZN11wxScintilla13sm_eventTableE
__ZN11wxScintilla14BraceHighlightEii
__ZN11wxScintilla14GetCurrentLineEv
__ZN11wxScintilla14MarkerPreviousEii
__ZN11wxScintilla14ScrollToColumnEi
__ZN11wxScintilla14SetMarginWidthEii
__ZN11wxScintilla14SetTargetStartEi
__ZN11wxScintilla15BeginUndoActionEv
__ZN11wxScintilla15EmptyUndoBufferEv
__ZN11wxScintilla15GetFoldExpandedEi
__ZN11wxScintilla15GetSelectionEndEv
__ZN11wxScintilla15MarkerDeleteAllEi
__ZN11wxScintilla15SetFoldExpandedEib
__ZN11wxScintilla16LineFromPositionEi
__ZN11wxScintilla16PositionFromLineEi
__ZN11wxScintilla16ReplaceSelectionERK8wxString
__ZN11wxScintilla17GetSelectionStartEv
__ZN11wxScintilla17PositionFromPointE7wxPoint
__ZN11wxScintilla17SetMouseDwellTimeEi
__ZN11wxScintilla17SetViewWhiteSpaceEi
__ZN11wxScintilla17WordStartPositionEib
__ZN11wxScintilla18GetLineEndPositionEi
__ZN11wxScintilla18SetMarginSensitiveEib
__ZN11wxScintilla18SetPrintColourModeEi
__ZN11wxScintilla18StyleSetBackgroundEiRK8wxColour
__ZN11wxScintilla19GetFirstVisibleLineEv
__ZN11wxScintilla19MarkerSetBackgroundEiRK8wxColour
__ZN11wxScintilla19MarkerSetForegroundEiRK8wxColour
__ZN11wxScintilla19SetCaretLineVisibleEb
__ZN11wxScintilla20SetIndentationGuidesEb
__ZN11wxScintilla21SetBackSpaceUnIndentsEb
__ZN11wxScintilla22SetCaretLineBackgroundERK8wxColour
__ZN11wxScintilla3CutEv
__ZN11wxScintilla4CopyEv
__ZN11wxScintilla4RedoEv
__ZN11wxScintilla4UndoEv
__ZN11wxScintilla5PasteEv
__ZN11wxScintilla7CanRedoEv
__ZN11wxScintilla7CanUndoEv
__ZN11wxScintilla7GetLineEi
__ZN11wxScintilla7GetTextEv
__ZN11wxScintilla7GotoPosEi
__ZN11wxScintilla7SendMsgEill
__ZN11wxScintilla8CanPasteEv
__ZN11wxScintilla8ClearAllEv
__ZN11wxScintilla8GotoLineEi
__ZN11wxScintilla8UsePopUpEb
__ZN11wxScintilla9ColouriseEii
__ZN11wxScintilla9GetCharAtEi
__ZN11wxScintilla9GetModifyEv
__ZN11wxScintilla9HideLinesEii
__ZN11wxScintilla9MarkerAddEii
__ZN11wxScintilla9MarkerGetEi
__ZN11wxScintilla9SelectAllEv
__ZN11wxScintilla9ShowLinesEii
__ZN11wxScintillaC2EP8wxWindowiRK7wxPointRK6wxSizelRK8wxString
__ZN11wxScintillaD2Ev
__ZNK11wxScintilla13DoGetBestSizeEv
__ZTI10wxListBase
__ZTI11wxScintilla
__ZTI8wxObject
_wxEVT_SCI_CHANGE
_wxEVT_SCI_CHARADDED
_wxEVT_SCI_DWELLEND
_wxEVT_SCI_DWELLSTART
_wxEVT_SCI_MARGINCLICK
_wxEVT_SCI_UPDATEUI
_wxEVT_SCI_USERLISTSELECTION
_wxSCINameStr
__ZN11wxScintilla11FormatRangeEbiiP4wxDCS1_6wxRectS2_
__ZN11wxScintilla15GetSelectedTextEv
__ZN11wxScintilla9GetLengthEv
__ZTI10wxPrintout
__ZTI12wxEvtHandler
__ZN11wxScintilla10TextHeightEi
__ZN11wxScintilla17PointFromPositionEi
__ZTI7wxPanel
__ZN11wxScintilla11SetKeyWordsEiRK8wxString
__ZN11wxScintilla12StyleSetBoldEib
__ZN11wxScintilla14StyleSetItalicEib
__ZN11wxScintilla16SetSelBackgroundEbRK8wxColour
__ZN11wxScintilla17StyleSetUnderlineEib
__ZN11wxScintilla18SetCaretForegroundERK8wxColour
__ZN11wxScintilla18StyleSetForegroundEiRK8wxColour
__ZN11wxScintilla8SetLexerEi
__ZN11wxScintilla13SetCaretWidthEi
__ZN11wxScintilla7SetTextERK8wxString
__ZN11wxScintilla8LoadFileERK8wxString
__ZN11wxScintilla11GetReadOnlyEv
__ZN11wxScintilla13EnsureVisibleEi
__ZN11wxScintilla15ReplaceTargetREERK8wxString
__ZN11wxScintilla15WordEndPositionEib
__ZN11wxScintilla8FindTextEiiRK8wxStringi
__ZTI10wxNodeBase
__ZTI17wxGenericTreeCtrl
__ZTI18wxGenericImageList
__ZTI23wxGenericScrolledWindow
__ZTI10wxNotebook
__ZN17MSVCWorkspaceBase13addDependencyERK8wxStringS2_
__ZN17MSVCWorkspaceBase14updateProjectsEv
__ZN17MSVCWorkspaceBase15registerProjectERK8wxStringP9cbProject
__ZN17MSVCWorkspaceBase24addConfigurationMatchingERK8wxStringS2_S2_
__ZN17MSVCWorkspaceBase25addWorkspaceConfigurationERK8wxString
__ZN17MSVCWorkspaceBaseC2Ev
__ZN17MSVCWorkspaceBaseD2Ev
__ZTI17MSVCWorkspaceBase
__ZTI9wxProcess
__ZTI17wxGenericListCtrl
/usr/bin/libtool: internal link edit command failed
make: *** [devel/libcodeblocks.so] Error 1
Title: Re: Compiling on Mac OS X
Post by: zieQ on August 30, 2005, 06:14:35 pm
Did you use the makefiles provided with C::B? Which version? CVS? Makefiles are outdated I think, that why you have these link errors. Hope someone could regenerate those makefiles in CVS, I'm do not have access to my home machine right now! There are some odds things with wx classes too, don't know why! Did you link wx library properly?
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 30, 2005, 06:25:06 pm
Actually I just used the Makefile.unix. The only thing I changed is -shared to -dynamiclib, as Mac OS X needs that.
Title: Re: Compiling on Mac OS X
Post by: Urxae on August 30, 2005, 06:39:59 pm
Yeah, makefiles tend to get outdated, especially Makefile.unix. That's what you get when the usual way to build Code::Blocks is to use the C::B project file ;).
Looks like it hasn't been updated to include the wxScintilla sources yet, so it can't find a lot of stuff in there.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 30, 2005, 06:41:21 pm
So I guess there's nothing I can do except wait?
Or can I somehow modify the Makefile?
I never needed to really get into Makefiles, although I have plenty of Linux experience.
Title: Re: Compiling on Mac OS X
Post by: Urxae on August 30, 2005, 08:32:41 pm
Well, it seems CodeBlocks-unix.cbp at least includes wxScintilla, so I exported a makefile for it and attached it. Zipped to meet both the size and file type restrictions of this board. You'll have to remodify it to work on OS X, I didn't do anything but export it.
Hope this helps.

EDIT: You mentioned you use wx 2.5.x, I'm not sure which project you need for that. Attached file is from CodeBlocks-unix.cbp, so for wx 2.4.

[attachment deleted by admin]
Title: Re: Compiling on Mac OS X
Post by: mandrav on August 30, 2005, 09:09:29 pm
Makefiles may be outdated for a while. They 're not constantly outdated :P
Judging by the error log, you probably used an older makefile. Newer CVS contains wxScintilla, which is what you 're missing.
So, update from CVS and everything should be fine again :)

Quote
I got pretty far with compiling Code::Blocks on Mac OS X, using gcc 3.3 and the bundled wxWidgets 2.5.x by making some changes to the source and makefile, but now I'm stuck. I know that Mac OS X isn't officially supported, but maybe you can help me anyway.
It 's not supported because none of us owns a Mac :P
We 'd be glad though to have Mac-guy on board :D

*EDIT*:
Notice that under linux it only works with wx2.4 currently. So if you finally build it but it doesn't run, don't despair. It might have the same problem with the linux port. In that case, either try to fix it (and many users will be greatful :) ), or use wx2.4.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 30, 2005, 09:30:02 pm
I use the latest CVS and did a make clean but now it already fails at libwxscintilla.so.

I think I'll just build wx 2.6 from source and try again then. I'll let you know if it works (or at least compiles)
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 30, 2005, 10:06:20 pm
Well,

The Makefile.unix.wx2.6 doesn't seem to include scintilla :(
and the other one won't work with wx 2.6, will it?

TheWizzard
Title: Re: Compiling on Mac OS X
Post by: mandrav on August 30, 2005, 10:57:46 pm
Sorry, my bad  :oops:
Because the linux port doesn't work with wx2.6, the relevant project file and makefile were outdated...

I 'm updating both now.
Because anonymous cvs lags a few hours, I 'm attaching a (hopefully) correct Makefile.unix.wx2.6 as a zip file.
If it doesn't work, try Makefile.unix. You will only have to change the lib names for wx...

[attachment deleted by admin]
Title: Re: Compiling on Mac OS X
Post by: byo on August 30, 2005, 11:17:32 pm
Hi, maybe I've found the cause of crashes under wx2.6 - some compiler flags set globally in wx2.6 project changed calling convention for some functions what was the cause of seg faults. In wx2.4 projet there's only `wx-config --cflags` left. After removing other flags it compiles and runs without any crashes at the beginning :)
I've to check it once more since I've checked out whole repository (I've messed in source code too much to find the cause of crashes ;) ). But I guess it will work :)

Yep. I've really seen C::B on Linux using wx 2.6 :D
Title: Re: Compiling on Mac OS X
Post by: rickg22 on August 31, 2005, 12:22:11 am
Calling conventions?  :? Please explain further... this is some area where i'm a total n00b.
Title: Re: Compiling on Mac OS X
Post by: byo on August 31, 2005, 12:35:04 am
Calling conventions?  :? Please explain further... this is some area where I'm a total n00b.

I think the cause of crashes on wx 2.6 was that wx code was compiled with one configuration of passing arguments and return values from functions and C::B with second one. In such case stack frames are incorrectly created - arguments may be shifted in stack space and incorrectly read. F. ex. reading address of place where to store result instead of 'this' pointer (what probably caused crashes in simple GetClientSize() function ).

I guess that -fno-pcc-struct-return compiler flag messed here ;)

I've attached project and makefile in http://forums.codeblocks.org/index.php/topic,824.msg5737.html#msg5737

And hope that wx 2.6 will soon be also supported ;)
Title: Re: Compiling on Mac OS X
Post by: xjluo on August 31, 2005, 05:02:15 am
The byo's solution succeeded on my Debian Linux with wxGTK-2.6.1, but failed on Mac OS X with wxMac-2.6.1.
I have downloaded the CVS version and replaced following setting in the Makefile:
-shared --> -dynamiclib
-D__WXGTK__ --> -D__WXMAC__
.so -> .dylib
and added -D__WXMAC_CARBON__ to all ???_GLOBAL_CFLAGS to avoid wxGenericImageList link error.
It finally stops on wxDockit compiling and says "Your platform does not currently support wxGdi".

Does anyone else have more information on Mac OS X platform?
Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 05:33:25 am
The -fno-pcc-struct-return flag is probably no longer needed for the windows version either.
http://64.233.187.104/search?q=cache:DVNNfK54IZoJ:www.bzzt.net/~wxwindows/xmldocs/generating/texdocs/wxWidgets/src/makeg95.env+fno-pcc-struct-return&hl=en&client=firefox-a

It was needed to workaround an mingw bug (prior to 08/98).

xjluo:
even the 2.1 wxDockit say:
"NOTE: wxDockIt currently supports only the wxGTK port of wxWidgets.
       wxX11 and wxMotif cannot be used with wxDockIt."

So I guess wxMAC won't work with wxDockit.
Title: Re: Compiling on Mac OS X
Post by: xjluo on August 31, 2005, 06:15:47 am
I tried on the tarball version and failed again. :(

According to byo's commention, I removed all flags except -Wall -g `wx-config --cflags`. I also modified the Makefile to avoid other compile errors. All modules compiled and linked successfully except plugin_CompilerGCC (So, I skip it), Code::Blocks got segment fault on running. :?
Title: Re: Compiling on Mac OS X
Post by: xjluo on August 31, 2005, 06:28:39 am
It's a pitty that wxDockit does not support wxMac, which means the newer Code::Blocks versions won't support Mac either.  :(

Though the tarball version of Code::Blocks does not use wxDockit, it failed me.  :( :( :(
Title: Re: Compiling on Mac OS X
Post by: takeshi miya on August 31, 2005, 07:28:14 am
"Porting" wxDockIt to Mac, anyone?
or
"Porting" wxIFM to Mac, anyone?
Title: Re: Compiling on Mac OS X
Post by: mandrav on August 31, 2005, 08:35:22 am
We will soon be evaluating wxIFM (which works under Mac AFAIK), so keep an eye open ;)
Title: Re: Compiling on Mac OS X
Post by: zieQ on August 31, 2005, 08:40:55 am
I tried on the tarball version and failed again. :(

According to byo's commention, I removed all flags except -Wall -g `wx-config --cflags`. I also modified the Makefile to avoid other compile errors. All modules compiled and linked successfully except plugin_CompilerGCC (So, I skip it), Code::Blocks got segment fault on running. :?

Can you report the errors you have with compilerGCC plugin? That would be cool if it compiles at least ;) And where did the segfault happens?
Title: Re: Compiling on Mac OS X
Post by: xjluo on August 31, 2005, 11:37:15 am
Error message on linking plugin_CompilerGCC:
=====================================================
Linking shared library devel/share/CodeBlocks/plugins/libcompilergcc.dylib...
ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option
.objs/2.6/plugins/compilergcc/depslib/src/depslib.o definition of common _g_stats (size 12)
/usr/bin/libtool: internal link edit command failed
make: *** [devel/share/CodeBlocks/plugins/libcompilergcc.dylib] Error 1
=====================================================

Error message on executing run.sh:
=====================================================
kevin-ibook:~/share/codeblocks-1.0-RC1-1/src/output kevin$ ./run.sh
./run.sh: line 5: 27881 Segmentation fault      $APP_DIR/codeblocks.exe [email protected]
=====================================================
The splash window of Code::Blocks was shown.
Title: Re: Compiling on Mac OS X
Post by: byo on August 31, 2005, 11:56:44 am
Check if You have all files from compiler plugin added into project, ecpecially compilerSDCC.cpp
Title: Re: Compiling on Mac OS X
Post by: xjluo on August 31, 2005, 12:02:16 pm
There is no file named compilerSDCC.cpp in the tarball version.

It's included in the CVS version.

Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 02:04:19 pm
So It seems that I have two options:

port wxDockit

or wait for C::B to use wxIFM

Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 03:20:15 pm
xjluo: have you tried:

http://public.kitware.com/pipermail/vtkusers/2004-February/071486.html
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 03:40:13 pm
Ok,

with the updated make and latest CVS I get:

Quote
Compiling sdk/wxscintilla/src/PlatWX.cpp...
sdk/wxscintilla/src/PlatWX.cpp: In constructor `Font::Font()':
sdk/wxscintilla/src/PlatWX.cpp:93: error: `ascent' undeclared (first use this function)

I'm confused. Guess I'll just have to wait for a new codeblocks, as I have little to no knowledge of wx.
Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 03:52:42 pm
I'm compiling right now.  As soon as everything tests OK I'll post needed changes to the CVS Makefile (based on the Makefile byo posted), but try this:

remove all -fno-pcc-struct-return
(i.e. change PROJECT CFLAGS to
*_PROJECT_CFLAGS= -Wall -g -pipe -fmessage-length=0 `wx-config --cflags`
)

scintilla is missing #defines.  change the scintilla target CFLAGS (which fixes your error):
scintilla_CFLAGS= $(scintilla_PROJECT_CFLAGS) -DGTK -DSCI_LEXER -DLINK_LEXERS -DWXMAKINGDLL_SCI $(scintilla_GLOBAL_CFLAGS)

add -Ldevel for sdk :
sdk_PROJECT_LIBDIRS= -Lsdk/tinyxml -Ldevel

also make sure you compiled wxwidgets 2.6 as nonunicode.  wxdockit 2.01 needs some unicode patches (2.1 is unicode compatible and wxIFM is also being looked at).
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 05:19:14 pm
Okay,

Thx, your tips worked. I (of course) got an error when compiling wxDockit. I tried to just make it use GTK for the mac platform, which actually compiled, but won't link.

I get many of those:

Quote
ld: src/wxDockit/lib/libwxDockit.a(dockhost.o) illegal reference for -dynamic code (section difference reference from section (__TEXT,__eh_frame) relocation entry (138) to symbol: __ZN12wxWindowListD0Ev defined in dylib: /usr/local/lib/libwx_mac_core-2.6.dylib)

Is it really incompatible or just something that can be fixed with some minor tweaks? As aforementioned I know little to nothing about wx, so I can't really port it. All the stuff wxDockit calls seems to be there in wxMac (it compiles), but I can't figure out what the linker message means.
Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 05:37:49 pm
`wx-config --cflags` gives you which flags?
is -fPIC defined (think mac needs PIC libs)
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 07:24:30 pm
Quote
-I/usr/local/lib/wx/include/mac-ansi-release-2.6 -I/usr/local/include/wx-2.6 -D__WXMAC__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -DNO_GCC_PRAGMA

That's wx-config --cflags

I just added -fPIC to ???_PROJECT_CFLAGS

It's now compiling.
Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 08:05:36 pm
cool.  If it fails you can check:
http://sourceforge.net/mailarchive/message.php?msg_id=12014390
http://64.233.167.104/search?q=cache:5-CtyzHOu-wJ:lists.wxwidgets.org/archive/wxPython-mac/msg00438.html+%22section+difference+reference%22&hl=en&client=firefox-a

Does mac tiger support .a files, btw?  One thing I would try (if needed) is to build that libwxDockit.a file as a shared lib instead (.so) and also use -fPIC.

Based on googling, it looks like either an ABI issue (application binary interface - which varies from gcc version to version) or some CFLAGS flag that is missing and needed for the macos build to go.  So, re the ABI thing, it's best to compile wxWidgets yourself and then codeblocks because this guarantees that they both have the same ABI, since they were compiled with the same compiler version.  (e.g.
in a lot of cases you can't mix libraries or binaries from gcc 3.4 and gcc 3.3 or gcc 4.0 compiled code).
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 08:10:40 pm
Ok,

I used fPIC and it failed, wxWidgets is self-built. I got plenty .a files in /usr/lib so I would say yes, os x supports them (and shared libs are .dynlib on os x, btw)

It's all compiled with gcc 3.3 (you can do gcc_select and choose between 3.3 and 4.0 on tiger) and I'll now try to recompile wx with the options listed on the wxPython-mac list.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 08:55:07 pm
w00t!

That worked. It now fails at astyle, I hope I can figure that out on my own.

*EDIT*

I can't. ;)

Quote
__Z19wxGetTopLevelParentP8wxWindow
__ZN10wxFontBaseD2Ev
__ZN10wxSpinCtrl8SetValueEi
__ZN12wxDialogBase11RemoveChildEP12wxWindowBase
__ZN12wxDialogBase12OnChildFocusER17wxChildFocusEvent
__ZN12wxDialogBase14SetDefaultItemEP8wxWindow
__ZN12wxDialogBase17SetTmpDefaultItemEP8wxWindow
__ZN12wxDialogBase24SetFocusIgnoringChildrenEv
__ZN12wxDialogBase4InitEv
__ZN12wxDialogBase8SetFocusEv
__ZN12wxEvtHandler12ProcessEventER7wxEvent
__ZN12wxEvtHandler15DoSetClientDataEPv
__ZN12wxEvtHandler16SearchEventTableER12wxEventTableR7wxEvent
__ZN12wxEvtHandler17DoSetClientObjectEP12wxClientData
__ZN12wxStringBase4nposE
__ZN12wxStringBase8InitWithEPKcmm
__ZN12wxStringBaseaSEPKc
__ZN12wxStringBaseaSERKS_
__ZN12wxWindowBase10GetCaptureEv
__ZN12wxWindowBase10InitDialogEv
__ZN12wxWindowBase12LayoutPhase1EPi
__ZN12wxWindowBase12LayoutPhase2EPi
__ZN12wxWindowBase12SetValidatorERK11wxValidator
__ZN12wxWindowBase12TryValidatorER7wxEvent
__ZN12wxWindowBase14DoSetSizeHintsEiiiiii
__ZN12wxWindowBase14MoveConstraintEii
__ZN12wxWindowBase14UpdateWindowUIEl
__ZN12wxWindowBase16DoMoveInTabOrderEP8wxWindowNS_8MoveKindE
__ZN12wxWindowBase16DoSetVirtualSizeEii
__ZN12wxWindowBase17InheritAttributesEv
__ZN12wxWindowBase17SetSizeConstraintEiiii
__ZN12wxWindowBase18SetConstraintSizesEb
__ZN12wxWindowBase19SetVirtualSizeHintsEiiii
__ZN12wxWindowBase20TransferDataToWindowEv
__ZN12wxWindowBase22TransferDataFromWindowEv
__ZN12wxWindowBase25GetClassDefaultAttributesE15wxWindowVariant
__ZN12wxWindowBase3FitEv
__ZN12wxWindowBase6LayoutEv
__ZN12wxWindowBase7DoPhaseEi
__ZN12wxWindowBase8AddChildEPS_
__ZN12wxWindowBase8NavigateEi
__ZN12wxWindowBase8ReparentEPS_
__ZN12wxWindowBase8ValidateEv
__ZN12wxWindowBase9FindFocusEv
__ZN12wxWindowBase9FitInsideEv
__ZN12wxWindowBase9MakeModalEb
__ZN12wxWindowBase9TryParentER7wxEvent
__ZN13wxXmlResource10LoadDialogEP8wxDialogP8wxWindowRK8wxString
__ZN13wxXmlResource3GetEv
__ZN13wxXmlResource8GetXRCIDEPKc
__ZN16wxEventHashTableC1ERK12wxEventTable
__ZN16wxEventHashTableD1Ev
__ZN18wxControlContainerC1EP8wxWindow
__ZN19wxTopLevelWindowMac11MacActivateElb
__ZN19wxTopLevelWindowMac12DoMoveWindowEiiii
__ZN19wxTopLevelWindowMac14ShowFullScreenEbl
__ZN19wxTopLevelWindowMac15ClearBackgroundEv
__ZN19wxTopLevelWindowMac17MacPerformUpdatesEv
__ZN19wxTopLevelWindowMac19MacCreateRealWindowERK8wxStringRK7wxPointRK6wxSizelS2_
__ZN19wxTopLevelWindowMac20RequestUserAttentionEi
__ZN19wxTopLevelWindowMac21MacSetBackgroundBrushERK7wxBrush
__ZN19wxTopLevelWindowMac22MacGetContentAreaInsetERiS0_S0_S0_
__ZN19wxTopLevelWindowMac36MacInstallTopLevelWindowEventHandlerEv
__ZN19wxTopLevelWindowMac4InitEv
__ZN19wxTopLevelWindowMac5LowerEv
__ZN19wxTopLevelWindowMac5RaiseEv
__ZN19wxTopLevelWindowMac7IconizeEb
__ZN19wxTopLevelWindowMac7RestoreEv
__ZN19wxTopLevelWindowMac7SetIconERK6wxIcon
__ZN19wxTopLevelWindowMac8MaximizeEb
__ZN19wxTopLevelWindowMac8SetShapeERK8wxRegion
__ZN19wxTopLevelWindowMac8SetTitleERK8wxString
__ZN19wxTopLevelWindowMacD2Ev
__ZN20wxTopLevelWindowBase16DoUpdateWindowUIER15wxUpdateUIEvent
[...]
Title: Re: Compiling on Mac OS X
Post by: grv575 on August 31, 2005, 09:03:55 pm
Well if that's the only part that doesn't work (it's a plugin for C/C++ source code autoformatting - i.e. it reformat all your source according to ANSI guidelines, or K&R or whatever) then maybe skip that plugin.  Good to know most of the stuff should't be too difficult to get working on macs without major changes.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on August 31, 2005, 09:13:01 pm
Well ok,

this is what I get with CompilerGCC:

Quote
Linking shared library devel/share/CodeBlocks/plugins/libcompilergcc.dynlib...
ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option
.objs/2.6/plugins/compilergcc/depslib/src/depslib.o definition of common _g_stats (size 12)
/usr/bin/libtool: internal link edit command failed
make: *** [devel/share/CodeBlocks/plugins/libcompilergcc.dynlib] Error 1

I don't understand that message. Whats MH_DYLIB and -multi_module?

*EDIT*
DebuggerGDB - same as Astyle
CodeCompletion - same as Astyle
ClassWizard - same as Astyle
DefMimeHandler - same as Astyle
PluginWizard - same as Astyle
ToDo - compiles
Title: Re: Compiling on Mac OS X
Post by: takeshi miya on August 31, 2005, 09:13:55 pm
Yeah, makefiles tend to get outdated, especially Makefile.unix. That's what you get when the usual way to build Code::Blocks is to use the C::B project file ;).

Yes, the makefiles for compiling C::B are always outdated in CVS (not a good thing for an IDE, which you can't compile if you don't have the IDE itself :cry:)

That's why I propose auto-generate makefiles when saving:
http://forums.codeblocks.org/index.php/topic,831.0.html
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 02:29:10 am
To TheWizzard:

Check your Makefile, if you find:
plugin_???_LDFLAGS = $(plugin_???_GLOBAL_LDFLAGS)

replace with following:
plugin_???_LDFLAGS = $(plugin_???_GLOBAL_LDFLAGS) $(plugin_???_PROJECT_LDFLAGS)

Then plugins will be linked. They forgot to link wxWidgets libraries to these plugins.

Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 02:43:58 am
The CompilerGCC error solution:

1. Change directory to plugins/compilergcc/depslib/src
    rename cache.c to cache.inc
    rename headers.c to header.inc
    rename depslib.c to depslib.inc
2. Create new empty file cache.c, headers.c
3. Create new file depslib.c with following lines:
========BEGIN==========
#include "depslib.inc"
#include "headers.inc"
#include "cache.inc"
========END==========
4. Edit headers.inc and cache.inc, delete all repeated header files (compared with depslib.inc) including:
jam.h hash.h lists.h newstr.h depslib.h (in cache.inc)
jam.h hash.h lists.h newstr.h headers.h depslib.h (in headers.inc)
and following line:
extern struct depsStats g_stats; (in both files)
5. Edit depslib.inc:
Find this line: struct depsStat g_stats;
Replace with: static struct depsStat g_stats;

CompilerGCC plugin should be linked.
Title: Re: Compiling on Mac OS X
Post by: grv575 on September 01, 2005, 02:46:44 am
thewizard: that -multi-module error was covered earlier in the thread (reply#24).
Need to pass -single I think.
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 03:04:37 am
I have done all previous steps. Code::Blocks and all plugins were generated. Finally, I got a segfault on running Code::Blocks.

The Mac compiler and linker settings are quite different with Linux versions. I rewrite the Makefile based on a Makefile template which I used on several projects (on Mac/Linux/Windows). The modules under sdk were statically linked into codeblocks. But, I got a segfault again after the splash window. :(

Anybody can explain following:
Are plugins neccessary?
Can sdk files be statically linked?
Which version of gcc should be used?

Thanks a lot.

BTW, in the following sdk files,
editormanager.cpp messagemanager.cpp newfromtemplatedlg.cpp projectmanager.cpp
They all use the wx class wxImageList. You have to add:
#include <wx/wx.h>
before all other header files. Otherwise, you will get a link error about wxGenericImageList. The file wx.h implicitly includes platform.h where a macro named __WXMAC_CARBON__ is defined. The macro __WXMAC_CARBON__ decides wether a Mac version of wxImageList will be used.
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 03:20:09 am
Two suggestions to project developers,

1. If you want to use wx classes in your file, please insert following line
#include <wx/wx.h>
before all other header files. wx.h implicitly includes platform.h and many other header files where a lot of important macros and other things are defined.

2. In your custom header files, please put your codes inside
#ifndef __XXX_H__
#define __XXX_H__
// put your own codes here
#endif __XXX_H__
or, you can also use pragma or other mechanism to avoid header files being iteratively/repeatedly included.

Title: Re: Compiling on Mac OS X
Post by: rickg22 on September 01, 2005, 03:43:49 am
O.O there are files with those missing?  :shock:

Yikes. Which files?
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 03:48:27 am
grv575 is right.

Append a "-single_module" option to plugin_CompilerGCC_PROJECT_LDFLAGS variable will get rid of the link error on plugin CompilerGCC.
My previous solution is too ugly. :)
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 03:54:41 am
editormanager.cpp messagemanager.cpp newfromtemplatedlg.cpp projectmanager.cpp inside sdk need wx.h to be included.

Header files inside plugins/compilergcc/depslib/src have no iteratively include avoiding mechanism.
Title: Re: Compiling on Mac OS X
Post by: grv575 on September 01, 2005, 04:02:54 am
xjluo: gccplugin needs to compile/link (but cb should still load ok without it?)  the rest are optional.
You said you seta crash.  Could you post the codeblocks.rpt stack trace file?
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 01, 2005, 04:38:06 am
grv575: No files named codeblocks.rpt generated. How to get it?
Title: Re: Compiling on Mac OS X
Post by: grv575 on September 01, 2005, 05:54:42 am
dunno.  it should be generated in the same directory as codeblocks.exe when it crashes.  you can always do
gdb codeblocks.exe
run
bt

to get the backtrace
Title: Re: Compiling on Mac OS X
Post by: squizzz on September 01, 2005, 01:45:24 pm
Maybe it's standard resource missing (bitmaps, xrc) crash? You have to run update script after succesfully building C::B, and make sure there are no errors during its execution.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 03:09:16 pm
Okay,

Thanks to you all for the tips. It compiles Astyle, but still fails at CompilerGCC, giving the following linker error:

Quote
ld: Undefined symbols:
__ZN12CompilerSDCCC1Ev

CompilerSDCC is compiled by CompilerGCC isn't it? So why is it unable to find it?
Title: Re: Compiling on Mac OS X
Post by: mandrav on September 01, 2005, 03:13:28 pm
If you 're having problems with CompilerSDCC, edit compilergcc.cpp and, in the constructor, remove the line
Code: [Select]
CompilerFactory::RegisterCompiler(new CompilerSDCC);

Also remove the #include "compilerSDCC.h" from the top of the file.

This will remove SDCC support until we update the makefile...
Title: Re: Compiling on Mac OS X
Post by: Urxae on September 01, 2005, 03:18:37 pm
Quote
ld: Undefined symbols:
__ZN12CompilerSDCCC1Ev

CompilerSDCC is compiled by CompilerGCC isn't it? So why is it unable to find it?

Did it actually compile? Did it show up in the output? Maybe the makefile you used didn't compile compilerSDCC.cpp, it's a relatively new file to the project IIRC, so if the makefile's a bit out of date it may not be included.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 03:36:24 pm
Quote
./run.sh
dyld: Library not loaded: devel/libcodeblocks.dylib
  Referenced from: /Users/jonasoberschweiber/codeblocks/codeblocks/src/output/codeblocks.exe
  Reason: image not found
./run.sh: line 5: 10904 Trace/BPT trap          $APP_DIR/codeblocks.exe [email protected]

It compiled! w00t! But that's what I get now. There are images in share/CodeBlocks and so on. The devel/libcodeblocks.dylib exists.
Title: Re: Compiling on Mac OS X
Post by: grv575 on September 01, 2005, 04:00:52 pm
well...run.sh is running output/codeblocks.exe
which wants to load devel/codeblocks.dylib

and output/devel/codeblocks.dylib doesn't exist of course.  it should want to look for output/codeblocks.dylib but maybe some of those -Ldevel library paths hardcoded the libpath in the exe?  this should really be tested more on linux (why -Ldevel isn't needed on windows to link the sdk libs I'm not sure, maybe it should be -L"." instead on linux, not sure).

just for kicks does it load if you copy devel to output?  or modify run.sh to run the .exe in the devel directory instead of the output one?

edit:
actually, the run.sh may need to be modified for macos?  does mac use LD_LIBRARY_PATH (like linux) or LIBPATH?
http://msgs.securepoint.com/cgi-bin/get/openssh-unix-dev-0507/9/1/1.html
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 04:05:13 pm
Runs,

Well, sort of. Shows Splash and crashes.
Quote
#./run.sh: line 5: 10926 Segmentation fault      $APP_DIR/codeblocks.exe [email protected]
Title: Re: Compiling on Mac OS X
Post by: grv575 on September 01, 2005, 04:13:06 pm
that's what xjluo got.  if there's a codeblocks.rpt backtrace you can post that and if not maybe try
gdb run.sh (maybe needs to be gdb codeblocks.exe)
run
bt

which will give a backtrace.
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 05:28:58 pm
Ahh

My backtrace got > 90000 lines O.o

Should i really post it?
Title: Re: Compiling on Mac OS X
Post by: rickg22 on September 01, 2005, 05:45:50 pm
Just the first 100 lines, thank you :)
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 06:06:41 pm
There you go... ;)

Quote
(gdb) bt
#0  0x006387a0 in wxStringBase::operator= ()
#1  0x0102e700 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:91
#2  0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#3  0x00328844 in wxNotebook::SetPageText ()
#4  0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#5  0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#6  0x00328844 in wxNotebook::SetPageText ()
#7  0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#8  0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#9  0x00328844 in wxNotebook::SetPageText ()
#10 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#11 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#12 0x00328844 in wxNotebook::SetPageText ()
#13 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#14 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#15 0x00328844 in wxNotebook::SetPageText ()
#16 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#17 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#18 0x00328844 in wxNotebook::SetPageText ()
#19 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#20 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#21 0x00328844 in wxNotebook::SetPageText ()
#22 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#23 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#24 0x00328844 in wxNotebook::SetPageText ()
#25 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#26 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#27 0x00328844 in wxNotebook::SetPageText ()
#28 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#29 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#30 0x00328844 in wxNotebook::SetPageText ()
#31 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#32 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#33 0x00328844 in wxNotebook::SetPageText ()
#34 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#35 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#36 0x00328844 in wxNotebook::SetPageText ()
#37 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#38 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#39 0x00328844 in wxNotebook::SetPageText ()
#40 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#41 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#42 0x00328844 in wxNotebook::SetPageText ()
#43 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#44 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#45 0x00328844 in wxNotebook::SetPageText ()
#46 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#47 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#48 0x00328844 in wxNotebook::SetPageText ()
#49 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#50 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#51 0x00328844 in wxNotebook::SetPageText ()
#52 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#53 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#54 0x00328844 in wxNotebook::SetPageText ()
#55 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#56 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#57 0x00328844 in wxNotebook::SetPageText ()
#58 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#59 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#60 0x00328844 in wxNotebook::SetPageText ()
#61 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#62 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#63 0x00328844 in wxNotebook::SetPageText ()
#64 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#65 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#66 0x00328844 in wxNotebook::SetPageText ()
#67 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#68 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#69 0x00328844 in wxNotebook::SetPageText ()
#70 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#71 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#72 0x00328844 in wxNotebook::SetPageText ()
#73 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#74 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#75 0x00328844 in wxNotebook::SetPageText ()
#76 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#77 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#78 0x00328844 in wxNotebook::SetPageText ()
#79 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#80 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#81 0x00328844 in wxNotebook::SetPageText ()
#82 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#83 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#84 0x00328844 in wxNotebook::SetPageText ()
#85 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#86 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#87 0x00328844 in wxNotebook::SetPageText ()
#88 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#89 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#90 0x00328844 in wxNotebook::SetPageText ()
#91 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#92 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#93 0x00328844 in wxNotebook::SetPageText ()
#94 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#95 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#96 0x00328844 in wxNotebook::SetPageText ()
#97 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
#98 0x010c2f5c in wxWindowBase::SetLabel (this=0x40a9200, [email protected]) at /usr/local/include/wx-2.6/wx/window.h:186
#99 0x00328844 in wxNotebook::SetPageText ()
#100 0x0102e794 in EditorBase::SetTitle (this=0x40a9200, [email protected]) at sdk/editorbase.cpp:94
Title: Re: Compiling on Mac OS X
Post by: byo on September 01, 2005, 06:19:35 pm
Wow, nice stack overflow
Title: Re: Compiling on Mac OS X
Post by: TheWizzard on September 01, 2005, 06:31:03 pm
Thanks! ^^
So what can I do about this (I know C++ in theory, but I haven't got much experience)
Title: Re: Compiling on Mac OS X
Post by: rickg22 on September 01, 2005, 09:21:53 pm
I don't know...

maybe if you gave us the LAST 100 lines of the stack log... argh. I have no idea of what's going on.
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 02, 2005, 02:20:55 am
Dear all,

I got Code::Blocks running on my iBook G4, though the window layout is totally mixed up. A screenshot is attached. I will post my work in a new topic. Thanks to all for your kind hints. :)

[attachment deleted by admin]
Title: Re: Compiling on Mac OS X
Post by: xjluo on September 02, 2005, 03:23:59 am
The crash is caused by line 93~94 in file src/app.cpp which set the title text of notebook page. I commented these two lines and then Code::Blocks got running.

The new topic address:
http://forums.codeblocks.org/index.php?topic=838.msg5842#msg5842