This morning I updated tn5250 cvs to not require glib anymore. I've been
running it with my changes for a while now without problems. Hopefully
this change should help Marc-Antoine with his work.
Next is removing the python code. This should be pretty straightforward.
I've already done most of it (but it isn't in cvs).
I'm wondering about lib5250.so. Because cursesterm.c is compiled as part
of the build, lib5250 depends on curses. This shouldn't really be
necessary considering that all the curses code should be in the curses
terminal, not the 5250 library. For example, x5250 has no need of curses
support. I'd like to be able to build lib5250 without curses or slang or
any terminal at all.
Finally, can anyone think of a way I could have the terminal start and
stop the trace at any time? I'd like to add a button to x5250 that turns
on the trace and then turns it off, instead of starting the trace from the
very beginning of the program.
It's not the software that's free; it's you.
- billyskank on Groklaw
This mailing list archive is Copyright 1997-2020 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