3.12 is the Python3 versioning.
@amf99
cmake in the file called build_pip_package_with_cmake.sh and it is available.
So, git clone tensorflow at their github page online!
cd tensorflow_src
mkdir build && cd build
cmake ..
// the cmake can be made to handle arguments like with gnu
// Then...back to it
cmake --build .
On the BBAI-64, it completes but does not produce what I thought it would produce. Oh and I will mention that tensorflow and tensorflow_lite are very large packages. It takes a good day on the board.
I tried other ways. I kept failing at it. Something about mismanaged packages and no cure. anyway…
Also, in /home/debian/tensorflow_src/tensorflow/lite/tools/pip_package/
, there is a file to help, e.g. helper script called build_pip_package_with_cmake.sh
Seth
P.S. I know that is wishy-washy right now but cmake and its good debugging will show evident. Also, there is a way with specific calls to “install” tflite_runtime.
Also!
/home/debian/tensorflow_src/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3/dist/
is where you can find your .whl package once cmake builds it. And as usual, you can cross-compile and/or use bazel. bazel build --config=elinux_aarch64
and other compiler flags can go here to optimize the build for bazel building tensorflow… bazel build is in a different state for me.
That last sentence describes their state of building versus more apology-type debugging. The bazel build source, esp. if you are like me and do not know the ins, outs, and severity it can cause to an unknown system like the BBAI-64, is difficult. Plain and simple. I thought I kept getting further and further with bazel, not bazelisk which is “better,” to compile the tensorflow_lite .so file(s) to build further.
Now, is that true? Did I keep getting further to completion? Who knows? I do not. cmake won me over many times in my life.
Oh! Enough do-dad stuff…
bazel build //tensorflow/tools/pip_package:wheel --repo_env=WHEEL_NAME=tensorflow_cpu
With the correct bazel listed, this is how to install tensorflow on the cpu but cpu only. No, GPU or TPU or whatever else…
Aw! One last thing: My File naming scheme and the .tar file naming scheme...
-rw-rw-r-- 1 debian debian 2473713 Aug 2 11:29 tflite_runtime-2.18.0-cp312-cp312-linux_aarch64.whl
-rw-rw-r-- 1 debian debian 2486929 Aug 2 11:29 tflite_runtime-2.18.0.linux-aarch64.tar.gz
Good luck!