I implemented a hello world example this morning on a STM324xG_EVAL (which worked :), see here) and I had to bring in some changes I had in my original CMake for that project (which was also very hacky and pretty crap). As we at TUM are building up many examples and thus many repositories I would be a fan of having a single FindTFLite.cmake that we can maintain for TF code base changes, new architectures/boards, build types etc.
I would be happy to maintain this as I and my students will probably use it a lot.
We can add it as a fetch dependency to the main CMakeLists to remove any hassle.
I have no clue about cmake, Sorry! But looking into your example's code I sta(r)ted this feature request which had been at the back of my mind for some time now #37
I implemented a hello world example this morning on a STM324xG_EVAL (which worked :), see here) and I had to bring in some changes I had in my original CMake for that project (which was also very hacky and pretty crap). As we at TUM are building up many examples and thus many repositories I would be a fan of having a single FindTFLite.cmake that we can maintain for TF code base changes, new architectures/boards, build types etc.
I would be happy to maintain this as I and my students will probably use it a lot.
We can add it as a fetch dependency to the main CMakeLists to remove any hassle.
Let me know what you think.