How to add current 1.2 handset target to SDK?

[Cornelius Hald]

Hi,

I've got a recent pre-release of the MeeGo SDK 1.2 for tablets working.
Currently the only target installed is:

meego-tablet-ia32-1.1.99.5.20110503.6

How do I install a recent handset target? I've tried following [1] and
[2] but meego-sdk-update-target always constructs invalid paths and thus
fails to download the needed files.

What is the recommended way to add a target to the SDK? Which target
would be appropriate to compile for N900 DE? Anything else to be aware
of?

Thanks!
Conny

[1] http://wiki.meego.com/SDK/Tutorials/Add_a_new_target
[2] http://wiki.meego.com/SDK/Docs/1.2-preview-under-progress

[Edmondas Girkantas]

Post by Cornelius Hald
What is the recommended way to add a target to the SDK? Which target
would be appropriate to compile for N900 DE? Anything else to be aware
of?

Read this (how to add N900DE target):
http://lists.meego.com/pipermail/meego-dev/2011-May/483027.html

--Edmondas

[Cornelius Hald]

Post by Edmondas Girkantas

Post by Cornelius Hald
What is the recommended way to add a target to the SDK? Which target
would be appropriate to compile for N900 DE? Anything else to be aware
of?

http://lists.meego.com/pipermail/meego-dev/2011-May/483027.html

Steps 1 to 3 are ok, but on Step 4 I get the following problem:

***@e6400:~# mad-admin create -f meego-handset-armv7hl-trunk
No predefined target/runtime 'meego-handset-armv7hl-trunk' found.

Any ideas?

Also what would be the best 1.2 target/runtime to compile and test my
app on a handset emulator?

Sorry for all the questions, but having so much choice is rather
confusing...

Thanks!
Conny

[Apollo Xue]

I met the same error when I tried to install a new target/runtime images (
http://repo.meego.com/MeeGo/builds/1.1.99/1.1.99.0.20110329.5/images/).
Does anyone know how to solve this problem?

Post by Cornelius Hald

Post by Edmondas Girkantas

Post by Cornelius Hald
What is the recommended way to add a target to the SDK? Which target
would be appropriate to compile for N900 DE? Anything else to be aware
of?

http://lists.meego.com/pipermail/meego-dev/2011-May/483027.html

No predefined target/runtime 'meego-handset-armv7hl-trunk' found.
Any ideas?
Also what would be the best 1.2 target/runtime to compile and test my
app on a handset emulator?
Sorry for all the questions, but having so much choice is rather
confusing...
Thanks!
Conny
_______________________________________________
MeeGo-sdk mailing list
http://lists.meego.com/listinfo/meego-sdk
http://wiki.meego.com/Mailing_list_guidelines
http://meego.com/developers

[Edmondas Girkantas]

Post by Apollo Xue
I met the same error when I tried to install a new target/runtime
images
(http://repo.meego.com/MeeGo/builds/1.1.99/1.1.99.0.20110329.5/images/).
Does anyone know how to solve this problem?

Uno momento! I will recheck provided instructions for N900 Developer
edition on my computer.

--Edmondas

[Edmondas Girkantas]

Post by Cornelius Hald
No predefined target/runtime 'meego-handset-armv7hl-trunk' found.
Any ideas?

wget
https://meego.gitorious.org/meego-developer-tools/madde-configurations/blobs/raw/master/madde.conf.d/meego-handset-armv7hl-trunk.conf
and put it to madde's configuration directory (on my Ubuntu 10.10 path
is /usr/lib/madde/linux-i686/cache/madde.conf.d)

Post by Cornelius Hald
Also what would be the best 1.2 target/runtime to compile and test my
app on a handset emulator?

Currently there is no working QEMU image for armv7hl target, because of
this bug:
https://bugs.meego.com/show_bug.cgi?id=16969

So there is only one option - use real N900 device as a target.
Probably you can survive with meego-handset-ia32-trunk target.


--Edmondas

[Cornelius Hald]

Post by Edmondas Girkantas

Post by Cornelius Hald
No predefined target/runtime 'meego-handset-armv7hl-trunk' found.
Any ideas?

wget
https://meego.gitorious.org/meego-developer-tools/madde-configurations/blobs/raw/master/madde.conf.d/meego-handset-armv7hl-trunk.conf
and put it to madde's configuration directory (on my Ubuntu 10.10 path
is /usr/lib/madde/linux-i686/cache/madde.conf.d)

Thanks for the fast answer. But what you suggest is actually step 3 on
the list. So I did that already and the file is there. I'm also on
Ubuntu 10.10.

Do I have to register that file somehow with madde? Something to make it
re-read that cache dir?

Post by Edmondas Girkantas

Post by Cornelius Hald
Also what would be the best 1.2 target/runtime to compile and test my
app on a handset emulator?

Currently there is no working QEMU image for armv7hl target, because of
https://bugs.meego.com/show_bug.cgi?id=16969
So there is only one option - use real N900 device as a target.
Probably you can survive with meego-handset-ia32-trunk target.

Good, so meego-handset-ia32-trunk sounds like something to start testing
with. After that I can move to meego-handset-armv7hl-trunk and test on
N900 DE.

Cheers,
Conny

[Edmondas Girkantas]

Post by Cornelius Hald
Thanks for the fast answer. But what you suggest is actually step 3 on
the list. So I did that already and the file is there. I'm also on
Ubuntu 10.10.
Do I have to register that file somehow with madde? Something to make it
re-read that cache dir?

Sorry that's my fault, I'm rechecking now if these instructions still work.

--Edmondas

[Edmondas Girkantas]

Post by Cornelius Hald
Do I have to register that file somehow with madde? Something to make it
re-read that cache dir?

no additional registration required, just put this file
(meego-handset-armv7hl-trunk.conf) to
/usr/lib/madde/linux-i686/cache/madde.conf.d

double check if it's really here:
ls -al
/usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.conf

then try to create target
mad-admin create -e -f meego-handset-armv7hl-trunk

Checked N900DE instructions against fresh Ubuntu 10.10 installation and
it works for me.

--Edmondas

[Cornelius Hald]

Post by Edmondas Girkantas

Post by Cornelius Hald
Do I have to register that file somehow with madde? Something to make it
re-read that cache dir?

no additional registration required, just put this file
(meego-handset-armv7hl-trunk.conf) to
/usr/lib/madde/linux-i686/cache/madde.conf.d
ls -al
/usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.conf
then try to create target
mad-admin create -e -f meego-handset-armv7hl-trunk
Checked N900DE instructions against fresh Ubuntu 10.10 installation and
it works for me.

Thanks for testing again. I'm quite sure the file is there :) If you
have other ideas, please let me know. Otherwise I could of course try to
reinstall the SDK from scratch.

Here is what I have:

***@e6400:~# ls
-lh /usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.conf-rw-r--r-- 1 root root 10K 2011-05-06 20:25 /usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.conf

***@e6400:~# mad-admin create -e -f meego-handset-armv7hl-trunk
No predefined target/runtime 'meego-handset-armv7hl-trunk' found.

***@e6400:~# mad-admin list

Targets:
meego-core-armv7l-1.1 (installable)
meego-core-armv7l-1.1.2 (installable)
meego-core-armv7l-trunk (installable)
meego-core-ia32-1.1 (installable)
meego-core-ia32-1.1.2 (installable)
meego-core-ia32-trunk (installable)
meego-handset-ia32-1.1.2 (installable)
meego-handset-ia32-1.1.2-4.7.1 (installable)
meego-handset-ia32-1.1 (installable)
meego-handset-ia32-w32-1.1 (installable)
meego-handset-ia32-trunk (installed)
meego-netbook-ia32-1.1.2 (installable)
meego-netbook-ia32-1.1.2-4.7.1 (installable)
meego-netbook-ia32-1.1 (installable)
meego-netbook-ia32-w32-1.1 (installable)
meego-netbook-ia32-trunk (installable)
meego-tablet-ia32-1.1.99.5.20110503.6 (installed)

Runtimes:
meego-handset-ia32-qemu-1.1.20110110.1026-runtime (installable)
meego-handset-ia32-qemu-1.1.20110118.1010-runtime (installable)
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime (installable)
meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime (installable)
meego-handset-ia32-qemu-1.1.99.0.20110329.5-runtime (installable)
meego-netbook-ia32-qemu-1.1.20110110.1049-runtime (installable)
meego-netbook-ia32-qemu-1.1.20110118.1020-runtime (installable)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime (installable)
meego-netbook-ia32-w32-qemu-1.1.20101031.2037-sda-runtime (installable)
meego-netbook-ia32-qemu-1.1.99.0.20110329.5-runtime (installable)
meego-tablet-ia32-qemu-1.1.99.5.20110503.6-runtime (installed)

***@e6400:~#
ls /usr/lib/madde/linux-i686/cache/madde.conf.dmeego-common.conf
meego-core-armv7l-1.1.2.conf
meego-core-armv7l-1.1.conf
meego-core-armv7l-trunk.conf
meego-core-ia32-1.1.2.conf
meego-core-ia32-1.1.conf
meego-core-ia32-trunk.conf
meego-handset-armv7hl-trunk.conf
meego-handset-ia32-1.1.2.conf
meego-handset-ia32-1.1.conf
meego-handset-ia32-trunk.conf
meego-netbook-ia32-1.1.2.conf
meego-netbook-ia32-1.1.conf
meego-netbook-ia32-trunk.conf
meego-tablet-ia32-1.1.99.5.20110503.6.conf

Cheers,
Conny

[Jussi Saavalainen]

Post by Cornelius Hald

Post by Edmondas Girkantas

Post by Cornelius Hald
Do I have to register that file somehow with madde? Something to make
it re-read that cache dir?

no additional registration required, just put this file
(meego-handset-armv7hl-trunk.conf) to
/usr/lib/madde/linux-i686/cache/madde.conf.d
ls -al
/usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.
conf
then try to create target
mad-admin create -e -f meego-handset-armv7hl-trunk
Checked N900DE instructions against fresh Ubuntu 10.10 installation and
it works for me.

Thanks for testing again. I'm quite sure the file is there :) If you
have other ideas, please let me know. Otherwise I could of course try to
reinstall the SDK from scratch.
-lh
/usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.c
onf-rw-r--r-- 1 root root 10K 2011-05-06 20:25
/usr/lib/madde/linux-i686/cache/madde.conf.d/meego-handset-armv7hl-trunk.c
onf
No predefined target/runtime 'meego-handset-armv7hl-trunk' found.
meego-core-armv7l-1.1 (installable)
meego-core-armv7l-1.1.2 (installable)
meego-core-armv7l-trunk (installable)
meego-core-ia32-1.1 (installable)
meego-core-ia32-1.1.2 (installable)
meego-core-ia32-trunk (installable)
meego-handset-ia32-1.1.2 (installable)
meego-handset-ia32-1.1.2-4.7.1 (installable)
meego-handset-ia32-1.1 (installable)
meego-handset-ia32-w32-1.1 (installable)
meego-handset-ia32-trunk (installed)
meego-netbook-ia32-1.1.2 (installable)
meego-netbook-ia32-1.1.2-4.7.1 (installable)
meego-netbook-ia32-1.1 (installable)
meego-netbook-ia32-w32-1.1 (installable)
meego-netbook-ia32-trunk (installable)
meego-tablet-ia32-1.1.99.5.20110503.6 (installed)
meego-handset-ia32-qemu-1.1.20110110.1026-runtime (installable)
meego-handset-ia32-qemu-1.1.20110118.1010-runtime (installable)
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime (installable)
meego-handset-ia32-w32-qemu-1.1.20101031.2201-sda-runtime (installable)
meego-handset-ia32-qemu-1.1.99.0.20110329.5-runtime (installable)
meego-netbook-ia32-qemu-1.1.20110110.1049-runtime (installable)
meego-netbook-ia32-qemu-1.1.20110118.1020-runtime (installable)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime (installable)
meego-netbook-ia32-w32-qemu-1.1.20101031.2037-sda-runtime (installable)
meego-netbook-ia32-qemu-1.1.99.0.20110329.5-runtime (installable)
meego-tablet-ia32-qemu-1.1.99.5.20110503.6-runtime (installed)
ls /usr/lib/madde/linux-i686/cache/madde.conf.dmeego-common.conf
meego-core-armv7l-1.1.2.conf
meego-core-armv7l-1.1.conf
meego-core-armv7l-trunk.conf
meego-core-ia32-1.1.2.conf
meego-core-ia32-1.1.conf
meego-core-ia32-trunk.conf
meego-handset-armv7hl-trunk.conf
meego-handset-ia32-1.1.2.conf
meego-handset-ia32-1.1.conf
meego-handset-ia32-trunk.conf
meego-netbook-ia32-1.1.2.conf
meego-netbook-ia32-1.1.conf
meego-netbook-ia32-trunk.conf
meego-tablet-ia32-1.1.99.5.20110503.6.conf
Cheers,
Conny
_______________________________________________
MeeGo-sdk mailing list
http://lists.meego.com/listinfo/meego-sdk
http://wiki.meego.com/Mailing_list_guidelines
http://meego.com/developers

Hi,
I ran into a similar problem just now. In my case the solution was clear after
looking at the .conf file's contents - the url isn't the file, but rather the
gitorious ui page. The real file should start with

"

require meego-common


toolchain meego-1.2-sdk-armv7hl-toolchain-1.2
"

etc.

[Cornelius Hald]

Post by Jussi Saavalainen
Hi,
I ran into a similar problem just now. In my case the solution was clear after
looking at the .conf file's contents - the url isn't the file, but rather the
gitorious ui page. The real file should start with
"
require meego-common
toolchain meego-1.2-sdk-armv7hl-toolchain-1.2
"
etc.

Arg, yes I should have noticed... That's the problem. Thank you very
much. It looks like using wget on that link does not work as expected.
I've now downloaded that file through the browser and everything looks
fine.

Thanks everyone!
Conny

[Edmondas Girkantas]

Post by Cornelius Hald
Thanks for testing again. I'm quite sure the file is there :) If you
have other ideas, please let me know. Otherwise I could of course try to
reinstall the SDK from scratch.

try to reinstall MeeGo SDK and use this repository
http://download.meego.com/live/Tools:/SDK:/Host/

For Ubuntu 10.10 it means:
/etc/apt/sources.list.d/meego-sdk.list has line
deb http://download.meego.com/live/Tools:/SDK:/Host/Ubuntu_10.10/ /

then

1. sudo apt-get install meego-sdk
2. put armv7hl config to madde conf. directory
3. install armv7hl toolchain (apt-get install
meego-1.2-sdk-armv7hl-toolchain)
4. create armv7hl target

--Edmondas

[Cornelius Hald]

Post by Edmondas Girkantas
So there is only one option - use real N900 device as a target.
Probably you can survive with meego-handset-ia32-trunk target.

SDK and toolchain are now installed fine. Thanks again. My (hopefully)
last question for today: How do I get a working handset runtime? It
doesn't need to be ARM, IA32 is fine.

I'm doing the following:

***@e6400:~# mad-admin create -f -e
meego-handset-ia32-qemu-1.1.99.0.20110329.5-runtime

But again the paths don't seem to match. The error is:

--2011-05-13 13:02:37--
http://mirrors.kernel.org/meego/builds/trunk/1.1.99.0.20110329.5/images/meego-handset-ia32-qemu/meego-handset-ia32-qemu-1.1.99.0.20110329.5-raw.tar.bz2
Resolving mirrors.kernel.org... 130.239.17.7, 199.6.1.167
Connecting to mirrors.kernel.org|130.239.17.7|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-05-13 13:02:38 ERROR 404: Not Found.

Download failed!

Do I need another file from gitorious? Or am I trying to install the
wrong runtime?

All hints would be highly appreciated :)
Conny

[Edmondas Girkantas]

Post by Cornelius Hald
meego-handset-ia32-qemu-1.1.99.0.20110329.5-runtime
--2011-05-13 13:02:37--
http://mirrors.kernel.org/meego/builds/trunk/1.1.99.0.20110329.5/images/meego-handset-ia32-qemu/meego-handset-ia32-qemu-1.1.99.0.20110329.5-raw.tar.bz2
Resolving mirrors.kernel.org... 130.239.17.7, 199.6.1.167
Connecting to mirrors.kernel.org|130.239.17.7|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-05-13 13:02:38 ERROR 404: Not Found.
Download failed!
Do I need another file from gitorious? Or am I trying to install the
wrong runtime?
All hints would be highly appreciated :)
Conny

madde configuration for meego-handset-ia32 is not up to date, because
this is trunk and versioning changes from time to time,
therefore you need update file manually or you can use my updated from
this gitorious repository:

wget
https://meego.gitorious.org/~edmondas/meego-developer-tools/edmondass-madde-configurations/blobs/raw/master/madde.conf.d/meego-handset-ia32-trunk.conf
mv meego-handset-ia32-trunk.conf
/usr/lib/madde/linux-i686/cache/madde.conf.d/


--Edmondas

[Cornelius Hald]

Post by Edmondas Girkantas
madde configuration for meego-handset-ia32 is not up to date, because
this is trunk and versioning changes from time to time,
therefore you need update file manually or you can use my updated from
wget
https://meego.gitorious.org/~edmondas/meego-developer-tools/edmondass-madde-configurations/blobs/raw/master/madde.conf.d/meego-handset-ia32-trunk.conf
mv meego-handset-ia32-trunk.conf
/usr/lib/madde/linux-i686/cache/madde.conf.d/

Thank you Edmondas! It's now booting up. Dog slow* and only into naked X, but that's something for another thread :)

Cheers,
Conny

[*] Yes, with hardware VT

[Cornelius Hald]

Post by Cornelius Hald

Post by Edmondas Girkantas
madde configuration for meego-handset-ia32 is not up to date, because
this is trunk and versioning changes from time to time,
therefore you need update file manually or you can use my updated from
wget
https://meego.gitorious.org/~edmondas/meego-developer-tools/edmondass-madde-configurations/blobs/raw/master/madde.conf.d/meego-handset-ia32-trunk.conf
mv meego-handset-ia32-trunk.conf
/usr/lib/madde/linux-i686/cache/madde.conf.d/

Thank you Edmondas! It's now booting up. Dog slow* and only into naked X, but that's something for another thread :)

Scratch that last bit. After rebooting my host the handset image works
well.

Cheers,
Conny

[Ville M. Vainio]

Post by Cornelius Hald
I've got a recent pre-release of the MeeGo SDK 1.2 for tablets working.
meego-tablet-ia32-1.1.99.5.20110503.6
How do I install a recent handset target? I've tried following [1] and
[2] but meego-sdk-update-target always constructs invalid paths and thus
fails to download the needed files.

I know this is not what you are asking about, but have you considered
building at OBS instead?

[Cornelius Hald]

Post by Ville M. Vainio

Post by Cornelius Hald
I've got a recent pre-release of the MeeGo SDK 1.2 for tablets working.
meego-tablet-ia32-1.1.99.5.20110503.6
How do I install a recent handset target? I've tried following [1] and
[2] but meego-sdk-update-target always constructs invalid paths and thus
fails to download the needed files.

I know this is not what you are asking about, but have you considered
building at OBS instead?

I've heard a lot about OBS, but I'm under the impression that it's a bit
overkill. I'm on a commercial project currently, so I think using the
community OBS would not be possible. That would only leave me with
setting up my own OBS. Or do I misunderstand the situation?

Cheers,
Conny