Mac Build

[Xytan]

we have some leaks. are they intended?

WMLScenarioDetails and WMLEvent do not call .

and it seems that in some classes not all instance-vars are released. should i put my fingers in there and meddle with it? or should i just keep my hands to myself and wait for someone to fix it?

[lwa]

here’s the fix:

replace
LOCALEDIR=/usr/local/share/locale
with
LOCALEDIR="/usr/local/share/locale".
do this with all path-defines (LIBDIR).

it can not work the other way. if the compiler finds something like
dir = relocate (LIBDIR);
and LIBDIR is /usr/local/lib and not "/usr/local/lib" it has to throw an error.
Iwa, i don’t know how you made that work. maybe you compiled intl and msgfmt some long time ago and never called make clean?

Yes, that's what is done but Xcode 2.1 don't remember the values.
If you use FOOBAR="something"
It will be reparsed to FOOBAR=something.
It use the FOOBAR="something". It will work one time, but
if you reload the project, it will be rewriten to FOOBAR="something", etc.

Check the kit in
http://lwa.retiaire.org/wesnoth/MacComp ... wa.tar.bz2
The offending macro definitions are pushed in a plain file.

[lwa]

we have some leaks. are they intended?

WMLScenarioDetails and WMLEvent do not call .

and it seems that in some classes not all instance-vars are released. should i put my fingers in there and meddle with it? or should i just keep my hands to myself and wait for someone to fix it?

I don't know. This is parts of the Mac scenario editor. I'm unsure if it still maintained. If you don't use it, no such bug should appear.

[Xytan]

Yes, that's what is done but Xcode 2.1 don't remember the values.
If you use FOOBAR="something"
It will be reparsed to FOOBAR=something.
It use the FOOBAR="something". It will work one time, but
if you reload the project, it will be rewriten to FOOBAR="something", etc.

ok i upgraded xcode to the 2.2 seed.

Check the kit in
http://lwa.retiaire.org/wesnoth/MacComp ... wa.tar.bz2
The offending macro definitions are pushed in a plain file.

it works like a charm
i used it on the svn content.

would you delete the old mac-stuff from the svn and just check your new directory in? that would be great.

EDIT:
/usr/bin/ld: Undefined symbols:
int lexical_cast_default<int, char const*>(char const*, int)

but i found it. util.hpp was in the project (therefore no compile problems) but util.cpp was missing.

[lwa]

Yes, that's what is done but Xcode 2.1 don't remember the values.
If you use FOOBAR="something"
It will be reparsed to FOOBAR=something.
It use the FOOBAR="something". It will work one time, but
if you reload the project, it will be rewriten to FOOBAR="something", etc.

ok i upgraded xcode to the 2.2 seed.

With the upgraded build kit, you shouldn't have such need.

Check the kit in
http://lwa.retiaire.org/wesnoth/MacComp ... wa.tar.bz2
The offending macro definitions are pushed in a plain file.

it works like a charm
i used it on the svn content.

would you delete the old mac-stuff from the svn and just check your new directory in? that would be great.

No, it's an unnofficial build kit. In fact, if it was only for me, I just had used a Makefile instead of a Xcode project. This would avoid a lot of maintainance (I spend half a day to Xcodidfy gettext compilation)
and would be more modular.

EDIT:
/usr/bin/ld: Undefined symbols:
int lexical_cast_default<int, char const*>(char const*, int)

but i found it. util.hpp was in the project (therefore no compile problems) but util.cpp was missing.

With subversion sources ? Well, sound develloppers are at work. I wont fix this now because, 1) new files can appear or disapear at any time on the unstable version, 2) my mac is currently toasted.

It should be easy to fix if you already used xcode before.