Hi dear Olly,
> Il Sabato 24 Maggio 2014 15:31, Olly Betts <[email protected]> ha scritto: > > I've just discovered an annoying consequence of this change. > > If you now install libwxgtk3.0-dev and ask for libraries to link with, > you get: > > $ wx-config --libs > -L/usr/lib/x86_64-linux-gnu -pthread -lwx_gtk2u_xrc-3.0 > -lwx_gtk2u_webview-3.0 > -lwx_gtk2u_html-3.0 -lwx_gtk2u_qa-3.0 -lwx_gtk2u_adv-3.0 -lwx_gtk2u_core-3.0 > -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0 > > Note that this includes "-lwx_gtk2u_webview-3.0", but that's not > installed, so linking fails. The same thing happens if you ask for an > explicit list of libraries and include "std" in that list. > > This is pretty serious as it's likely to cause packages to FTBFS. > > Some options I can see for fixing this and their downsides: > > * Make libwxgtk3.0-dev depend on libwxgtk-webview3.0-dev - this would > pull in libwxgtk-webview3.0-0 and hence webkit for such builds; it > may also sometimes end up with webkit getting unnecessarily included > as a runtime dependency, for packages which don't link with > -Wl,--as-needed. This seems ugly, at least on debian (no changes on ubuntu, I wonder if debian will ever se them as default) > > * Alter the meaning of "std" in wx-config - makes it behave > differently > on Debian to elsewhere. > This is something I didn't understand correctly, but I think I did something similar > * Update all packages to explicitly request the wx component libraries > they actually need - significant fiddly work, but perhaps the way > forwards. This seems to require a lot of uploads... I'm attaching a little patch I did to make wx-webview behave a more little closer than wx-media... However I'm stuck with a little problem: how can I use wx-config to export wx-media libraries? I think we can make it return wx-webview only if the library is found on the system, with this patch I made webview optional, next step is to understand how wx-config really works (I fall asleep before understanding it completely). I see wx-config already have some loops inside looking for libraries on the system, my approach will return the flags only if found on the system, and since this webview is marked as mandatory but seems optional I think we can push this patch also upstream. Is that what you intended in #2? for me if I can fix this last problem we can ask even for an upstream inclusion. Do you want to let this package reach testing? maybe reopening and reassignig the severity will prevent automatic rebuild failures... what do you think? cheers, Gianfranco > > Any better ideas? > > > Cheers, > Olly >
debdiff
Description: Binary data
debdiff
Description: Binary data
