Tiny Core Linux
Tiny Core Extensions => TCE Talk => Extension requests => Topic started by: Misalf on September 17, 2013, 10:01:11 PM
-
Anyone want to be so kind as to compile xfe file manager for TinyCore 5, please?
Jason W is too busy with dCore and what not and I'm not that experienced when it comes to compiling.
Thanks a lot.
-
Anyone want to be so kind as to compile xfe file manager for TinyCore 5, please?
Jason W is too busy with dCore and what not and I'm not that experienced when it comes to compiling.
Why not give it a go - there's plenty of people willing to help :)
-
Trying to be kind to myself by overcoming my laziness might create scanty material.
But well, if there is help..
I just installed / loaded compiletc.tcz, Xorg-7.7-dev.tcz and xorg-server-dev.tcz.
When 'make'ing fox-1.6.49, it complains about missing ftheader.h, even though freetype-dev is loaded.
Any advise?
-
The original error message just befor "compilation terminated." is:
/usr/local/include/ft2build.h:56:38: fatal error: freetype/config/ftheader.h: No such file or directoryIndeed, ftheader.h is in /usr/local/include/freetype2/freetype/config/
in "/usr/local/include/ft2build.h" it sais:
/* `<prefix>/includde/freetype2' must be in your current inclusion path */
Wats my 'inclusion path' and how can I see/set it?
Thanks
-
Hi Misalf
You could try executing this from the command line first:
export C_INCLUDE_PATH=/usr/local/include/freetype2More info can be found here:
http://stackoverflow.com/questions/558803/how-to-add-a-default-include-path-for-gcc-in-linux
-
Thanks
export CPLUS_INCLUDE_PATH=/usr/local/include/freetype2
did the trick.
-
Yay!
Seems to work, kind of. Some graphical glitches when xfe starts.
If I will be able to sort that out and if xfe doesn't crash I will submit updated fox.tcz and xfe.tcz.
-
That graphical glitches seem to have been temporary; disappeared after reboot.
In the original xfe.tcz.info file, it's mentioned that a Patch has been applied for mount/umount to work with flwn (typo?) and another patch for 'proper root Xfe button launch'.
Anyone knows something about these patches and if I should somehow apply them as well?
Mounting/Unmounting seems to work. Same for the root button.
-
Also, I have changed deps for Xfe:
from
graphics-libs-1.tcz
to
glu.tcz
+
libtiff.tcz
And added
libjpeg-turbo.tcz
+
libpng.tcz
Is it OK like that?
-
Dont you need fox?
-
Yes, I have as well compiled latest stable fox and created extensions. (:
Also everything seems to work (Xfe, Xfi, Xfv etc) but I'm not quite sure what I'm doing here so I hesitate to submit the .tczs. Would be a shame if I submit crappy extensions and others had to fix them.
-
Hi, if you have not yet read the extns wiki feel free to do so. Its been written and re-written on the back of some bad mistakes by no-one I know (eyes blinking rapidly)(grins like a sheep)
Secondly if you put all of your submission stuff into one folder and run submitqc5 against,
it will soon let you know if you made bad mistakes. Have submitqc5 as a part of the build script helps.
Forgive if you already know--but when you see the wiki referring to 755 and 775 its often easier to know what that means at a glance by running
ls -al /tmp/packagename/usr/local/tce.installed/packagename (example only)755 is rwxr-xr-x ( or two dashes)
while 775 has just the one missing world w rwx rwx r - x
TIP I like mc as it gives me colours for executables, white font for files and you can press F3 against an executable or shared object and see if you have stripped it or not.---where applicable.
good luck
-
Thanks for those hints, gordonselfish.
I have read the wiki and also ran submitqc5.
Good you mention file permissions which I should check if they are all correct (I didn't quite get what's this about and probably messed it up).
I don't care what file manager you use.. Xfe is also pretty magical. :)
-
Everything was tc:staff
I changed everything to root:root
It's correct like that, right?
(Neither Xfe nor fox are using start/launch scripts)
-
I believe so
I forgot to mention that after stripping, if you load the tce called file you can then run
file /tmp/package/usr/local/bin/filename
file /tmp/package/usr/local/lib/x-so/to also see that these are stripped....pathways may change of course.
I have never used xfe, I am currently receiving blood injections until my pcmanfm arrives ;)
-
Stripping means deleting unneeded files, right?
I have recreated the same package layout as JW did (*-dev, *-doc, ...) by hand for both fox and Xfe.
-
Stripping means removing the debugging symbols from the compiled files:
Static libs (*.a) --strip-debug
Dynamic libs (*.so*) --strip-unneeded
Executables (usually in bin/ sbin/ libexec/) --strip-all
You can check if a file has been stripped using the file command - "file /usr/local/lib/*.a" for example
-
From the wiki:
find . | xargs file | grep "executable" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null|
|find . | xargs file | grep "shared object" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip -g 2> /dev/nullI'm not sure how to run this line of commands.
The trailing "|" on the first line, as well as the leading "|" on the second line are confusing me.
Is that only one line in total?
Like so?
find . | xargs file | grep "executable" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null||find . | xargs file | grep "shared object" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip -g 2> /dev/nullOr like so?
find . | xargs file | grep "executable" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null | find . | xargs file | grep "shared object" | grep ELF | grep "not stripped" | cut -f 1 -d : | xargs strip -g 2> /dev/null
-
Hi Misalf
It appears the line happened to wrap around between the two | symbols. Since an extension can have both executables
and shared objects I would think you'd want to run both commands unconditionally, so I'm not sure why the || is in there.
-
Thanks
Executing 'both' lines, ignoring "||" from in the middle, seems to at least have an effect on files in dev folder.
-
Hi Misalf
It appears the line happened to wrap around between the two | symbols. Since an extension can have both executables
and shared objects I would think you'd want to run both commands unconditionally, so I'm not sure why the || is in there.
Erroneous newline in wiki corrected.
Would it be preferable to replace "||" by ";"?
-
No.
|| means if the left hand part returns false, do the right hand part.
-
I tryed that and it gave me an error.
I've then used both instead.
Extension already on its way by the way.
-
No.
|| means if the left hand part returns false, do the right hand part.
I was fully aware of that, but based on what I quoted I wondered if unconditional execution of both parts would possibly be preferable.
-
nice job Misalf with Xfe
thanks
-
Extension already on its way by the way.
What are the chances of a x86_64 version please ?
:p
-
nice job Misalf with Xfe
thanks
My pleasure.
I'm glad it works. Also for myself or Misalf. (:
What are the chances of a x86_64 version please ?
I did'nt yet set up a 64bit install of TinyCore.
While you're asking, I might do soon.
However, I'm not sure if I bacame the maintainer by submitting an updated version.
Compiling was straight forward except of
export CPLUS_INCLUDE_PATH=/usr/local/include/freetype2
so if you are faster than me I'd be good with it because I don't think I really need x64 and also have no experience in compiling for 64bit.
-
Hi,
On my system (core 5.1 with icewm) xfe has no letters only icons on folders and menu and does not appears on application menu. It can be run only from OnDemand menu and terminal. Earlier on core 4.7.7 all worked without troubles.
-
I havn't had much time lately to do anything Core related, so I'll have to reorganize a little.
I'll try to look into this in the next couple of days.
--
- Is IceWM the only WM you're using or just the only one where this happens?
- Which X server and Display driver are you using?
- Are you using UTF-8 or locale settings that require those?
-
Hi Misalf,
Sorry for late response.
I use only IceWM.
My X server is Xorg. Display driver xf86-video-nv.
Yes I use locale pl_PL.utf8 that requires utf8.
Here is my locale output:
LANG=pl_PL.utf8
LC_CTYPE="pl_PL.utf8"
LC_NUMERIC="pl_PL.utf8"
LC_TIME="pl_PL.utf8"
LC_COLLATE="pl_PL.utf8"
LC_MONETARY="pl_PL.utf8"
LC_MESSAGES="pl_PL.utf8"
LC_PAPER="pl_PL.utf8"
LC_NAME="pl_PL.utf8"
LC_ADDRESS="pl_PL.utf8"
LC_TELEPHONE="pl_PL.utf8"
LC_MEASUREMENT="pl_PL.utf8"
LC_IDENTIFICATION="pl_PL.utf8"
LC_ALL=
-
Thanks.
I'll try to recreate this.
I did test UTF8 before submitting the extensions, but I'm suspecting that FOX might better be compiled with an additional flag to maybe fix this problem in Xfe.
It might take a little longer until my next reply. :p
-
It might take some more time until I submit updated versions of FOX and Xfe, which I have already built and sent to Gawron via PM for testing - If Gawron is just as slow as I am (reasonable after my 'warning') that is, since I am unable to reproduce this bug.
So, if there is any demand for an updated version regarding fixing incorrect UTF8 character encoding, please send me a PM and I'll send you a link to the extensions before I will submit them to the repo.
Otherwise, I will just submit it as is, because I have actually no idea how to fix this issue (I thought I'd have taken care about it from the beginning by giving FOX the necessary compiling flag - but meh.. I use english.)
BTW, Xfe was updated to version 1.37 and includes a 'search' feature now.
-
Hi Misalf. I am sorry for slow response , I changed disk and OS on this old PC to Debian, and can't check the hardware compatibility with this new version. On VirtualBox everything is OK with pl_PL.utf8 and xfe. Thanks.
-
No problem. You've still been much faster than I was.
So the bug fixed itself / was caused by something else. No surprise since TC doesn't come with UTF8 support out of the box.
I will submit those updated extensions of FOX and Xfe.