All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Daniel Toussaint <daniel@dmhome.net>
Cc: yocto@yoctoproject.org
Subject: Re: Building a Qt4-x11 app.
Date: Sun, 29 Apr 2012 21:19:59 +0200	[thread overview]
Message-ID: <20120429211959.3f12671b@eb-e6520> (raw)
In-Reply-To: <CADVYk4SBWkAnU4RL6k2_+1aedbFnfptohKffjGdaK6C2bs-6RQ@mail.gmail.com>

Le Sun, 29 Apr 2012 21:16:44 +0800,
Daniel Toussaint <daniel@dmhome.net> a écrit :

> I wish to run an application developed with QT in a Yocto filesystem.
> The app should be linked against Qt4-X11 libs. What is the exact work
> flow to get my app cross compiled on my x86_64 host ?
> So far I have :
> -> Build a complete core-image-sato with IPKG as a packaging system.
> -> Build qt4-x11-free
> -> Build qt4-tools-nativesdk
> 
> Now, I got something called qmake2 in the build directory
> (sysroot-x86_64) , but it complains about not finding the right qmake
> specs.
> I got the feeling I am doing something fundamentally wrong with my
> setup, can anyone enlighten me ?
> 
simply write a recipe for your app and let the build system build
your application.

The recipe can be quite simple if your app doesn't depends on other
libs than qt4 :

DESCRIPTION = "Application QT4-X11"
SECTION = "Apps"
LICENSE = "yourlicense"
LIC_FILES_CHKSUM = "file://youlicense;md5=yourmd5"

inherit qt4x11

SRC_URI = "file://application.tar.bz2"
# or directly download it from a VCS

# may be necessary :
EXTRA_QMAKEVARS_PRE += "PREFIX=/usr"
EXTRA_OEMAKE += "INSTALL_ROOT=${D}"

do_install() {
	oe_runmake install INSTALL_ROOT=${D}
}

Eric


  parent reply	other threads:[~2012-04-29 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-29 13:16 Building a Qt4-x11 app Daniel Toussaint
2012-04-29 14:41 ` Wolfgang Denk
2012-04-29 19:14   ` Eric Bénard
2012-04-29 19:19 ` Eric Bénard [this message]
2012-04-30 10:04   ` Daniel Toussaint

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=20120429211959.3f12671b@eb-e6520 \
    --to=eric@eukrea.com \
    --cc=daniel@dmhome.net \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.