On Fri, Jul 23, 2021, 2:00 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote:
> Hello Chris, > > On 22/07/2021 10:44, Chris Johns wrote: > > Hello, > > > > Libbsd uses the pre-processor to map all the kernel calls into a libbsd > kernel > > name space by prepending _bsd_ to each symbol. The script ... > > > > > https://git.rtems.org/rtems-libbsd/tree/create-kernel-namespace.sh?h=6-freebsd-12 > > > > ... generates the list and the result is pushed into the repo. The > symbols need > > to be regenerated when new sources are added into the `freebsd` tree. > > > > The script has a few issues: > > > > 1. Objdump does not work on FreeBSD for different archs. > > > > 2. Binutils is being removed from FreeBSD base. > > what would be the alternative? > Why wouldn't an RTEMS toolchain work? You built for an architecture we support, so our tools must work. Maybe add a target argument to precede the tools with. We tend not to depend on native tools anyway. > > > > > 3. A number of BSPs need to be built to cover all the possible symbols > > > > I would like to document the list of BSPs a generate needs to cover. I > propose: > > > > arm/xilinx_zynq_a9_qemu > > aarch64/xilinx_versal_lp64_qemu > > i386/pc686 > > powerpc/mvme2307 > > sparc/erc32 > > Basically if you import code you just have to build a BSP which covers > the imported code. Then you use ... > > > > > Also the documentation says to use `git add -p` to add the changes. How > does an > > interactive add help? > > git add -p > > to add only the changes relevant to the imported (or removed or changed) > code. > > -- > embedded brains GmbH > Herr Sebastian HUBER > Dornierstr. 4 > 82178 Puchheim > Germany > email: sebastian.hu...@embedded-brains.de > phone: +49-89-18 94 741 - 16 > fax: +49-89-18 94 741 - 08 > > Registergericht: Amtsgericht München > Registernummer: HRB 157899 > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler > Unsere Datenschutzerklärung finden Sie hier: > https://embedded-brains.de/datenschutzerklaerung/ > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
