Originally Posted by
Pekele
No doubt that installing wx-widget is the easier way.
By default the wxWidgets has the prefix path /usr/local/lib, and this gets embedded into the product which you can confirm with
Code:
otool -L /Users/Pekele/wxMac-2.6.3/build-unicode-debug/lib/libwx_macud-2.6.0.dylib
. This path is then copied into the executable as the place to look for this library. At some point in the future, Xara may decide to link everything statically, in which case this problem will go away, but I think that using dynamically linking is the correct course for the moment (and may be under all circumstances, we shall have to see).
Clearly, if you put the library in that place then everything is sweet. So go to your wxWidgets directory and issue the command . Then return to your Xara directory and issue the command . It will now run. Use if you want to use the debugger.
You may get some run time errors.
(Now I am giving these commands from memory, and I haven't checked them today on a Mac, so kindly let us know at once if any errors have crept in, which is quite possible).
Also note that this technique cannot be used to deliver XaraLX as we cannot expect end users to install libraries in a place of our choosing - and I would be circumspect about expecting developers to do so, as well - but in this case, everyone knows that if you want to hack on XaraLX, you need wxWidgets, and the additional effort in putting libraries into /usr/local is not going to be off-putting, I would venture.
Good Luck.
Bookmarks