I updated the wiki with the build depends found out so far.

The latest version of CE GCC is the one I used, since it hasn't changed for a while. Revision 1449 that is.

For the x86 version CE GCC, first thing I wonder is if it will install anything over the ARM CE GCC toolchain or not. I'll run some tests.

Hi,

I am trying to build the OrbiterCE and see the following error message during the build of CEGCC.
Anybody a suggestion what is going wrong?

Regards Herman

.............
/home/herman/TouchOrbiter/WindowsCE/cegcc/mingw32ce/binutils/binutils/syslex.c:1: multiple definition of `main'
sysinfo.o:/home/herman/TouchOrbiter/WindowsCE/cegcc/mingw32ce/binutils/binutils/sysinfo.c:1: first defined here
collect2: ld returned 1 exit status
make[2]: *** [sysinfo] Error 1
make[2]: Leaving directory `/home/herman/TouchOrbiter/WindowsCE/cegcc/mingw32ce/binutils/binutils'
make[1]: *** [all-binutils] Error 2
make[1]: Leaving directory `/home/herman/TouchOrbiter/WindowsCE/cegcc/mingw32ce/binutils'
make: *** [all] Error 2
make[1]: *** [cegcc/mingw32ce/.compiled] Error 2
make[1]: Leaving directory `/home/herman/TouchOrbiter/WindowsCE'
make: *** [cegcc] Error 2

This error looks quite interesting. Just by looking at it, I think it shouldn't happen. What system are you trying to build on? I used Ubuntu 10.04 (since there's no need to use the same distro that is used by LinuxMCE at all), and I also used Ubuntu 7.10 right now.

A few problems that anyone could encounter are related to -dev packages. libgmp3-dev, libmpfr-dev, and possibly a few others, but these happen at the configure stage of different packages in cegcc.

Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.

SSHHHH, don't tell them. They will replace it with a waving Windows flag

Or an Apple... err... apple

OK, that rules in a Javascript issue with Internet Explorer. I don't have it, so I never tested it. The other screens seem to be botched regens.

SuperTux appears before an AJAX request is sent with a command and to load the resulting image, and then it disappears. Somewhere the AJAX request dies on Internet Explorer.

Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.

I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)

Actually, I didn't upload the beach ball cursor to LinuxMCE You still get SuperTux. I'll put it in LinuxMCE SVN now, but leave it disabled until a switch is made for selecting one or the other (some people like SuperTux ).

After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one.

The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached)

The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user).

Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help.

Personally I don't like this message: "Could not find text object: 670". Try a full regen (not a quick one).

The "device kills connection immediately" symptom is actually alright, since the web page connects, does its thing and disconnects. Once a second you should see a "ANYNEWS?" message in the logs, because the web page checks for updates every second, and if you don't, it means the Proxy_Orbiter lacks a change (but this change would only prevent automatic refreshes from working, the rest of the web orbiter should work just fine regardless).

To compile the Uplink's demo just download it, uncompress the archive somewhere using;

tar zxf clutter-orbiter-sample.tar.gz<return>

Now you need the clutter lib;

apt-get install libclutter-1.0-dev<return>

Im trying to learn clutter at present, ive been throught the tutorials and now I wanted to build the example, i have the example downloaded and can see the cpp code etc, however when i try to do the install libclutter-1.0-dev it says it cannot find the package?? am i doing someting wrong?

You're doing it right, except that the package libclutter-1.0-dev was first introduced in Ubuntu Karmic. You'll have to either run Ubuntu 9.10 or 10.04, or backport the package.

A warning: be prepared to scrap all the code we write at this stage, several times over, until we get a grip on it. That can look like duplication of work, but to me that's experience. When we get to a "Wow, we all like it" moment, we'll be ready to start the real work

Just my immediate prediction...

The entire Orbiter codebase will be dropped, and rewritten from scratch.

-Thom

Nice prediction. Quoting from the past

My sample is hardcoded because it's just a first attempt to making something. I didn't have time to play enough with clutter to come up with a silly UI definition to go with it, but I may just as well do in the following days and post the new sample, with the UI definition taken out so people can move things about. Maybe I'll add a few transitions as well (2-3 screens you can bounce around).

Check out Moovida. You may find some of this stuff in there, even if it's not written in C++.

I made something silly that you can get from here: http://dianemo.com/clutter-orbiter-sample.tar.gz. It should NOT be used as a base (I mean, just look at the sloppy coding style). Just build it and enjoy the simple effects when you click the buttons

If you find someone with a Denon amp that he can connect to a LMCE machine, I'll help update your current Denon template so it uses my bash code instead of the ruby code. Thing is, I don't want to break the Denon template blindly in 0810. If I break it, I'd like to do so with a working system.

remind me to look at show_vfsmnt+0x125/0x170, iirc i've seen that elsewhere already..

Is it alright if I remind you now? Or is this fixed in 0810?