All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: package VDR for OE
Date: Sun, 13 Dec 2009 17:34:11 +0100	[thread overview]
Message-ID: <hg3523$2lg$3@ger.gmane.org> (raw)
In-Reply-To: <1260711980.3110.21.camel@mattotaupa.wohnung.familie-menzel.net>

On 13-12-09 14:46, Paul Menzel wrote:
> Am Samstag, den 12.12.2009, 18:33 +0100 schrieb Henning Heinold:
>> On Sat, Dec 12, 2009 at 12:48:40PM +0100, Paul Menzel wrote:
>>> I am trying to write a recipe for The Video Disc Recorder (VDR) [1] and
>>> get it into OE.
>>>
>>> Unfortunately I have never done this and I also do not know much about
>>> things related to compiling.
>>>
>>> I tried to follow [2] and [3] and came up with the following which is
>>> not much as you can see and in addition does not work yet.
>>>
>>> The problem I am facing is, that in the Makefile of VDR [4] there is
>>>
>>>          […]
>>>          LIBS     = -ljpeg -lpthread -ldl -lcap -lrt -lfreetype
>>>          -lfontconfig
>>>          INCLUDES = -I/usr/include/freetype
>>>          […]
>>>
>>> so that the path `/usr/include/freetype/` is passed to the make command
>>> which of course fails trying to cross compile the program.
>>>
>>>          CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include/freetype2
>>>          cc1plus: internal compiler error: in add_path, at c-incpath.c:425
>>>
>>> Now, if I understand it correctly by looking at other recipes there is
>>> EXTRA_OEMAKE = "" where I should be able to set the INCLUDEPATH to the
>>> OE build environment. Is that correct.
>>>
>>> Could you please also tell me what the recipe variable name is for libs?
>>
>> What buildsystem is vdr using autotools or handmade Makefiles?
>
> VDR uses a handmade Makefile.
>
> […]
>
>> for handmade Makefiles
>>
>> make a Patch which patches the Makefile and sets the include path to
>> our staginginclude-Path
>
> Thank you! I tried this
>
>          +-INCLUDES = -I/usr/include/freetype2
>          ++INCLUDES = -I${STAGING_INCDIR}/freetype2
>
> but the `${STAGING_INCDIR}` was not expanded. The result is the
> following.
>
>          INCLUDES = -I${STAGING_INCDIR}freetype2
>
> Using an absolute path worked.
>
> Could you please point out my mistake?

AFAIK Makefiles don't use accolades but parens for variables.

regards,

Koen




  parent reply	other threads:[~2009-12-13 16:36 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     ` Koen Kooi [this message]
2009-12-13 18:05       ` package VDR for OE Paul Menzel
2009-12-13 18:32         ` Petr Štetiar

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='hg3523$2lg$3@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.