From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: package VDR for OE
Date: Sun, 13 Dec 2009 19:32:38 +0100 [thread overview]
Message-ID: <20091213183238.GB1260@ibawizard.net> (raw)
In-Reply-To: <1260727515.3110.65.camel@mattotaupa.wohnung.familie-menzel.net>
Paul Menzel <paulepanter@users.sourceforge.net> [2009-12-13 19:05:15]:
> > AFAIK Makefiles don't use accolades but parens for variables.
>
> I see. But
>
> -INCLUDES = -I/usr/include/freetype2
> +INCLUDES = $(STAGING_INCDIR)/freetype2
>
> did not help and resulted in.
>
> INCLUDES = $(STAGING_INCDIR)/freetype2
No, I think, that Koen was writing about your general mistake. If there was
STAGING_INCDIR available in the environment, your ${} won't work anyway.
Correct is to use $(), parens in Makefile when accessing variables. It's
nothing about your issue.
-- ynezz
prev parent reply other threads:[~2009-12-13 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 11:48 package VDR for OE Paul Menzel
2009-12-12 17:33 ` Henning Heinold
2009-12-13 13:46 ` Paul Menzel
2009-12-13 14:18 ` Petr Štetiar
2009-12-13 15:45 ` Paul Menzel
2009-12-14 19:13 ` Paul Menzel
2009-12-14 20:10 ` Henning Heinold
2009-12-14 20:28 ` Paul Menzel
2010-01-03 14:15 ` Paul Menzel
2010-01-04 21:37 ` [done] " Paul Menzel
2010-01-10 12:40 ` environment variables in Makefile for cross compilation (was: package VDR for OE) Paul Menzel
2010-01-10 13:00 ` Frans Meulenbroeks
2010-01-19 0:22 ` Setting environment variables in recipes and fixing upstream the right way to cross compile? " Paul Menzel
2009-12-13 16:34 ` package VDR for OE Koen Kooi
2009-12-13 18:05 ` Paul Menzel
2009-12-13 18:32 ` Petr Štetiar [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=20091213183238.GB1260@ibawizard.net \
--to=ynezz@true.cz \
--cc=openembedded-devel@lists.openembedded.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.