Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] BR2012.rc1 :: problem to build a new package
Date: Fri, 16 Mar 2012 00:54:10 +0100	[thread overview]
Message-ID: <201203160054.10741.arnout@mind.be> (raw)
In-Reply-To: <CAPEB33x+aVFQoFgN8FXUDWsdqux4Kgf6cPnpMnxN3eRLedGB2g@mail.gmail.com>

On Thursday 15 March 2012 14:45:58 MERCADIER Johann wrote:
> Hi all,
> 
>    I try to add my 1st package to BR.
>    I primarily succeed compiling the program manually and once it had been
> added to the rootfs. I could use it normally wihtout bug til now.
>    Then as I would like to add this functionality to build root through the
> menuconfig option. This part seems ok
>    The next one is to built a .mk file and here start the troubles!

 That should be pretty easy with the AUTOTARGETS infrastructure.

>    This program require freetype2 and fontconfig. 

 So you should have the line
<PKG>_DEPENDENCIES += freetype fontconfig
in your .mk file.

 Normally configure should pick it up automatically then.

 Make sure that the Config.in also has the lines
	select BR2_PACKAGE_FREETYPE
	select BR2_PACKAGE_FONTCONFIG

 
>    On my system pkg-config
> can find it at the following places:
> ./workdone/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/lib/pkgconfig/freetype2.pc
> ./output/target/usr/lib/pkgconfig/freetype2.pc
> ./output/build/freetype-2.4.8/builds/unix/freetype2.pc
> 
>   But it cannot find any .pc file for fontconfig and then quit with an
> error.

 After the fontconfig package is built, you should have a fontconfig.pc
next to the freetype2.pc.


[snip]
>   I wish to learn to do some good work and not a kind of scrappy job even
> if it works. So advices are welcome!

 As soon as you have something that works more or less, post it and
we'll give feedback!SO-0809-Leuven-M.S.G

 Preferably, use git send-email to send the patch.  That makes sure all the
tabs and line breaks are properly conserved, and that the commit message
and authorship is correct.  Also add your Signed-off-by line to the commit
message (see http://kerneltrap.org/files/Jeremy/DCO.txt).

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-03-15 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 13:45 [Buildroot] BR2012.rc1 :: problem to build a new package MERCADIER Johann
2012-03-15 23:54 ` Arnout Vandecappelle [this message]
2012-03-18 21:41   ` MERCADIER Johann
2012-03-18 22:09     ` Samuel Martin
2012-03-19 15:16       ` MERCADIER Johann

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=201203160054.10741.arnout@mind.be \
    --to=arnout@mind.be \
    --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