[RSB Graphics Library] add patch for library source

Hesham ALMatary heshamelmatary at gmail.com
Tue Jun 30 22:40:08 UTC 2015


On Tue, Jun 30, 2015 at 5:54 PM Gedare Bloom <gedare at gwu.edu> wrote:

> Chris,
>
> Have we documented how to get custom patches working in RSB?
>
> I CC'ed Hesham too, since he has done this recently, he might have some
> advice.
>
> There were two ways I used to get RSB fetch the patches: 1) An absolute
URL to a patch (on Github for example), and I think some gaisler and/or
sparc tools do the same, and 2) Place the patch at rtems-tools as Dr. Joel
mentioned and refer to it from RSB.

I think RTEMS would prefer the second approach to avoid fetching from
external sources that might be changed or even the URL might get
invalidiated, seizing the whole toolchain build (and IIRC that happened
with sparc)

> Gedare
>
> On Tue, Jun 30, 2015 at 3:24 AM, QIAO YANG <yangqiao0505 at me.com> wrote:
> > Hi,
> >
> > I'm now working on moving the graphic libraries from
> rtems-graphic-tool-kits
> > into rsb, based on the existing work for libjpeg and the
> > rtems-graphic-tool-kits's buid script.
> >
> > The port of libpng, libtiff, freetype2 can be review on my github:
> > https://github.com/yangqiao/rtems-source-builder/commits/graphics
> >
> > While I've got some problems when trying to add patch for source code.
> > As what I've read from other cfg files, we should first "patch add" the
> > needed patches, then "patch setup" to apply them. When I try to add the
> > patch under source-builder/patches/,  it warned me that the path doesn't
> > have a proper protocl such as https, git .... And I've found that some
> > patches of gdb ..etc are in rtems-tools and the sb-build retrieve them
> from
> > the git server. How can I add a patch from source-builder/patches/
> instead
> > of uploading to rtems-tools ? Or maybe I missed something?
> >
> > Thanks in advance
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20150630/e5cbce3c/attachment-0002.html>


More information about the devel mailing list