From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] Q: How to change include paths?
Date: Tue, 27 May 2008 12:32:11 -0700 (PDT) [thread overview]
Message-ID: <17498220.post@talk.nabble.com> (raw)
In-Reply-To: <C681C76E0D5F1E4BB01DE79E0A80EEC7765D34@usrdes03.ebgroup.elektrobit.com>
I have been building Cairo and DirectFB recently for my platform.
I have found the include paths to be correct as long as pkg config finds the
.pc files properly. The other issue I had was the build order and I posted
a patch that made sure directfb is built first before cairo is compiled.
The patches I posted also stopped cairo etc from redefining PKG_CONFIG_*
variables.
I hope these get adopted by buildroot. Maybe try these and then see if the
problem goes away.
Cheers
Dan Laird
Michael.Forkey wrote:
>
> What is the correct way/place to change the include paths for a package
> build in buildroot?
>
> When I build cairo with directfb support I get a build error. It expects
> directfb.h to be in /staging_dir/include/directfb but it is actually in
> /staging_dir/usr/include/directfb.
>
> How can I fix this?
>
> Thanks,
> mf
>
>
> ----------------------------------------------------------------
> Please note: This e-mail may contain confidential information
> intended solely for the addressee. If you have received this
> e-mail in error, please do not disclose it to anyone, notify
> the sender promptly, and delete the message from your system.
> Thank you.
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
--
View this message in context: http://www.nabble.com/Q%3A-How-to-change-include-paths--tp17495303p17498220.html
Sent from the BuildRoot mailing list archive at Nabble.com.
prev parent reply other threads:[~2008-05-27 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 17:04 [Buildroot] Q: How to change include paths? Michael.Forkey at elektrobit.com
2008-05-27 19:32 ` Daniel Laird [this message]
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=17498220.post@talk.nabble.com \
--to=daniel.j.laird@nxp.com \
--cc=buildroot@busybox.net \
/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