Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: LazyLarry on December 07, 2013, 10:13:34 PM
-
AM I correct in assuming that all tcz files need to be rebuilt following the release of TC5.X? I'm not sure how this works, but is there any way to request qt creator be done sooner rather than later?
-
Not all extensions need to be rebuilt.
Probably the best thing to do is to test tc-4.x extensions in tc-5.x and report those that do work in the thread created for this purpose. The working extensions can then be copied to the tc-5.x repo.
The extensions that don't work in tc-5.x should be reported via pm to the maintainer with a request to recompile them to work in tc-5.x
-
So I'll need to copy them from the optional dir on a 4.x install ? And all the dependencies too? And not overwrite a newer version. Bit of a mouthful for qt-creator :-(
-
You can download them directly from the 4.x repo using:
$ wget -c http://www.tinycorelinux.net/4.x/x86/tcz/extension_name.tcz
..and only download deps that are not present in the 5.x repo.
-
Hi libpng_base-dev.tcz
Assuming they are compatible, you will have to change Xorg-7.6-lib.tcz to Xorg-7.7-lib.tcz in the dependency file.
@Juanito: I see libpng_base-dev.tcz is a dependency, does that mean recompiling is necessary?
-
@Juanito: I see libpng_base-dev.tcz is a dependency, does that mean recompiling is necessary?
Almost certainly, but you can easily check using "ldd" on the libs/executables in the extension - if you see libpng12 in the output, then the extension needs recompiling.
-
I think I might have worked around it. My app needed qt-4.x-base.tcz, which I got from your link, and also libpng.tcz. However, 5.1 already has libpng, so i renamed the libpng from the older version, included the renamed one and the app runs. I was missing lib12.so.0. the new libpng has lib16* files, so maybe there's no overlap.
Did I get out of jail?
-
Using the qt-4.x-base extension from the tc-4.x repo under tc-5.x:
$ ldd /usr/local/lib/libQtGui.so | grep found
libpng12.so.0 => not found
..so the extension will need to be recompiled - I suggest you pm the extension maintainer.