All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerard van den Bosch <gerard@de-haardt.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: compile application header file missing
Date: Tue, 15 Mar 2011 16:03:16 +0100	[thread overview]
Message-ID: <4D7F7FB4.30007@de-haardt.com> (raw)
In-Reply-To: <1300196286.30423.1726.camel@rex>

On 03/15/2011 02:38 PM, Richard Purdie wrote:
> On Tue, 2011-03-15 at 11:57 +0100, Gerard van den Bosch wrote:
>> Hello,
>>
>> I have programmed an application that uses the OpenSLP library and thus
>> needs the header file from it.
>> OpenSLP is already compiled and running fine on the target.
>>
>> But when I try to compile my application it can't find the header file.
>> When I print out the CFLAGS with bitbake myimage -e | grep CFLAGS the
>> BUILD_CFLAGS point to:
>> /home/gerard/green-3.3/build/tmp/sysroots/i686-linux/usr/include
>> The slp.h is indeed missing, but it is located at:
>> /home/gerard/green-3.3/build/tmp/sysroots/armv7a-poky-linux-gnueabi/usr/include
>>
>> How can I change the CFLAGS to look in the other folder or force OpenSLP
>> to drop it in the i686 folder?
>>
>> I have added OpenSLP to my DEPENDS in the recipe, also tried RDEPENDS
>> but it didn't solve the problem.
> You should be adding OpenSLP to DEPENDS. The toolchain should be
> automatically searching the arm sysroot /usr/include directory for
> include files which is where your file is.
>
> I appreciate this is the green release, in master we have this in
> meta/conf/bitbake.conf:
>
> TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
>
> export CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}"
>
> Back in green, this option should be being hardcoded into gcc as the
> default sysroot option but you could try explicitly setting it.
>
> Note that BUILD_CFLAGS is the wrong place to look, those are for native
> build tools, not target ones. You want to use TARGET_CFLAGS and
> TARGET_CFLAGS should be the same as CFLAGS.
>
> After reading the above, if your image *is* using BUILD_CFLAGS and
> BUILD_CC instead of CC, that is your real problem, it should be using
> the target device compiler, not the build one.
>
> Cheers,
>
> Richard
>
I am indeed using the Green release.

The TARGET_CFLAGS are indeed the same as the CFLAGS. The system is using the default CC and not the BUILD_CC, thanks for pointing out the difference.

I have added the --sysroot option pointing to the arm sysroot to the CFLAGS in my recipe, with compilation it now looks like this:
arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize -fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2 -ggdb -feliminate-unused-debug-types --sysroot=/home/gerard/green-3.3/build/tmp/sysroots/armv7a-poky-linux-gnueabi/ libxmlpcp.c -o libxmlpcp.o

This removes the missing SLP.h error.

Is this problem related to my recipe or did I broke my build environment?

My recipe looks like this:
DESCRIPTION = "libxmlpcp"
SECTION = "examples"
DEPENDS = "openslp libxml2"
LICENSE = "LGPL"

SRC_URI = "file://libxmlpcp.tar.gz"

CFLAGS += --sysroot=/home/gerard/green-3.3/build/tmp/sysroots/armv7a-poky-linux-gnueabi/

do_install() {
     install -d ${D}${libdir}
     install -d ${D}${includedir}
     oe_runmake 'INSTALLHEADERDIR=${D}${includedir}' 'INSTALLLIBDIR=${D}${libdir}' \
     install
}

Regards,
Gerard








  reply	other threads:[~2011-03-15 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 10:57 compile application header file missing Gerard van den Bosch
2011-03-15 13:38 ` Richard Purdie
2011-03-15 15:03   ` Gerard van den Bosch [this message]
2011-03-16 16:08     ` Richard Purdie
2011-03-17  7:43       ` Gerard van den Bosch
2011-03-17  7:52         ` Khem Raj
2011-03-17  8:00           ` Gerard van den Bosch
2011-03-17  8:22             ` Gerard van den Bosch
2011-03-17 13:54               ` Gerard van den Bosch

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=4D7F7FB4.30007@de-haardt.com \
    --to=gerard@de-haardt.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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.