Compiling Metisse, a 3D desktop

FreddoNotAFrog · 2015-04-13 07:49:22

Hey,
I've found a pretty cool desktop window manager called Metisse. Essentially it does some things that Compiz doesn't.... at least Compiz 0.8.x (0.9 doesn't work with my laptop's graphics )

I've downloaded it from http://insitu.lri.fr/metisse/ and following the instructions. The other one, Nucleo, needs to be compiled first. If anybody would like to have a go, I've patched most of the files, and managed to get it to run, just let me know and I can upload somewhere.

However, compiling it has been a bit of a hassle - I spent most of today (NZ time) trying to compile, without success.
After tweaking several of the files and removing errors (thanks, Google!), it comes up with another error that nobody seems to have been able to solve recently:
(The 'Entering, Leaving, nothing to be done' is simply because this isn't the first time I ran 'make', so it had already done everything for those folders.)

[lyndon@LyndonArch metisse-0.4.1]$ make
make  all-recursive
make[1]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1'
Making all in doc
make[2]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc'
Making all in docs
make[3]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc/docs'
make[4]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc/docs'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc/docs'
make[3]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc/docs'
make[3]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc'
make[2]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/doc'
Making all in fvwm-insitu
make[2]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu'
make  all-recursive
make[3]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu'
Making all in libs
make[4]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs'
Making all in .
make[5]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs'
Making all in libgfvwm
make[5]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs/libgfvwm'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs/libgfvwm'
make[4]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/libs'
Making all in fvwm
make[4]: Entering directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/fvwm'
gcc -DFVWM_MODULEDIR=\"/usr/local/libexec/fvwm-insitu/2.5.20\" -DFVWM_DATADIR=\"/usr/local/share/fvwm-insitu\" -DFVWM_CONFDIR=\"/usr/local/etc\" -DFVWM_COLORSET_PRIVATE=1 -DLOCALEDIR=\"/usr/local/share/locale\" -Wall -Wno-implicit-int -g -O2   -o fvwmi menus.o style.o events.o move_resize.o add_window.o builtins.o borders.o icons.o fvwm.o module_interface.o frame.o virtual.o stack.o ewmh.o menustyle.o session.o colorset.o placement.o functions.o gnome.o focus.o conditional.o geometry.o ewmh_events.o windowlist.o menuitem.o ewmh_icons.o decorations.o update.o expand.o misc.o functable.o bindings.o cursor.o colormaps.o ewmh_conf.o modconf.o read.o menucmd.o ewmh_names.o icccm2.o schedule.o windowshade.o focus_policy.o repeat.o execcontext.o menudim.o condrc.o metisse.o -L../libs -lfvwm -lXft   -lXpm -lstroke -lSM -lICE -lXinerama -lXext -lX11  -lm  -lXrender  -lpng -lz  -lXtst -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0  
/usr/bin/ld: ../libs/libfvwm.a(Fft.o): undefined reference to symbol 'FcPatternDel'
/usr/lib/libfontconfig.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:427: recipe for target 'fvwmi' failed
make[4]: *** [fvwmi] Error 1
make[4]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu/fvwm'
Makefile:392: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu'
Makefile:331: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1/fvwm-insitu'
Makefile:346: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/lyndon/Downloads/metisse/metisse-0.4.1'
Makefile:266: recipe for target 'all' failed
make: *** [all] Error 2

The interesting part - to the best of my limited knowledge - is just before the 'collect2:error' line, where it says:

/usr/bin/ld: ../libs/libfvwm.a(Fft.o): undefined reference to symbol 'FcPatternDel'
/usr/lib/libfontconfig.so.1: error adding symbols: DSO missing from command line

Has anybody tried Metisse recently, and managed to get it working on Arch? If so, please do let me know!

Cheers,
Freddo

Lone_Wolf · 2015-04-13 12:04:50

http://stackoverflow.com/questions/1990 … mmand-line

Basically the linker can't find the library that defines 'FcPatternDel' .

Once it's figured out which library provides that symbol (maybe one the fontconfig libraries ? ) it can be added to the gcc line that needs it using
-lsomelibrary .

FreddoNotAFrog · 2015-04-13 23:33:09

Lone_Wolf wrote:

http://stackoverflow.com/questions/1990 … mmand-line
Basically the linker can't find the library that defines 'FcPatternDel' .
Once it's figured out which library provides that symbol (maybe one the fontconfig libraries ? ) it can be added to the gcc line that needs it using
-lsomelibrary .

Thanks Lone_Wolf, the library is -lfontconfig, which I added to a 'link' line. There's now another error, complaining about:

../libs/libfvwm.a(PictureImageLoader.o): In function `PImageLoadPng':
/home/lyndon/Downloads/metisse2/metisse-0.4.1/fvwm-insitu/libs/PictureImageLoader.c:211: undefined reference to `png_set_gray_1_2_4_to_8'

Apparently they changed 'png_set_gray_1_2_4_to_8' to 'png_set_expand_gray_1_2_4_to_8' in an older version, but it doesn't like it when I change the makefile to that either... any ideas?

Cheers,
Freddo

solar · 2015-04-14 04:25:14

Thi has also to do with library versions.. you are gonna have to hack away or link it to older libs, eg. statically for example.

fvwm-insitu/libs/PictureImageLoader.c:211 <- check the code, check headers for png_set_gray

png might be the libpng but it might be referring to an older lib which has since updated/removed that reference.

Hint.. when debugging such things, using grep -rl and grep -r are quite useful !

with l will just list the files which contain your pattern, without it and it will list the actual pattern withint the files.

FreddoNotAFrog · 2015-04-18 06:09:12

Hi all,
Solar, thanks a dozen. You were right about the PictureImageLoader.c - in the headers it referred to another file, which had png_set_gray, which needed to be changed to png_set_expand_gray. Worked like a charm.

Since then I've had to add $(FC_LIBS) to the 'link' line in several makefiles; the 'DSO Missing from command line' is a recurring problem that is easily fixed.

It turns out that I now have to install several 32 bit libraries to make it work. Lib32-pam doesn't want to build from AUR... it's complaining about a patch that is already applied or reversed, so rejecting the current one. Anyway, shall hack away at that.

I think I'll leave this thread open because I'm anticipating more issues to pop up that I'll need help with.

Cheers,
Freddo

metak · 2015-06-06 12:48:15

Hey @FreddoNotAFrog!

Could you please post an update on your progress? Did you make it compile? Thanx

graysky · 2015-06-06 16:31:40

As an aside, from the developer's page, looks like "the latest" is dated over 4.5 years ago... stale project?

FreddoNotAFrog · 2015-06-06 21:22:08

metak wrote:

Hey @FreddoNotAFrog!
Could you please post an update on your progress? Did you make it compile? Thanx

Hey @Metak,
I've been at uni and haven't really had time for all these little pet projects as yet, but last time I tried updating (pacman -Syu) I got about 30 error messages, so will have to debug first before I go any further... which will be after 1st Semester exams, so watch this space after June 25 or so (unless I happen to have some 'free time' )

Last I remember, I was compiling a bunch of 32-bit packages for 64-bit Arch from AUR and sorting out conflicts etc. Time consuming, but almost done (I think).

When I get to my Arch laptop and finish a couple of uni assignments (probably this afternoon) I'll try compiling and see what happens, shall let you know.

@Graysky,
Definitely stale- it refuses to compile on my x86_64 system, hence the 32 bit package compiling first. I don't have especially high hopes for it but we'll see what happens. If you guys are interested I can send a link with all the necessary packages in Dropbox or similar to work on? Not too sure how successful it'd be since I've forgotten exactly which packages are required, but still worth a try.

Cheers
Freddo

FreddoNotAFrog · 2015-06-07 05:45:34

Okay, I promised an update and here it is:

Basically I started again on the entire thing, which involves compiling Nucleo first, then Metisse.

Nucleo gives me error messages similar to ones in an earlier post about png set 1,2,4 to 8. The full error log is here - I've left out all the 'entering directory xyz' notes.

Making all in apps
make[1]: Entering directory '/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/apps'
Making all in videoServer
make[2]: Entering directory '/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/apps/videoServer'
/bin/sh ../../libtool --tag=CXX   --mode=link g++  -g -O2 -L../../nucleo -lNucleo -lpng -o videoServer main.o VideoServer.o VideoService.o Notifier.o FileStreamer.o VideoStreamer.o  -ljpeg -lGLU -lGL -lpthread   -lSM -lICE   -lXi -lpng16  -lexif  -ldl
libtool: link: g++ -g -O2 -o .libs/videoServer main.o VideoServer.o VideoService.o Notifier.o FileStreamer.o VideoStreamer.o  -L/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/nucleo /home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/nucleo/.libs/libNucleo.so -lexpat -ldns_sd -lfreetype -lgnutls -lpng -ljpeg -lGLU -lGL -lpthread -lSM -lICE -lXi -lpng16 -lexif -ldl -Wl,-rpath -Wl,/usr/local/lib
/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/nucleo/.libs/libNucleo.so: undefined reference to `png_set_gray_1_2_4_to_8'
collect2: error: ld returned 1 exit status
Makefile:341: recipe for target 'videoServer' failed
make[2]: *** [videoServer] Error 1
make[2]: Leaving directory '/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/apps/videoServer'
Makefile:409: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/apps'
Makefile:421: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Unfortunately, I can't seem to read *.so files - in both Nano and Mousepad everything appears as funny little question mark characters.

So, a new question: (no pun intended) How does one open and edit .so files? Even on my mac it looks like utter gibberish in TextEdit.

Cheers,
Freddo

mauritiusdadd · 2015-06-07 06:46:55

.so files are shared libraries and cannot be edited in a text editor because they are binary files. The message

/home/lyndon/Downloads/June07Metisse/nucleo-0.7.6/nucleo/.libs/libNucleo.so: undefined reference to `png_set_gray_1_2_4_to_8'

means that a function (png_set_gray_1_2_4_to_8 in this case) is required but it is missing from the library itself (libNucleo.so in this case) and thus should be provided by an external library. Usually the configure script takes care to find and add the needed libraries but if it doesn't happen you have to manually find which library contains the missing symbol and pass it to the compiler/linker. To show what symbols a library contains you can use readelf. In this case the symbol name suggests us to search into the library libpng.so. In particular that symbol is provided by the version 1.2 of libpng provided by the package libpng12

$ readelf -Ws /usr/lib/libpng12.so | grep png_set_gray
   135: 0000000000017730    18 FUNC    GLOBAL DEFAULT   12 png_set_gray_1_2_4_to_8@@PNG12_0
   226: 0000000000017770    20 FUNC    GLOBAL DEFAULT   12 png_set_gray_to_rgb@@PNG12_0

--edit: typo

Last edited by mauritiusdadd (2015-06-07 09:16:07)

graysky · 2015-06-07 09:09:45

graysky wrote:

As an aside, from the developer's page, looks like "the latest" is dated over 4.5 years ago... stale project?

metak wrote:

Definitely stale- it refuses to compile on my x86_64 system, hence the 32 bit package compiling first. I don't have especially high hopes for it but we'll see what happens.

It's a fool's errand.

Buddlespit · 2015-06-07 11:39:29

graysky wrote:

It's a fool's errand.

And that, boys and girls, is how you motivate and encourage the next generation of innovative programmers. Let them know that the pet side-project that they're trying to figure out isn't worth the time it takes for you to tell them that it isn't worth your time.

graysky · 2015-06-07 12:50:06

Buddlespit wrote:

And that, boys and girls, is how you motivate and encourage the next generation of innovative programmers. Let them know that the pet side-project that they're trying to figure out isn't worth the time it takes for you to tell them that it isn't worth your time.

No, but it is an honest assessment in this case.

FreddoNotAFrog · 2015-06-07 19:05:38

Perhaps it is a fool's errand, but I'd still like to give it a go - I don't see why it couldn't be updated. If it doesn't work then it doesn't work, but if it does, then great.

Anyway.

The Nucleo component finished compiling last night, once I referenced libpng12 instead of libpng16, and now I simply have to do the same with the actual Metisse programme.

More details this afternoon once I get home from uni.

Fred

metak · 2015-06-07 19:38:30

@Graysky,

Yeah, I know it's a dead project and their latest release was years ago... I was just curious. ;-)

FreddoNotAFrog wrote:

The Nucleo component finished compiling last night, once I referenced libpng12 instead of libpng16, and now I simply have to do the same with the actual Metisse programme.

Why did you referenced libpng12 in Nucleo? On my end it builds fine with the latest libpng16 with small patch.
What about the nucleo plugins? I disabled them with ./configure and nucleo builds.

Now the Metisse... ;-)

Last edited by metak (2015-06-07 19:39:28)

Rasi · 2015-06-07 22:27:09

if you only want to give it a try, why not use the mandrive metisse cd? http://iso.linuxquestions.org/mandriva/ … e/#live-cd

FreddoNotAFrog · 2015-06-08 02:43:40

metak wrote:

@Graysky,
Why did you referenced libpng12 in Nucleo? On my end it builds fine with the latest libpng16 with small patch.
What about the nucleo plugins? I disabled them with ./configure and nucleo builds.
Now the Metisse... ;-)

I referenced libpng12 because it provides the expand 1, 2, 4 to 8 ability which is needed.
The nucleo plugins I disabled too - according to http://lists.lri.fr/pipermail/metisse/2 … 00330.html they aren't necessary.

Which patch did you use?
Have you needed to go and add #include <unistd.h> at all, or is there a patch for that?

Cheers
Freddo

metak · 2015-06-08 04:08:54

FreddoNotAFrog wrote:

I referenced libpng12 because it provides the expand 1, 2, 4 to 8 ability which is needed.
The nucleo plugins I disabled too - according to http://lists.lri.fr/pipermail/metisse/2 … 00330.html they aren't necessary.
Which patch did you use?
Have you needed to go and add #include <unistd.h> at all, or is there a patch for that?
Cheers
Freddo

I was talking about these patches over at the FreeBSD ports tree. (files/ - folder for the patches)

http://svnweb.freebsd.org/ports/head/x1 … ts/nucleo/
http://svnweb.freebsd.org/ports/head/x11/metisse/

Anyway, good luck making it work for you! ;-)

FreddoNotAFrog · 2015-06-09 05:11:38

Rasi wrote:

if you only want to give it a try, why not use the mandrive metisse cd? http://iso.linuxquestions.org/mandriva/ … e/#live-cd

Error 404 - I'd guess they've been taken down.
Thanks for the idea though - I hadn't thought of looking for ISO's with Metisse precompiled.

Freddo

FreddoNotAFrog · 2015-06-09 21:07:12

metak wrote:

I was talking about these patches over at the FreeBSD ports tree. (files/ - folder for the patches)
http://svnweb.freebsd.org/ports/head/x1 … ts/nucleo/
http://svnweb.freebsd.org/ports/head/x11/metisse/
Anyway, good luck making it work for you! ;-)

Hey @Metak,
Call me a bit of a newbie here, but how do we download all the Nucleo/Metisse files from the site in one go? It seems a bit counterintuitive to be able to download only one file at a time...

Thanks,
Freddo

metak · 2015-06-10 00:05:54

FreddoNotAFrog wrote:

Hey @Metak,
Call me a bit of a newbie here, but how do we download all the Nucleo/Metisse files from the site in one go? It seems a bit counterintuitive to be able to download only one file at a time...
Thanks,
Freddo

Well, one way would be:

svn checkout --depth empty svn://svn.freebsd.org/ports/head/x11-toolkits
svn update --set-depth infinity x11-toolkits/nucleo

svn checkout --depth empty svn://svn.freebsd.org/ports/head/x11
svn update --set-depth infinity x11/metisse

FreddoNotAFrog · 2015-06-10 03:15:28

Woohoo! Success - Metisse works wonderfully - in a window!

Thanks so much to everyone for your help.

From here: How to make this work as a WM in XFCE...

EDIT:-- I spoke too soon. Segmentation faults are popping up. Oh well, it is old code, so it is probably to be expected.

Matisse without effects:
Metisse No Effects

Rotated z axis
Metisse Rotated 1

Rotated XY axes
Metisse Rotated 2

Freddo

Last edited by FreddoNotAFrog (2015-06-10 03:39:26)

Arch Linux

#1 2015-04-13 07:49:22

Compiling Metisse, a 3D desktop

#2 2015-04-13 12:04:50

Re: Compiling Metisse, a 3D desktop

#3 2015-04-13 23:33:09

Re: Compiling Metisse, a 3D desktop

#4 2015-04-14 04:25:14

Re: Compiling Metisse, a 3D desktop

#5 2015-04-18 06:09:12

Re: Compiling Metisse, a 3D desktop

#6 2015-06-06 12:48:15

Re: Compiling Metisse, a 3D desktop

#7 2015-06-06 16:31:40

Re: Compiling Metisse, a 3D desktop

#8 2015-06-06 21:22:08

Re: Compiling Metisse, a 3D desktop

#9 2015-06-07 05:45:34

Re: Compiling Metisse, a 3D desktop

#10 2015-06-07 06:46:55

Re: Compiling Metisse, a 3D desktop

#11 2015-06-07 09:09:45

Re: Compiling Metisse, a 3D desktop

#12 2015-06-07 11:39:29

Re: Compiling Metisse, a 3D desktop

#13 2015-06-07 12:50:06

Re: Compiling Metisse, a 3D desktop

#14 2015-06-07 19:05:38

Re: Compiling Metisse, a 3D desktop

#15 2015-06-07 19:38:30

Re: Compiling Metisse, a 3D desktop

#16 2015-06-07 22:27:09

Re: Compiling Metisse, a 3D desktop

#17 2015-06-08 02:43:40

Re: Compiling Metisse, a 3D desktop

#18 2015-06-08 04:08:54

Re: Compiling Metisse, a 3D desktop

#19 2015-06-09 05:11:38

Re: Compiling Metisse, a 3D desktop

#20 2015-06-09 21:07:12

Re: Compiling Metisse, a 3D desktop

#21 2015-06-10 00:05:54

Re: Compiling Metisse, a 3D desktop

#22 2015-06-10 03:15:28

Re: Compiling Metisse, a 3D desktop

Board footer