wxperl seems to pick /usr/bin/wx-config for its wx-config, while it should pick whatever WX_CONFIG_NAME environment variable set in wxwidgets.eclass, similarly how configure based wx users do (assuming they use wxwin.m4 for this, as they are supposed to). From bug 144122: There might be issues when wx-config symlink points to wx-config-2.4, which it does if the system has both wxGTK versions installed. The wxwidgets eclass sets environment variables WX_CONFIG, WX_CONFIG_NAME, WXBASE_CONFIG_NAME which are then picked up by configure based build systems that properly use wxwin.m4 aclocal macros to handle wx versioning - see /usr/share/aclocal/wxwin.m4 -> AM_PATH_WXCONFIG explanation in comments. WX_CONFIG_NAME is the one that is used in 2.6's wxwin.m4 and others might be redundant, but I'd need to check 2.4's wxwin.m4 to be sure. With the current collision-protect violating mess with 2.4 and 2.6 it might happen that a system has wxwin.m4 from 2.4 installed. Once 2.4 is out the tree and I start looking at adding 2.8 (or 2.7 in p.mask) I will fix this mess with an eselect module or whatnot - however the build procedure will still have to obey WX_CONFIG_NAME or different means (that would have to be added to the eclass) for selecting the wx-config to use, as wx-config will be a means for users to select which version they want to use for self-compiled packages, while the portage provided packages need to go through the eclass and the WX_GTK_VER in the packages ebuild. I believe the magic in build/Wx/build/MakeMaker* doesn't honor WX_CONFIG_NAME and always just picks /usr/bin/wx-config, which will then get the configuration that agriffis got (2.4). If there is a solution found, it would be nice to see it incorporated upstream, as WX_CONFIG_NAME seems to be the way to do this (in addition to configure switches introduced by wxwin.m4 for per package basis)
Created attachment 113902 [details, diff] build Alien-wxWidgets with wxGTK-2.6 by default
Created attachment 113903 [details, diff] remove use of wxwidgets class wxperl depends of Alien-wxWidgets to get the wx configuration, this patch remove all use of the class wxwidgets
Hi, The problem is not wxperl but Alien-wxWidgets. wxperl doesn't use the WX_CONFIG variable at all, it gets all the wx configuration from Alien-wxWidgets who builds with the configuration it gets from /usr/bin/wx-config because the current ebuild (Alien-wxWidgets-0.30.ebuild) doesn't export WX_CONFIG. I submitted a couple of patches that must solve the problem forcing Alien-wxWidgets to build with wxGTK-2.6 by default. Sorry if I made a mess with the patches, I'm just learing to use bugzilla.
no, these are good. good catch. i actually have something very similar in my overlay.
Fixed.
