Tiny Core Extensions > TCE Talk
FLTK 1.4 for TC 16
curaga:
--- Quote from: hiro on February 06, 2025, 08:27:07 AM ---Is that because there's interest in maintaining both in parallel? Will everybody try and contribute to both things?
How are other people here planning to manage this transition? Personally I haven't left X land because my (extremely customized) window manager and favourite terminal are both X only.
--- End quote ---
Juanito was interested in doing one for it being the future. It's also less bloat if apps are only compiled for one screen tech. The repos weren't meant to diverge outside of that - command-line stuff could be copied, etc., or possibly a fallback check could be added. Contributing would be based on interest. But it's all still open for discussion I believe.
My personal opinion is that Wayland doesn't solve any issues I have, but it introduces several new ones. So I will be using X for the foreseeable future.
polikuo:
Hi, hiro.
--- Quote from: hiro on February 06, 2025, 08:31:09 AM ---what does that have to do with FLTK? sorry if i'm missing the context here.
--- End quote ---
Well, I'm sorta asking if we are going to LTO the FLTK extensions.
--- Quote from: hiro on February 06, 2025, 08:31:09 AM ---I disagree about your last sentence. I have increasingly used static linking
--- End quote ---
Would you mind elaborate a little more on that ?
So that we can know the benefits.
I'm a hobbyist at best in programming, I don't quite know where static linking is being used.
Right now, we have {fltk-1.3-dev(with static), fltk-xft-dev(with static), fltk-full-dev(with static)}
If I make it {fltk-1.4-dev(without static), fltk-xft-dev(without static), fltk-full-dev(without static), fltk-static(from fltk-full-dev)}
Will that break anything ?
GNUser:
--- Quote from: curaga on February 06, 2025, 09:24:26 AM ---My personal opinion is that Wayland doesn't solve any issues I have, but it introduces several new ones. So I will be using X for the foreseeable future.
--- End quote ---
Hi curaga. I have a frugal install of TCL + Wayland (labwc) on a separate partition. It is not better than my TCL + Xorg (fluxbox) daily driver in any way. In fact, the Wayland setup is considerably more complex just to (almost) achieve feature parity with the Xorg setup.
I keep my toes in Wayland just in case someday I have no choice between Xorg and Wayland. For as long as I have a choice, Xorg is clearly a better fit for me because it gives me more for less.
Rich:
Hi polikuo
--- Quote from: polikuo on February 06, 2025, 09:50:39 AM --- ... I don't quite know where static linking is being used.
Right now, we have {fltk-1.3-dev(with static), fltk-xft-dev(with static), fltk-full-dev(with static)} ...
--- End quote ---
Static libraries are only included with -dev packages. They are
not required when running programs that are linked to them.
Say we have a program called adventure and libraries
called libxyzzy.so and libxyzzy.a.
Most programs use shared libraries (so=shared object).
If adventure gets linked to libxyzzy.so, then that library
must be present on the system for adventure to run.
When adventure gets linked to libxyzzy.so, it doesn't pull
in any code. The linker just tells adventure where it can
find the functions provided by libxyzzy.so.
If adventure gets linked to libxyzzy.a, then that library
is not needed on the system for adventure to run.
When adventure gets linked to libxyzzy.a, it does pull
in code. The linker finds the needed functions provided
by libxyzzy.a and adds them to adventure so it can run
stand alone.
Static linking allows a program to not be dependent on
which library version is present. The cost is a larger
program because needed functions are compiled in.
hiro:
--- Quote from: curaga on February 06, 2025, 09:24:26 AM ---It's also less bloat if apps are only compiled for one screen tech.
--- End quote ---
This may be, but it needs a good consensus to avoid a situation like the ipv4/ipv6 switchover. I would call this the best-case scenario.
It will be more bloat if apps are compiled for both screen tech.
I got wayland forced upon me at work in some instances, which still creates a huge instability in my everyday work days whenever I err on not simply ssh'ing in from my tinycorelinux laptop, so other distros are not doing good advertisement work to foster the adoption rates of wayland.
I kinda trust you guys here, so my hope was to wait before trying to voluntarily use wayland again until tinycorelinux shows me how it's done correctly. ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version