“You will find the Cosmoe 0.5.1 tarball on the download area of www.cosmoe.com. Please read the README before building to avoid problems. This version should compile cleanly under any gcc 2.96 through 3.1. I did
not test under 2.95.x” Bill Hayden announced the release to the Cosmoe mailing list. This version should also build cleanly on PPC.
Cosmoe 0.5.1 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
His code bounty system deal is a hoot!
Overall, the gui looks pretty nice. I can’t wait to get home to try it….
Are there any screenshots anywhere?
http://www.cosmoe.com/screenshot.png
Complains about missing exceptions.h
Can anyone help? What library provides this file?
Thanks!
Edit the source that complains and change the #include path to cosmoe/exception.h
Do the same for the other headers that it will complain too.
how do we know that the screen shot is of cosmoe not atheos?
Read the terminal in the screenshot.
Its kind of interesting how the source doesn’t actually build. First, headers in the include directory don’t give full paths (exceptions.h instead of cosmoe/exceptions.h) and some stuff is not in the right case (Box.h includes layoutview.h instead of LayoutView.h) Does he do his development on a wintel machine or something? If not, I’d really like to know how he compiled this source as is…
Correct! Edit those include paths, however, once I’ve done this, gcc can’t find layoutview.h, and to make matters worse, it’s no where on my system, including the cosmoe 5.1 tarball.
Does anyone else seem to have this strange mystery file known as layoutview.h?
Just edit the files that complain and change the word layoutview.h with
this: LayoutView.h
Weird. LayoutView.h is in the same dir as Box.h but the compiler still can’t find it.
Eugenia, you said:
“Edit the source that complains and change the #include path to cosmoe/exception.h Do the same for the other headers that it will complain too.”
Actually, it would make more sense to edit the makefile for global include paths. That way, you don’t need to modify the source files, which are fine the way they are.
I think it can’t find LayoutView.h because it’s in brackets. Try “LayoutView.h” instead of <LayoutView.h>.
Damn… Now I thought I was smart and would make sure the HTML brackets won’t destroy my comment.
Next try: “I think it can’t find LayoutView.h because it’s in brackets. Try “LayoutView.h” instead of <LayoutView.h>”
<interface/LayoutView.h> should also work and is probably more elegant (I don’t know, I’m a C newb).
A fix for these problems didn’t make it in time for the 0.5.1 release.
It is available from:
http://users.bigpond.net.au/pcky/cosmoe/cosmoe.diff
Apply it to your cosmoe directory like so:
patch -p1 -d cosmoe < cosmoe.diff
Other problems I encountered:
<circularbuffer.h> has to be <translation/CircularBuffer.h>
Next is an internal compiler error…
app/looper.cpp: In method `status_t os::CLooper::SafeLock()’:
app/looper.cpp:471: Internal compiler error.
app/looper.cpp:471: Please submit a full bug report.
app/looper.cpp:471: Internal compiler error:
app/looper.cpp:471: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
cpp0: output pipe has been closed
make[1]: *** [objs/looper.o] Error 1
Probably because he is using the 2.96 gcc…? I’m using 2.95 with Debian. *sigh*
Was anyone successful in building it on PPC? I’d like to know that before I erase a partition on my ibook…
how do we know that the screen shot is of cosmoe not atheos?
Parent Menus don’t have the > arrow on them under AtheOS, so its not AtheOS. Also see the uname -a output; its running on a Linux kernel (Mandrake 8.x SMP kernel, in fact).
Ok, got it working. Really nice to have AtheOS run on Linux. =) It works with USB mouse btw with a symlink from /dev/psaux to /dev/input/mice (had to do that because my ps2 mouse support is broken currently).
The speed is terrible slow… Probably VESA although I thought I would run the rivafb. Either it isn’t working with my Geforce 4 or the rivafb driver is extremely bad…
Yes. My Mdk 8.2 machine doesn’t seem to have no ‘make’ command. Or is it something the sourcecode has?
I’m sorry for my previous stupid post about me not having ‘make’… A closer look revealed that I didn’t have gcc installed. Sorry about that.
After I type ‘make install-headers’ it starts copying stuff and then I get this message:
make[1]: Leaving directory `/root/tmp/cosmoe/include’
make[1]: Entering directory `/root/tmp/cosmoe/libcosmoe’
Makefile:29: /usr/src/cosmoe/makefile.rules: Filen eller katalogen finns inte
make[1]: *** No rule to make target `/usr/src/cosmoe/makefile.rules’.
make[1]: Failed to remake makefile `/usr/src/cosmoe/makefile.rules’.
make[1]: Nothing to be done for `install-headers’.
make[1]: Leaving directory `/root/tmp/cosmoe/libcosmoe’
It then tries to enter the other directories but always displayes the same message as above.
(Filen eller katalogen finns inte >> File or directory doesn’t exist)
LayoutView.h, correct, this has led me to fix what appears to be all the include issues (though I believe I need to do some more massaging before I post anything up).
Just didn’t think to use locate -i earlier
.
LayoutView.h is in /blah/cosmoe/include/interface
So you must change from:
#include <layoutview.h>
to:
#include <interface/LayoutView.h>
There are MANY include errors, and it appears several people, including myself have already gone about fixin this stuff so you probably shouldn’t bother doing it yourself at this point, just wait for the next release.
Nah, don’t wait just install one of the several patches that are already available.
And there is also a problem that it wants to compile against a libcosmoe that isn’t installed yet, simple doing a make install first in the libcosmoe dir should make it possible.
This version should compile cleanly under any gcc 2.96 through 3.1. I did not test under 2.95.x
Ok, I tryed with 2.95 and doesn’t work… debian woody don’t like 2.96!
Ferco, same here. But look at the offending sourcecode (that makes the compiler crash), it’s a function like SafeLoop or something like that. It calls a Lock() and an Unlock() function IIRC. Just comment those out and it will work. Of course this will most probably break something, but it actually works somehow so you can at least try it out.
Wouldn’t it make more sense to change the include file PATH so that it contains the various Cosmoe include directories? I’m sure that is the setup that Bill has, which is why the includes don’t have the full path.
On BeOS there are many header directories but you don’t have to specify #include <be/interface/Window.h> for example but just #include <Window.h> because be/interface has been added to the header path.
“Wouldn’t it make more sense to change the include file PATH so that it contains the various Cosmoe include directories? I’m sure that is the setup that Bill has, which is why the includes don’t have the full path.”
I’m not sure because most other header files are also in subdirectories and included with something like <subdir/header.h>. So it just seemed right to also add the subdir for the other header files.