OpenEuphoria

Re: Building wxEuphoria with 2.9

• Posted by mattlewis (admin) Dec 17, 2011
• 1970 views

Sorry, I meant installing wxWidgets itself after it is built. I should put all of the wxWidgets stuff somewhere in the msys bin directories so that it would be a part of msys. One thing it does is create a script called wx-config, which can be used to get lists of flags or libraries that need to be linked or lots of other useful information. Then, instead of the hard coded junk, the msys build could be just like the process on *nix, and a lot more robust.

I haven't tried it under msys, so I'm not sure if it will actually work. I suspect it should. As I mentioned, it worked for me when cross compiling. I built both a 32-bit and 64-bit windows version of wxWidgets for windows using my system's windows cross compilers, and it installed the wx-config, setup.h, include files and libraries in the appropriate place, e.g.:

/usr/x86_64-w64-mingw32/include/wx-2.9/wx/... 
/usr/x86_64-w64-mingw32/wxbase292u_gcc_eu.dll 
/usr/x86_64-w64-mingw32/lib/wx/include/x86_64-w64-mingw32-msw-unicode-2.9/wx/setup.h 
/usr/x86_64-w64-mingw32/bin/wx-config 

Once that was done, the wxEuphoria configure script would probably need to be updated to remove all of the Windows hardcoding stuff. Specifically, at least this:

if echo "$UNAME_SYSTEM" | grep MINGW > /dev/null; then 
	if [ "$1" = "" ]; then 
		echo "You must supply the path to wxWidgets" 
		exit 1 
	fi 
	echo PREFIX=$1 >> Makefile.gcc 
	echo CC=gcc >> Makefile.gcc 
	echo include Makefile.mingw >> Makefile.gcc 
	exit 
fi 

Then building on msys and cross compiling (or regular *nix compiling) would basically be the same, which would actually simplify things.

Matt