[Buildroot] BR2012.rc1 :: problem to build a new package

[Buildroot] BR2012.rc1 :: problem to build a new package

[MERCADIER Johann]

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!

   This program require freetype2 and 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.
Looking at the man pkg-config I should write a .pc file to help pkg-config
to download it. Doing so I manually interfere the automated build process.
  I found some help in the book "Linux Embarqu?" by P.FICHEUX from page 247
and in the doc provided with buildroot but I don't know how and where to
config things to make the things automatically  I mean download of the
required dependencies.
  I wish to learn to do some good work and not a kind of scrappy job even
if it works. So advices are welcome!

Regards,

-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120315/f07b2baf/attachment.html>

[Buildroot] BR2012.rc1 :: problem to build a new package

[Arnout Vandecappelle]

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

[Buildroot] BR2012.rc1 :: problem to build a new package

[MERCADIER Johann]

Hi Arnout,

  Thanks for your suggestions, it helped me. Troubles were caused by a
small mistake:


>  So you should have the line
> <PKG>_DEPENDENCIES += freetype fontconfig
> in your .mk file.
>
> => I forgot to remove the 'lib' prefix from the libraries name, that I got
with a ldd


 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
>
=> this part was already OK


>  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).
>
=> Now that's work. FbTerm is integrated and I can launch it. No troubles
til now.
I went to the website and created a signature.
Now what I am confused with is the proper way to create a patch, do I have
to :
   * use the a simple 'diff'  command, with only the files I modified?
   or
   * use git + git format + git send-mail?... As it's explain here:
http://tutoriels.itaapy.com/wiki/tutoriel-git/#bien-configurer-son-git

  At the end where the signature must be added? Obviously not in the patch
All the one I read didn't have such an information on it.

I didn't find relevant relevant informations on that part. some infos will
be great so as I can finished this part and know it for next time.

Thank you in advance.

Regards.
-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120318/1434eb4e/attachment.html>

[Buildroot] BR2012.rc1 :: problem to build a new package

[Samuel Martin]

Hi Johann, all,

2012/3/18 MERCADIER Johann <johann.mercadier@imerir.com>:
> Hi Arnout,
>
> ??Thanks for your suggestions, it helped me. Troubles were caused?by a small
> mistake:
>
>>
>> ?So you should have the line
>> <PKG>_DEPENDENCIES += freetype fontconfig
>> in your .mk file.
>>
> => I forgot to remove the 'lib' prefix from the libraries name, that I got
> with a ldd
>
>
>> ?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
>
> => this part was already OK
Glad you successfully find your way out :-)

> => Now that's work. FbTerm is integrated and I can launch it. No troubles til now.
> I went to the website and created a signature.
> Now what I am confused with is the proper way to create a patch, do I have to :
> ?? * use the a simple 'diff' ?command, with only the files I modified?
> ?? or
> ?? * use git + git format + git send-mail?... As it's explain here: http://tutoriels.itaapy.com/wiki/tutoriel-git/#bien-configurer-son-git
>
> ??At the end where the signature must be added? Obviously not in the patch All the one I read didn't have such an information on it.
You will find most of the answers here:
http://elinux.org/Buildroot_how_to_contribute

Note that if you didn't had the SOB at commit time, git can add it
when generating patches, just add '-s' option to the git format-patch
command line.
To generate them, I usually use:
$ git format-patch -M -n -s master

As usual, man is your friends ;-)
Have a look at:
$ man git-format-patch
$ man git-send-email

>
> I didn't find relevant relevant information on that part. some infos will be great so as I can finished this part and know it for next time.
You're right, we are working on make it clearer.
We are gathering all pieces of doc and put them in such a way it easy
to find out the relevant information.
It is a continuous process...


Regards,

Sam

[Buildroot] BR2012.rc1 :: problem to build a new package

[MERCADIER Johann]

Hi Sam,

   I succeed in my guest! I just send my patch. Thanks for your support
guys!
  I tested it and it should work. Waiting for your feedback...


> As usual, man is your friends ;-)
> Have a look at:
> $ man git-format-patch
> $ man git-send-email
>
=> I was not asking for someone to give me the better choice to do I
totally agree with the fact that man or google now can be our better
friends! and it's real better to read that than: RTFM! :o))

> I didn't find relevant relevant information on that part. some infos will
> be great so as I can finished this part and know it for next time.
> You're right, we are working on make it clearer.
> We are gathering all pieces of doc and put them in such a way it easy
> to find out the relevant information.
> It is a continuous process..
>
=> I finally found 3 others website from the one you gave to me which are
really good. They use different interresting ways to explain it, but
merging all of them could make a very good startup for noobs! Here are
these sites I don't know if it can be useful?

+http://gitref.org/basic/#diff
+http://elinux.org/Git_usage
+http://elinux.org/Buildroot_how_to_contribute
http://tutoriels.itaapy.com/wiki/tutoriel-git/#bien-configurer-son-git
http://home.regit.org/technical-articles/git-for-the-newbie/

I am working now on omapfbplay. Coming soon... ;o)

Regards.

-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120319/79403e8b/attachment.html>