bochs-2.2.6 was released in January http://bochs.sourceforge.net/getcurrent.html http://cvs.sourceforge.net/viewcvs.py/bochs/bochs/CHANGES?rev=REL_2_2_6_FINAL&content-type=text/vnd.viewcvs-markup
Created attachment 85215 [details] bochs-2.2.6 ebuild
Created attachment 85216 [details] wxwidgets.eclass the version detection of ld spits out an error, this fixes it up
Created attachment 85217 [details] wxlib.eclass same error was in this one too
Created attachment 85241 [details] bochs-2.2.6.ebuild updated to use gtk2 Need to run autoconf, otherwise gtk1 libs are used. Patch from FC5 to fix the wx GUI to use wxWindows unicode correctly. Patch for the few cases the FC5 one misses.
Created attachment 85242 [details, diff] patch from FC5 to fix wx GUI to use wxWindows unicode
Created attachment 85243 [details, diff] Few cases the FC5 patch missed
the eclass fixes should be discussed with the wxwindows team
Ok, I think now I know what the eclass changes in bug #130899 are actually meant to do. I'll try to take a look at these in the near future (0-2 days).
any chance of getting this into portage? (even if it's hard masked)
wxwindows.eclass issues should be long resolved. I believe Flameeyes simply removed all kind of LDFLAGS filtering, whereas the filtering was causing the problem in certain cases. No filtering, no problems.
Closing bug
Created attachment 88715 [details] bochs-2.2.6.ebuild with wx unicode fix Reopening this bug, (or should I start a new one?) Anyway I've added a unicode USE flag to the ebuild, otherwise the compile says * Using /usr/lib/wx/config/gtk2-ansi-release-2.6 even if wxGTK was compiled with the unicode USE flag. The new changes are minimal (3 lines) and the ebuild now uses the correct wxconfig: * Using /usr/lib/wx/config/gtk2-unicode-release-2.6
Reopening
This was added ages ago.
