cbor: use unversioned libchrome libraray.

Libchrome is changing pkg-config and .so library name from
xxxx-${libbase_ver}.{pc,so} to xxx.{pc,so}.

Libchrome uprev rebuild will be handled by ebuild subslot change. And
there's no need to install multiple libchrome. Keeping libbase_ver
suffix will cause troubles on linking libraries when developers wants to
test locally emerge a-single-package without build_packages, after a
libchrome uprev. Especially in a case a package depends on another
package(library), and both depends on libchrome. Thus, removing
libbase_ver from suffix.


Change-Id: I2b85c7c42d5ada974aa00a3a26118549fc74a14c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/cbor/+/2501401
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Commit-Queue: Qijiang Fan <fqj@google.com>
Tested-by: Qijiang Fan <fqj@google.com>
1 file changed
tree: 44021ce5241d712ce75d8be72c55f0e61dde192b
  1. reader_fuzzer_corpus/
  2. BUILD.gn
  3. cbor_export.h
  4. constants.h
  5. diagnostic_writer.cc
  6. diagnostic_writer.h
  7. diagnostic_writer_unittest.cc
  9. reader.cc
  10. reader.h
  11. reader_fuzzer.cc
  12. reader_unittest.cc
  13. README.md
  14. values.cc
  15. values.h
  16. values_unittest.cc
  17. writer.cc
  18. writer.h
  19. writer_unittest.cc

cbor: Concise Binary Object Representation

This library is a partial implementation of the RFC 7049 Concise Binary Object Representation standard.

The source code was fetched from chromium/src (https://chromium.googlesource.com/chromium/src/+/242df8b64d2a0ab5f057d1d4c76ea8537fdbb789) in order to avoid code duplication.

The cros/upstream/master branch is a mirror of the components/cbor directory from upstream. It is automatically updated to reflect the latest changes in upstream.

How to update the source

To pull in updates from chromium/src, do the following:

  • git checkout -b upstream cros/upstream/master
  • git checkout master
  • git merge --allow-unrelated-histories upstream
    • Expect merge conflicts, because of the difference in header paths.
    • OWNERS should use the version from master.
    • BUILD.gn should mostly use the version from master, unless the upstream changes the files to be built.
    • The #include paths should use the version from master (without “components/”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the changes from upstream that are merged, with original commit hash from upstream.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.