Catapult's build system can't find my wxWidget install

[madcrow]

I installed the complete wxWidget set of stuff, both the libraries and the headers, in order to compile Catapult on my OpenSuSE 11 box. The script finds the headers, but not the libraries themselves. Is there a way I can force the build system to build anyway or do I have to do something else. I'm using Catapult 0.6.3, btw, as I have no desire to be running untested CVS/SVN snapshots on my system.

[Manuel]

I'm not running SUSE, so I asked mth to check with you on this...

Anyway, about SVN versions: there's not much to fear. Worst that can happen is that it doesn't work. But usually it works fine. They're not untested either, just not as well tested as for a release and there could be stuff in development on it. You can help us a lot by trying SVN versions and giving us feedback about them. Lots better than finding critical problems *after* a release!

You could also try the new Catapult (which is a prototype with loads of functionality), which is in SVN. It requires Python, Qt4 and PyQt4. You may actually like it a lot more than the old wx Catapult, which is not really maintained anymore.

[mth]

On my SUSE 10.3 system, I get:

Code: Select all

Found libraries:
  wxWidgets:       2.8.8
  wxWidgets XRC:   yes
  libxml2:         2.6.30


Which of the 3 libraries are not found on your system?

Please look in the log file (derived/x86-linux-i686/config/probe.log) for error messages and post them here.

[wal7er]

There is an error in built/probe.mk
package used: openmsx-catapult-0.6.3-R1

line 119:
error : @echo "int main(char **argv, int argc) { return 0; }" > $(OUTDIR)/$@.cc
correction : @echo "int main(int argc, char **argv) { return 0; }" > $(OUTDIR)/$@.cc

explanation:
gcc never compile a program whose main is int main(char** argv, int argc)
rather than int main (int argc, char **argv)

Now it works with:
wxWidgets: 2.8.7
wxWidgets XRC: yes
libxml2: 2.6.32
on x86 64bit

good msx-ing

[Manuel]

Ah, indeed, you're right, we've fixed that in CVS 7 months ago:
http://openmsx.cvs.sourceforge.net/view ... 12&r2=1.13

but we didn't make a release yet... Sorry for this bug! Using the latest CVS (or mostly SVN) version can help.