Maemo 5 SDK on Fedora

[gbraad]

It is possible to install the Maemo 5 SDK (final) on Fedora 12. You first need to make sure you have installed Xephyr. You can do so with the command:

$ yum install Xephyr

since the installer is not able to do so for other distributions than Ubuntu and debian.

In the file maemo-sdk-install-wizard_5.0.py you can change line 129 to

SB_PATH="/opt/scratchbox"

change line 2311 to:

exec_cmd(sb_installer_fn + opt + "-s " + SB_PATH)

change line 2351 to:

cmd = "%s -d -m %s -s %s" % (sdk_installer_fn, self.__sdk_inst_m_opt_arg, SB_PATH)

this includes the Scratchbox path during the command invocation. You can then install the SDK by running the script. It will handle the download of PyQT and sip itself.

After the install you can start Xephyr. However you can not use the -kb option:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac &

The first start of af-sb-init.sh failed for me with a coredump and several segmentation faults. try to close the scratchbox environment and try again. The result: http://picasaweb.google.com/lh/photo/2wUSWdzrPVlzul5UjAaSqg

Greets!

Note: I haven't tried it with SELinux as enforcing since I currently run my workstation as permissive.

[deadmalc]

Wow!
I found your page off "fedora people" http://blog.gbraad.nl/2009/11/maemo-5-sdk-on-fedora-12.html

Now to get coding! A lot of learning and work to do.
Got to say I am massively impressed with maemo 5, I can't think of the last time something actually impressed me.
I really didn't think it would be this good.

[acedip]

nice article, I did exactly the way you have mentioned on my f12-kde machine. But after installation there were some errors though the Xephyr server started but the window was black with only mouse/keyboard grab/release with following errors


[root@localhost ~]# Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac &
[1] 3458
[root@localhost ~]# record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
Ignoring device from HAL.
(EE) config/hal: NewInputDeviceRequest failed (2)
^C^C
[root@localhost ~]# XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 41 requests (41 known processed) with 0 events remaining.

[mooninite]

The SDK is not SELinux friendly. The QEMU that Nokia is using requires some privileged access. Nokia should have fixed this issue before releasing the final SDK.

I also cannot get it to work on a 64-bit machine. All the packages are installed, but starting up the GUI results in nothing in my Xephyr window. Yes, I started it on :2 and exported DISPLAY=:2. I have this working within the Nokia packaged VM under VirtualBox, but I'd rather not have it there.

[ewan]

I have to say I saved myself the hassle and just used the VM approach - Fedora has excellent in-built support for running virtual machines and it doesn't take long to set up a basic Ubuntu install in one. Aside from giving the SDK the sort of environment it expects to see it also protects your real system from any potential SDK weirdness - it does need to run some components as root, and a VM keeps it nicely contained.

[jebba]

I'm trying to install on Fedora 12 x86_64, but it aborts thusly:


which: no dpkg in (/usr/bin:/bin)
dpkg tool in path... no
E: This script requires dpkg to install .deb files.
V [17:19:35 04.12.2009]: Installer execution failed
V [17:19:35 04.12.2009]: ----- Begin logging exception -----
Traceback (most recent call last):
File "./maemo-sdk-install-wizard_5.0.py", line 2705, in run
task()
File "./maemo-sdk-install-wizard_5.0.py", line 2318, in __taskInstallScratchbox
raise Exception("Installer execution failed")
Exception: Installer execution failed
V [17:19:35 04.12.2009]: ----- End logging exception -----
V [17:19:35 04.12.2009]: Executor set exit status to (status_error)

[jebba]

I just need to RTFS. :)

--- maemo-sdk-install-wizard_5.0.py.orig 2009-11-16 08:16:39.000000000 -0300
+++ maemo-sdk-install-wizard_5.0.py 2009-12-04 17:29:00.905719892 -0300
@@ -2308,7 +2308,7 @@
tries = 2
while (True):
try:
- exec_cmd(sb_installer_fn + opt)
+ exec_cmd(sb_installer_fn + opt + "-s " + SB_PATH)
except:
tries -= 1
if tries:
@@ -2348,7 +2348,7 @@


# do the installation thing
- cmd = "%s -d -m %s" % (sdk_installer_fn, self.__sdk_inst_m_opt_arg)
+ cmd = "%s -d -m %s -s %s" % (sdk_installer_fn, self.__sdk_inst_m_opt_arg, SB_PATH)

if self.__targets_exist:
if self.__remove_targets:

Btw, I have some notes which may be of use to you as the page develops:

http://wiki.maemo.org/User:Jebba

Thanks,

-Jeff

[jebba]

I got this up and running A-OK in Fedora 12 x86_64 (64 bit), FYI.

[jebba]

@acedip:

That's actually OK. Note, you don't have to run Xephyr as root. In fact you probably shouldn't.

Then run these commands (in another terminal, perhaps):

newgrp sbox
/scratchbox/login

Then at the scratchbox prompt, run:
af-sb-init.sh

That will start up the emulator.

Good luck,

-Jeff

[mooninite]

I got this up and running A-OK in Fedora 12 x86_64 (64 bit), FYI.

Jebba, you don't have to modify the kernel command line. Just add a line to /etc/sysctl.conf

abi.vsyscall32=0

That way you don't have to reboot. ;)
(sysctl -p)

P.S. I have F12 x86_64 working as well. Sweetness...

P.P.S. You still can't run the ARM emulator. X86 only. Ugh.

[turnik]

Hello guys. I'm also have success running maemo5 SDK on Fedora 12 x64, but... Does anybody of you tried to use esbox (eclipse) IDE. As for me I have downloaded achive of esbox IDE from home esbox site and met some problem: Target list is empty for me, from esbox/workspace/.metadata/.log I got those errors:

!SESSION 2009-11-22 16:06:03.185 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86

!ENTRY org.maemo.esbox.scratchbox.sb1 4 0 2009-11-22 16:06:30.685
!MESSAGE Could not refresh targets
!STACK 0
org.maemo.esbox.scratchbox.core.scratchbox.Scratch boxException: Process failed with exit code 1
Traceback (most recent call last):
File "/scratchbox/tools/bin/sb-conf", line 10, in ?
os.execv(chroot,[chroot,p.basename(sys.argv[0])]+sys.argv[1:])
OSError: [Errno 13] Permission denied

Maybe somebody of You had the same problems and can help.

BR, Nick.

[kopele]

I had the same problem and just figured out what I did wrong. After installing the SDK you have logout and log back in to be properly added to the 'sbox' group, apparently I did not do that. See if this helps.

However, now when I start a new project esbox locks up after selecting a template and clicking next. Is there a guide for this somewhere?

[gbraad]

I just need to RTFS. :)
-Jeff

I was maybe off by one line with last statement... can't imagine I did it wrong;). Did you try to push it upstream?

Gerard

[mdengler]

In F12 x86_64, I had to up the mmap_min_addr as suggested http://lists.scratchbox.org/pipermai...st/001530.html :

echo "vm.mmap_min_addr = 1048576" >> /etc/sysctl.conf

Otherwise dbus / hal / other .debs wouldn't install in the scratchbox chroot.

I wrote up all the steps at http://www.martindengler.com/index.html#2010-02-03 because I found that three guides (at least to get this up & running was one or two too many :).

[mdengler]

In F12 x86_64, I had to up the mmap_min_addr as suggested http://lists.scratchbox.org/pipermai...st/001530.html :

echo "vm.mmap_min_addr = 1048576" >> /etc/sysctl.conf

Otherwise dbus / hal / other .debs wouldn't install in the scratchbox chroot.

I wrote up all the steps at http://www.martindengler.com/index.html#2010-02-03 because I found that three guides (at least to get this up & running was one or two too many :).