Graham Sanderson
Graham Sanderson
Note also, that lots of code like ``` # Example common such as compiler warnings include(${CMAKE_CURRENT_SOURCE_DIR}/../../example.cmake) ``` was added to each example CMakeLists.txt, however there was a function call in...
converting this to a draft as I'm not going to apply this quick fix at the moment
the bcel in external is patched (to make it renentrant... running with the bcel from maven for me is causing random exceptions at runtime.
maybe look at the .DIS and see what calls them?
Note if you use the compilers mentioned in the README.md for branch b0/b1 in the bootrom repo (different compiler for the two branches) then you should get an identical binary...
Its a bit of a weird one to be checking actually, since Windows itself will happily mount such a volume, and those fields are supposed to indicate a bootable volume...
can you please rebase
relates to #881
merged into develop
One issue with using `CMAKE_TOOLCHAIN_FILE` is that the SDK build also builds native tools used by the build (which was deemed easier for the majority of users/platforms). We may revisit...