From: Pete S. <pst...@gm...> - 2008-12-02 15:01:01
|
DM>> Well, I suppose if Kevin didn't install debug + release DM>> versions of wx. that -may- explain it... tex2rtf is built against a release version of wxWidgets. Jazz++ is built against a debug version. From the log, when tex2rtf is run it is finding the debug build of wxWidgets as indicated by... The library used 2.8 (debug,ANSI,compiler with C++ ABI 1002,STL containers) but tex2rtf want a release version as indicated by... and your program used 2.8 (no debug,ANSI,compiler with C++ ABI 1002,STL containers) where "your program" is tex2rtf. Note the "no debug" in the second entry. DM>> but then, going by his log, the jazz build -did- DM>> find the release version??? No it did not. The jazz build didn't compile any single file. The first step is building help, and that failed. No Jazz++ files were even compiled in the build log. If Kevin followed the build instructions, Jazz++ doesn't build against the release version of wxWidgets, but the debug version. DM>> ....so I presumed he did build both...otherwise things DM>> wouldn't have complained? KC> I built only the "release", not the "debug". Then you are not following the wxWidgets build instructions on the web site. The web site has you build both a release (for tex2rtf) and a debug version (for jazz) of wxWidgets. The old instructions only had you build a debug version. The Jazz++ build instructions have always used the debug build of wxWidgets. This is specified in the configure line... ../jazz/configure \ --prefix=/usr/local/Jazz++ \ --enable-debug \ --enable-alsa \ --enable-sequencer2 with --enable-debug. This triggers the use of the debug version of the wxWidgets build. KC> What's the debug for anyway? It seemed unused to me. This allows you to use gdb to get a back trace if Jazz++ crashes while you are using it. Pete |