Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Porting KDE Plasma Active (WIP)
Date: Thu, 5 Apr 2012 12:50:24 +0800	[thread overview]
Message-ID: <4F7D2490.5060102@windriver.com> (raw)
In-Reply-To: <1967286.NbkyaBu6kN@helios>



On 04/01/2012 08:00 PM, Paul Eggleton wrote:
> On Sunday 01 April 2012 10:31:48 Robert Yang wrote:
>> On 04/01/2012 08:47 AM, Paul Eggleton wrote:
>>> usr/bin/icemaker: No such file or directory
>>
>> This is a known issue, there is an work around, it seems that the MACHINE is
>> qemux86, and host is x86_64, we can:
>>
>> cp
>> tmp/work/i586-poky-linux/kdelibs4-4.8.0+git1+1439483a67135f483632f4c4cd239e9
>> 6d2ed61fc-r0/git/build/bin/icemaker
>> tmp/sysroots/x86_64-linux/usr/bin/icemaker
>>
>> The problem is that we don't have a kdelibs4-native, and it seems it is not
>> easy to add it.
>
> Ah, I see I neglected to install kdelibs-devel; but on the version of Fedora I
> am building on when I do install it that executable is not provided (at
> version 4.6.5 perhaps it is too old). I've copied it as you suggested but then
> I run into the lack of kconfig_compiler. On this machine "yum whatprovides"
> tells me that the only package that provides kconfig_compiler is kdelibs3-devel
> which is clearly not what is needed.
>

For the kconfig_compiler issue, I used a hacked workaround:

1) cd /usr/bin
2) ln -s kconfig_compiler4 kconfig_compiler
3) ln -s kconfig_compiler4 makekdewidgets

Fortunately, kdelibs4-native has been successfully ported currently, we will
submit the patch sooner, so these problems would be fixed with kdelibs4-native.

Other problems you may meet are:

1) Sometimes the raptor and rasqal_git.bb may fail, just rebuild them
    would fix the error, seems strange errors.

2) After then build successed, we can start the kde:
    $ runqemu qemux86
    edit /usr/bin/startkde there is a host absolute path in it:
    LD_BIND_NOW=true 
/host/path/to/tmp/sysroots/qemux86/usr/lib/kde4/libexec/start_kdeinit_wrapper 
kcminit_startup

    Fix it to:

    LD_BIND_NOW=true /usr/lib/kde4/libexec/start_kdeinit_wrapper +kcminit_startup

    Then

    $ startkde

// Robert

> I can't help feeling we need to have kdelibs4-native and forget the
> consequences of having to extend qt4-native if that's what's required;
> otherwise it's just too hard for people to build.
>
> Cheers,
> Paul
>



  reply	other threads:[~2012-04-05  4:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 11:50 RFC: Porting KDE Plasma Active (WIP) Samuel Stirtzel
2012-02-02 11:56 ` Martin Jansa
2012-02-02 12:18   ` Samuel Stirtzel
2012-02-02 12:24     ` Martin Jansa
2012-02-02 20:35 ` Khem Raj
2012-02-08 10:09 ` Paul Eggleton
2012-02-08 10:59   ` Koen Kooi
2012-03-01 13:24 ` Samuel Stirtzel
2012-03-01 13:35   ` Koen Kooi
2012-03-01 14:15     ` Samuel Stirtzel
2012-03-01 14:37       ` Paul Eggleton
2012-03-26 12:48         ` Samuel Stirtzel
2012-04-01  0:47 ` Paul Eggleton
2012-04-01  2:31   ` Robert Yang
2012-04-01 12:00     ` Paul Eggleton
2012-04-05  4:50       ` Robert Yang [this message]
2012-04-05  9:23         ` Samuel Stirtzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F7D2490.5060102@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox