Releases: google/emboss
Releases · google/emboss
v2024.0328.174154
Update Python version requirement (#117) Updates the minimum supported Python version to 3.8 and notes the policy of tracking the support timeline of the Python project.
v2024.0304.184309
Fix `import_dirs` support (#114) `import_dirs` arguments come through as part of the `ctx.files` list and need to have their `path` extracted when building the `embossc` command-line. This CL also adds a `testdata` entry that checks that `emboss_cc_library` works when specifying `import_dirs`. Test: bazel build '//testdata:import_dir_importer_emboss'
v2024.0301.001301
Add support for a import_dirs param (#113) This adds support for specifying custom `import_dirs` in an `emboss_cc_library` bazel declaration. Example usage: emboss_cc_library( name = "foo", srcs = ["public/foo/foo.emb"], import_dirs = ["public"], )
v2024.0228.001840
Add --output-file embossc flag to allow setting exact generated file …
v2024.0220.215552
Merge pull request #111 from reventlov/importlib_instead_of_pkgutil Switch from pkgutil to importlib.resources.
v2024.0214.172519
Move cpp_utils to compilation_contexts (#109) Move cpp_utils from the cc_common.compile private_hdrs parameter to the compilation_contexts parameter in order to fix the cpp_utils header include paths when Emboss is an external repository. Fixes #108
v2024.0208.184122
Fix using emboss_cc_library from external Bazel repo (#106) Fixes google#105
v2024.0207.171840
Fix emboss_cpp_library Bazel rule (#104) Add `toolchains` parameter to _cc_emboss_aspect rule to fix find_cpp_toolchain error. Fixes #103
v2024.0112.220248
Reorder sections in bits to match the ordering in struct (#102) * doc: reorder sections in bits to match the ordering in struct * doc: add documentation about using struct to effectively create a union (#101)
v2023.1004.224448
Fix subscripted types for Python 3.8 (#97) The changes in PR #89 inadvertently added a line that is incompatible with Python version 3.8. However, Python 3.8 is still supported for around one more year from now (https://devguide.python.org/versions/), so this change restores 3.8 compatibility.