Re: [RSB Graphics Library] add patch for library source
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. Gedare On Tue, Jun 30, 2015 at 3:24 AM, QIAO YANG yangqiao0...@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 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB Graphics Library] add patch for library source
On 6/30/2015 11:54 AM, Gedare Bloom 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. I don't know if it is documented. But if the upstage doesn't have a patch retrieval system, then it goes in rtems-tools on our side as far as I understand. For testing, you can manually place the patch in the RSB patches directory. FWIW I have a series of patches for 5 packages to add to the RSB. Gedare On Tue, Jun 30, 2015 at 3:24 AM, QIAO YANG yangqiao0...@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 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available(256) 722-9985 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB Graphics Library] add patch for library source
On Tue, Jun 30, 2015 at 5:54 PM Gedare Bloom ged...@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 yangqiao0...@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 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB Graphics Library] add patch for library source
On 1/07/2015 4:35 am, Joel Sherrill wrote: On 6/30/2015 11:54 AM, Gedare Bloom 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. I don't know if it is documented. But if the upstage doesn't have a patch retrieval system, then it goes in rtems-tools on our side as far as I understand. We have been putting patches into rtems-tools when there is no other home. Having no patches in rtems-tool is the ideal situation. This is the first use case, the RTEMS project needs a specific patch. For testing, you can manually place the patch in the RSB patches directory. This is the second use case, when testing patches. Placing the files in the patches directory and then adding any path to the config file works. The RSB uses the basename of the URL for the file name and it checks the patches directory for that file. Another solution is to define a real path such as the rtems-tools repo and to create a user macro file. An example I am currently using for qemu is: # # QEMU patches # [patch-qemu] patch0100: none, override, 'file://opt/work/chris/rtems/rsb/patches/0001-FIXME-Hack-to-support-libbsd-tests.patch' patch0101: none, override, 'file://opt/work/chris/rtems/rsb/patches/0001-net-cadence_gem-Set-initial-MAC-address.patch' Notice, absolute paths. I am not sure if relative paths work. I have not tried. Use high patch numbers that keep clear of any patches included in the base config files. The RSB applies the patches in the numbered order. Use the --macros argument to supply the macros with the patches. The RSB places the places in a macro map with the name of the patch set prefixed by 'patch-'. The source files live in a different map to the where the map name prefix is 'source-'. This lets the RSB collect all the sources and patches without packages overlapping each other in a build set. If you add '--dry-run --trace' the log file will output the macros. FWIW I have a series of patches for 5 packages to add to the RSB. Please post. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
