Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[buildbot] TFLite updates #343

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[buildbot] TFLite updates #343

wants to merge 1 commit into from

Conversation

mtrofin
Copy link
Collaborator

@mtrofin mtrofin commented May 8, 2024

  • move to TFLite 2.16.2
  • bump deps' versions accordingly (based on TF bazel workspace)
  • support building with custom sysroot
  • support pthreadpool self-build

The latter currently requires a hack whereby it gets to be installed
in the sysroot. We need to patch pthreadpool to support find_packge.

- move to TFLite 2.16.2
- bump deps' versions accordingly (based on TF bazel workspace)
- support building with custom sysroot
- support pthreadpool self-build

The latter currently requires a hack whereby it gets to be installed
in the sysroot. We need to patch pthreadpool to support `find_packge`.
Copy link
Collaborator

@boomanaiden154 boomanaiden154 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable enough to me.

We don't need to patch pthreadpool upstream to support find_package, we just need to add a find module, probably on the tensorflow side. There is support for downloading/specifying the pthreadpool source natively within the tensorflow build, but I remember running into issues the last time I hacked on the build. It should probably be converted to a find module and use an external build just like everything else rather than hackily using CMake to build it as part of the TFLite build if not specifying to use the system dep.

# pthreadpool
# NOTE: currently a hack, because pthreadpool doesn't support find_package.
# we install in the default install dir, which really means the script must be run
# under sudo. Works for buildbots. Not ideal elsewhere.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would need doc updates probably?

I'm wondering if we should just install it to the sysroot if that's specified, but otherwise default to the system dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants