Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: harjoc on May 09, 2011, 06:19:48 AM
-
Hello,
I am trying to build a wxWidgets GUI for tinycore that uses existing 64bit binary-only firmware.
Comparing the contents of microcore.gz and microcore64.gz shows that only the kernel modules are different. The entire userland is still 32bit.
I am contemplating rebuilding for amd64 all the libraries my GUI depends on (libc, libstdc++, X libs, gtk, wx, etc). Is this at all feasible ? I've had some success rebuilding wxGtk, but would certainly rely on someone else's efforts, if this has already been done.
Thanks for any pointers or "don't do it" advice!
-
What do you mean by "64bit binary-only firmware"?
-
The application is a GUI for an av-engine, and it uses already installed signatures. If those signatures are 64-bit (from a 64-bit Windows partition) then the GUI has to be compiled for amd64 as well.
-
It would be easier to build statically on an existing 64-bit install, and then deploy the static binary. Both ways are possible though.
-
Thanks, that's what I'll most likely do.
But I will end up with 32bit as well as 64bit versions of libc, libstdc++, Xlib, etc. A dynamic binary would save ~15M of space, plus I'll need to build the libs on tinycore anyway, to be able to link against them.
-
?
Just build on $DISTRO of your choice, 64-bit ubuntu fedora etc, statically. Assuming their libc is ok with our kernel (most are, much more conservative than we are), it will run.