> > 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. Ok. I had really looked at the wrong eclass. The correct eclass is wxlib. If I look as at a possible wx-using package like wxPython, seems that each package must be "ported" to wxMac / wxCocoa separately. I would think this could .lead to some conflicts with the package maintainers, doesn't it? Regards Dirk -- [email protected] mailing list
