User forums > Help

Upgrading codeblocks using darwinports + wiki instructions

<< < (2/2)

afb:
Another thing to consider is whether we want the application to link towards an external "wx.framework", instead of including the wx libraries in the bundle itself...

I didn't want to do an internal framework, since wx comes with almost 20 MB of header files that seemed redundant if you couldn't use it from your own projects anyway ?

libwx_mac-2.6.0.3.1.dylib is 14M (unpacked) for the Universal Binary, so that's 33% of the entire application bundle. But DLL Hell with wx versioning isn't very fun either...

bnilsson:
I downloaded rev 3002 fresh, applied patches,
./bootstrap
./configure --enable-contrib --prefix=$HOME CXXFLAGS=-I/opt/local/include LDFLAGS=-L/opt/local/lib
make
make install

and moved all (bin,lib,share/codeblocks) to MacOS and Resources according to wiki.
cd Contents/MacOS
install_name_tool -change ~/lib/libcodeblocks.0.dylib @executable_path/libcodeblocks.0.dylib CodeBlocks
install_name_tool -id @executable_path/libcodeblocks.0.dylib libcodeblocks.0.dylib

Started CodeBlocks but no plugins found.
A yellow popup message window reported a "list of failed plugins: lib<pluginnames>.so" .

Any suggestions?

afb:
Sorry, haven't yet added to the Wiki that you should change
*all* of the libraries (.dylib) and bundles (.so) not just one...
So you should repeat the process for your plugins, or they
will look in the wrong dir for their libs (check with otool -L)

afb:
If you find it easier while debugging, you can just leave the
binaries and libraries under /usr/local and set up symlinks ?
(and this is what the DarwinPorts build does, for wxMac build)
Alternatively you can avoid the bundle and use the old Rez.

Navigation

[0] Message Index

[*] Previous page