tree f135738d8976871a1b53baa66956c50242f41e85
parent 10877f61c2e73d578bb889012b84bbd1edf15ed0
author Scott Todd <scott.todd0@gmail.com> 1721849258 -0700
committer GitHub <noreply@github.com> 1721849258 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmoVWqCRC1aQ7uu5UhlAAAvlsQAFP/K3+QjwyhyDrB0lhasCAi
 nJxlldED68qnCgeJ/jcpRwiwKnRxJ6swTzsLgXaeoscnzX/uW8y2eVYh666a3zNe
 /t0qTg1fOOGZrE0MXeukz7F27RELzJ8Jjl3kZwU8wIxwseTo4hFVhFjmQFRTg9NW
 9hSggv4x26GVOimUbHoz37Ay5iAbSjENi04RW3M6dFOqNMwEepj3GfievPb3Kis5
 9s5fEpn6rhckGyzv8XYotlsIO5/LYKSYcYWW2CmA+1ucA/puA/vhh2ve/vBOqMxe
 1LL9Y9fMDL1z1fTchnvBTlc8n1FppqevrAAHK6DUgiMkB2UulpihgrFf0QUqvgCr
 Ea/kmWVRtrZw5mhrK9sxI+oBPATgT1TfZhN/TRnJXZb2moG1SX1bCr8P4D9Hc53d
 id6zkAPD2wxXY20FbwGYS79SXa3YVkb5/Ft51JgRngK4l9YYcPrfSDUCzISPR358
 NZcjYsNdZKo2X7kVRDmXamg0/h+ygbk9DmrJFr1LW/TW4NXwM4EX5tEYxYDqZAvc
 +TyROsX3o9ijT7F3Q4ZWAcibra4uALicEMEQ1v2xqYDR0T9hLHDZZYMe56OSqbJ6
 EqxdrKddE5lq0jkK3aSJ3JMvvzxvKrqXFi7taqVJaZzxIi0xO2llSGosml+uAmia
 HodVC/oalRonakjJd683
 =GkTa
 -----END PGP SIGNATURE-----
 

Add `iree-c-embed-data` and `iree-flatcc-cli` to release packages. (#18001)

Progress on https://github.com/iree-org/iree/issues/16203.

First, this renames `generate_embed_data` to `iree-c-embed-data`. The
name here dates back to having a single implementation shared across
multiple projects using Bazel (and Google's internal Blaze). There isn't
much code in the tool, but we've been using it for long enough to give
it a name matching our other tools IMO.

Next, this includes `iree-c-embed-data` and `iree-flatcc-cli` in the
`iree-runtime` Python package (https://pypi.org/project/iree-runtime/).
Both of these host tools are required for building large parts of the
runtime (embed data for builtins and bitcode, flatcc for schemas), so
including them in packages will allow users (and pkgci workflows) to get
them without needing to build from source.