> > Any chance to get a virtual/wx which I can package.provide against? > Difficult, as it requires to decide at build time which wx to use, see > wxwindows (or was it wxwidgets) eclass.
> You'd have to overlay the eclass and the packages building against it. If I look at the eclass (provided that I found the correct one ;) it seems that there are some conceptual problems. In the ebuild you can specify which backend you (as ebuild developer I suppose) want want to use, while you still have to link against the correct "backend" libraries. Would it be possible that you could use a (cross platform) wxwidgets package where the actual libraries to be used are calculated in the eclass. Possibly I am completely off her ;) A package like wxPython which explicitly depends on WxGTK is not really helpfull for a cross platform library... Regards Dirk -- [email protected] mailing list
