Closed TommyMurphyTM1234 closed 7 years ago
Docker ... MSYS2 ...
for quick development cycles you can use whatever environment you prefer, but for public releases a controlled build in a controlled environment is recommended.
the build fails due to warnings
I know, I silence these annoying warnings in my scripts. the purpose of the GNU MCU Eclipse OpenOCD fork is mainly to facilitate the integration into the GNU MCU ecosystem, I do not have the resources to fix errors/warnings, so please address these suggestions to the RISC-V maintainers.
RISC-V target support files get compiled even if --disable-riscv is not specified
I noticed this, but I do not know the dependencies of this file. in the QEMU build there are many conditional definitions in the makefile fragments, perhaps something similar can be used here.
please feel free to suggest imprevements in the form of pull requests.
I've logged the issue against the SiFive openocd fork here:
https://github.com/riscv/riscv-openocd/issues/71
So I'll close this one - I presume that's OK?
ok
Again not a major issue but a small annoying build issue.
I realise that you build using Docker but I am building on MinGW-64/MSYS2 using the i686 (32 bit environment) as follows:
However the build fails due to warnings (treated as errors by default) in the RISC-V target support:
To build successfully I have to specify --disable-werror:
Note that building the official OpenOCD 0.10.0+dev sources without specifying --disable-werror at configuration time works fine:
BTW - I'm not sure if it's another (small) issue that the RISC-V target support files (and fespi.c etc.) get compiled even if --disable-riscv is not specified? I don't know if the openocd build process normally does selective compilation based on the flags specified?