Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Mac OS development
afb:
--- Quote from: jens on January 26, 2010, 09:16:08 am ---If you use pch on mac, try to delete them manually and see if it works.
--- End quote ---
Precompiled headers is the default, yes, unless using --disable-pch.
(There's also an old bug that it keeps the .gch files in the source dir,
instead of in the proper build directories but I've patched that locally
as I'm doing Universal Binary builds and thus doing more than one build)
But it built with these modifications:
--- Code: (svn diff) ---Index: src/sdk/wxscintilla/src/scintilla/src/ExternalLexer.h
===================================================================
--- src/sdk/wxscintilla/src/scintilla/src/ExternalLexer.h (revision 6113)
+++ src/sdk/wxscintilla/src/scintilla/src/ExternalLexer.h (arbetskopia)
@@ -14,6 +14,8 @@
#define EXT_LEXER_DECL
#endif
+#include <string>
+
#ifdef SCI_NAMESPACE
namespace Scintilla {
#endif
Index: src/include/infowindow.h
===================================================================
--- src/include/infowindow.h (revision 6113)
+++ src/include/infowindow.h (arbetskopia)
@@ -26,6 +26,7 @@
#include <wx/popupwin.h>
typedef wxPopupWindow wxInfoWindowBase;
#else
+ #include "scrollingdialog.h"
typedef wxScrollingDialog wxInfoWindowBase;
#endif
Index: src/plugins/contrib/wxSmith/propgrid/Makefile.am
===================================================================
--- src/plugins/contrib/wxSmith/propgrid/Makefile.am (revision 6113)
+++ src/plugins/contrib/wxSmith/propgrid/Makefile.am (arbetskopia)
@@ -1,4 +1,5 @@
INCLUDES = $(WX_CXXFLAGS) \
+ -I$(top_srcdir)/src/include \
-I$(srcdir)/contrib/include
AM_CPPFLAGS = -DWXMAKINGLIB_PROPGRID -DwxPG_USE_WXMODULE=0
Index: src/plugins/contrib/wxSmith/propgrid/contrib/src/propgrid/odcombo.cpp
===================================================================
--- src/plugins/contrib/wxSmith/propgrid/contrib/src/propgrid/odcombo.cpp (revision 6113)
+++ src/plugins/contrib/wxSmith/propgrid/contrib/src/propgrid/odcombo.cpp (arbetskopia)
@@ -104,6 +104,7 @@
#else
#undef USE_TRANSIENT_POPUP
#define USE_TRANSIENT_POPUP 0
+ #include "scrollingdialog.h"
#endif
// For versions < 2.6.2, don't enable transient popup. There may be
--- End code ---
MortenMacFly:
--- Quote from: afb on January 26, 2010, 10:00:57 am ---But it built with these modifications:
...
--- End quote ---
Jens and I have committed the modification to trunk. Can you please try again?
roxlu:
Hi Jens and others!
I finally build Codeblocks from source on a Mac 10.6.2!
1)
Though it can't get focus when I run it which is a wxWidgets problem because I did not create a bundle for my codeblocks executable yet. I'm reading about bundles but am I correct when I say that I can but libraries in the codeblocks.app/Contents/MacOS dir? And I've also seen the comment about this on http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X#FYI:_Universal_Binaries where they use the install_name_tool. Now I'm wondering what this install_name_tool actually does and if there is a build/make script which does this for you in the Code::Blocks repository?
- snip -
2)
I just copied some things and created my own codeblocks.app directory and now I can run codeblocks!
Though it still crashes when I try to open the File > New Project wizard. I haven't used the install_name_tool and Code::Blocks still runs, why?
3)
And in the CodeBlocks.app file I downloaded from www.codeblocks.org there are some Icon files in the bundle. Are they part of the repository?
Roxlu
eranif:
--- Quote from: roxlu on January 26, 2010, 10:11:38 pm ---I haven't used the install_name_tool and Code::Blocks still runs, why?
--- End quote ---
Because all the paths exists under your local machine. AFAIR, the install_name_tool replaces the replaces the hard coded absolute path with something like
(Assuming you copies the dylib to be located under the same path as the exe)
--- Code: ---install_name_tool -change /some/abs/path/wx-some-dylib @executable_path/wx-some-dylib ${file}
--- End code ---
but since you compiled the binary on your machine the absolute paths will work OK as well - but they will probably fail on another Mac machine
Eran
afb:
--- Quote from: roxlu on January 26, 2010, 10:11:38 pm ---Hi Jens and others!
I finally build Codeblocks from source on a Mac 10.6.2!
--- End quote ---
Congratulations :-) As you might have noticed I'm using the 10.4u SDK for portability.
--- Quote ---1)
Though it can't get focus when I run it which is a wxWidgets problem because I did not create a bundle for my codeblocks executable yet. I'm reading about bundles but am I correct when I say that I can but libraries in the codeblocks.app/Contents/MacOS dir?
--- End quote ---
Yeah, this is a generic problem with Mac OS X and not something specific to wxWidgets. For instance when you are running a Python program that wants an Aqua graphic user interface you have to use "pythonw" (which is a symlink into such a bundle) rather than just "python" which is a regular program. There's some hacks around it (as noted on the Wiki page), but the "easiest" (only supported) way is to make an app bundle. BTW, it should be called "CodeBlocks.app" as you are now allowed case sensitivity...
--- Quote ---And I've also seen the comment about this on http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X#FYI:_Universal_Binaries where they use the install_name_tool. Now I'm wondering what this install_name_tool actually does and if there is a build/make script which does this for you in the Code::Blocks repository?
--- End quote ---
The install_name_tool part is so that it can run from /Developer/Applications or ~/Applications or wherever the user wants it, instead of having to be installed under /usr/local which is hidden by the Finder and thus most users. There is a build script that does it, but not in the repository (yet) - at least not the latest version. I'll try to put it up after the next "nightly", when I've fixed some extra helper libraries needed by wxSmith.
--- Quote ---- snip -
2)
I just copied some things and created my own codeblocks.app directory and now I can run codeblocks!
Though it still crashes when I try to open the File > New Project wizard. I haven't used the install_name_tool and Code::Blocks still runs, why?
--- End quote ---
Presumably it can still find some things in /usr/local ? You'll need to copy the resources into the bundle, though.
--- Quote ---3)
And in the CodeBlocks.app file I downloaded from www.codeblocks.org there are some Icon files in the bundle. Are they part of the repository?
--- End quote ---
The icons are hidden under ./src/src/resources/*.icns. They need to be located in Resources in the app bundle.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version