|
On Thu, Mar 14, 2002 at 07:27:08PM -0700, James Rich wrote: > On Thu, 14 Mar 2002, Scott Klement wrote: > > > One small problem, though. b0-16 does not use glib. (Only HEAD uses glib) > > > > That's why the Windows support only exists in 0-16, because of glib. > > (Yes, I know they make glib for Windows, but it's beta-only, and I haven't > > had a chance to download and play with it.) It's not beta! I used it _years_ ago, when gtk+ on Windows was not even alpha software, and glib was solid as a rock with Tor Lillqvist's changes folded back into the main tree (it's not that I feel the need to give credit, I just love the dude's name). In fact, separating glib from gtk+ was partly motivated by the fact that glib was useful and more portable than gtk+. I think making the Windows port use glib would probably make things easier. > > Because of this I assume that scs2pdf won't work under Windows (scs2pdf > uses glib)? I wonder if glib has some sort of pipe or other inter-process communication feature? It seems likely, as Tor was running into pipes not working those million years ago-- he was porting the Gimp, and Gimp plugins use pipes for communication. I think I suggested using TCP sockets, as they pretty much work accross platforms. > > James Rich > james@eaerich.com > > _______________________________________________ > This is the Linux 5250 Development Project (LINUX5250) mailing list > To post a message email: LINUX5250@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250 > or email: LINUX5250-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/linux5250. -Jay 'Eraserhead' Felice
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.