[sword-devel] gnomesword compile error

[Andy Piper]

Benedykt P. Barszcz said:
> perhaps anybody could help:
>
[snip]
> -MF ".deps/sw_sword.Tpo" -c -o sw_sword.o sw_sword.cpp; \
> then mv -f ".deps/sw_sword.Tpo" ".deps/sw_sword.Po"; else rm -f
> ".deps/sw_sword.Tpo"; exit 1; fi
> /usr/include/sword/localemgr.h: In function `void
> initSWORD(SETTINGS*)':
> /usr/include/sword/localemgr.h:57: error: `
>     sword::LocaleMgr*sword::LocaleMgr::systemLocaleMgr' is
> protected
> sw_sword.cpp:282: error: within this context
> make[2]: *** [sw_sword.o] B?a;d 1
> make[2]: Leaving directory `/home/kb2qzv/gnomesword/src'
> make[1]: *** [all-recursive] B?a;d 1
> make[1]: Leaving directory `/home/kb2qzv/gnomesword'
> make: *** [all] B?a;d 2
>
> This is a CVS copy of both gnomesword and sword.

It turns out that to compile GnomeSword against current CVS
versions of SWORD you should configure with --enable-sword_cvs.
This works in some additional changes made to the SWORD API
since v1.5.7. We should probably update the docs and website.

The critical thing here is a recent change to localemgr.h in
SWORD. GnomeSword compiles fine against 1.5.7 of SWORD. These
CVS log entries from SWORD hold the key:

revision 1.18
date: 2004/02/06 21:01:00;  author: scribe;  state: Exp; 
lines: +6 -4
Changed system[Log|File|Locale]Mgr to
Mgr *[get|set]System*Mgr() per Daniel Glassey's
discovery of potential problems from order of
initializing statics.

Added new prefix recognition for OSIS lemma prefix
"strong:"
----------------------------
revision 1.17
date: 2004/02/05 10:24:36;  author: dglassey;  state: Exp; 
lines: +4 -4

dglassey: change systemLocaleMgr to a function that returns the
static object
----------------------------

-- 
Andy Piper - Farnborough, Hampshire (UK)
http://jumpgate.homelinux.net/