From: Achim G. <Str...@ne...> - 2020-06-07 06:11:55
|
Ethan A Merritt writes: >> I'm the maintainer for gnuplot on Cygwin and as long as the Qt/Cygwin >> problem isn't properly solved > > Thank you for reminding me of that problem. > I reviewed the original report and the trail of issues filed with the > Cygwin and Qt upstreams. It seems that nothing came of either after > the first flurry of investigation. It sort of got stalled, yes. The consensus was that the patch proposed would probably have unintended side-effects and that the bug was likely within Cygwin itself. > However one point was raised which you might know more of. > As I understand it, the original diagnosis was that Cygwin was using > named pipes to emulate unix sockets. But that was corrected by > Corinna Vinschen, who said that Cygwin was moving towards using > named pipes but was [at that time] using loopback IPv4 sockets to > implement AF_UNIX sockets. That was more than a year ago. > Has the situation changed? If switching to named pipes would > resolve this problem and the work is planned anyhow, perhaps it is worth > prodding to see how close to completion it might be? Since then there was a lot of work done on pipes which is still not complete (and I think at least two bugfixes for the socket code), but unfortuntaley it didn't remove the bug that's the problem for gnuplot so far. > No, sorry. There is not a gnuplot variant that uses wxWidgets as an outboard > driver. About 10 years ago there was some work to create one because at the > time the inboard driver did not work on OSX, but it never reached completion > and also I think the OSX problem resolved itself. > https://sourceforge.net/p/gnuplot/patches/380/ OK, that's a bit disappointing even though semi-expected. I have resolved for now to building gnuplot five times with different configuration options (which fortunately is fast enough on my new build machine), package the various bits and pieces separately so that users can mix and match and then using alternatives to select the correct executables. Instead of having outboard drivers running a s a separate process as you use for X11 and Qt may driver modules could work? The problem for packagers really is that e.g. wx pulls in about half of the GNOME stack as a dependency and it's linked to the executable. Having that dependency chain in a separate library that could be dynlinked if and when the driver was actually used would alleviate that problem. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves |