View Single Post
Old 08-18-2012, 01:30 AM   #68
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Here is one, well, one pair, of programs to add to the collection:
http://www.daemonology.net/bsdiff/

Should be easy to add-in (and push upstream) to Buildroot.
The general use would be to build bsdiff for the host and bspatch for the target but the makefile isn't organized that way.
So just build the pair for both host and target with two calls to GENTARGETS ( ... )

If you haven't added a package file to Buildroot before, for this one just copy one of the simplest ones you can find - text edit the various names.
The GENTARGETS macro will write the actual makefile glue between Buildroot and the package's makefile.

This package depends on one external package, libbz2 but I suspect that package is already defined in Buildroot.

Upstream **might** want a patch included to change that CFLAGS line (which would over-ride the optimization level selected in Buildroot and also contains a LDFLAGS item.

- - - -

Oh, as I am sure you have learned by now - you can build any individual package in Buildroot with the correct "make ... ... ..." Voodo command.
knc1 is offline   Reply With Quote