[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]

Re: [XaraXtreme-dev] Xcode project query

Hi Ben,

I haven't been able to spend as much time on this as I would like over the last few days.

Your reference to the info about ZeroLink was spot on, thanks. The key is to realise that ZeroLink is enabled in two levels and that / both/ have to be turned off to get normal linking. (I.e. both in Target Options and Project Options). The project now attempts to link and I am working through the undefined symbols. Some of them may be caused by the xcode project containing files which are not in the makefile. A methodical (semi-automated) way of transferring that file list from the makefile to the xcode project would be very useful - I'm doing it empirically at the moment, similar to your .o file presence test.

Stefan kindly sent his xcode project to me but I haven't tried to build it yet.

As you hint, we might be better off dynamically linking to wxWidgets in the long run (I imagine we would supply a version of libwx_mac.dylib in the XaraLX bundle to guarantee that the program remains stable no matter what other version of wxWidgets might be installed on the machine) but for now getting any version to link in Xcode and will be a major step forward. So I'm concentrating on static linking for now.

Should be able to tell you more later today.


On 10 Apr 2006, at 13:10, Ben Fowler wrote:

On 06/04/06, Phil Martin <phil@xxxxxxxx> wrote:

I am not quite sure where you have got to.

...there may be some files missing and they should show up during linking. ...

See later. Working with your project file, I get about 690 mising symbol errors.

Note that I found that during compilation I had to replace one call
to _tcsdup with wxStrdup but since that change is speculative I
haven't checked it into SVN yet. You'll find it!

I think that I did. IIRC I found 17 errors in around two files. One
might be fairly simple:

Index: Kernel/epscdef.h
--- Kernel/epscdef.h    (revision 795)
+++ Kernel/epscdef.h    (working copy)
@@ -154,6 +156,6 @@

 // An empty definition to pass back when problems occur.
-const EPSCommentDef EmptyDefinition ( "", "", FALSE, 0 );
+const EPSCommentDef EmptyDefinition ( _T( "" ), _T( "" ), FALSE, 0 );


The other was cameleps.cpp  and I don't think that this file is needed
at the moment.


If I find time, I will try this again. Are you asking for a list of
Xara source files to be added to the project? I am fairly sure that
basestr.cpp is one.

Would it be sense to work from the list in Makefile.am .

What I did was to go by which .cpp files had corresponding .o files.

Also, I had to go back to wxWidgets and create a 'monolithic' library
(Was this the right thing to do?): If you did this you re-named it.

Looking around on the web, there is support for the wxWidgets as
static library approach, but I suspect that this may not be the best
long term route, clearly it is the obvious thing to do at the present.
Rightly or wrongly, I compiled ir with --enable-debug, and this may
have been a mistake.

I need to look for a few MacOS wxWidgets projects.


On 6 Apr 2006, at 15:46, Ben Fowler wrote:
On 06/04/06, Phil Martin <phil@xxxxxxxx> wrote:
I've created an XCode project ... but
once it has created all the .o files, instead of linking them
together it "Bundlizes" them, making a corresponding .ob file for
each .o file.

 Isn't it meant to do that?

I can't find out why it's doing this or how to change it. Anyone any

You are possibly several steps ahead of me: I am trying to create
wxOil. Kernel and now tools Frameworks as targets within a XaraLX
project, and am having hideous problems linking owing to hundreds of
undefined symbol errors.

I do look forward to seeing your project, mind.