# chromium_third_party_cros_system_api

**Repository Path**: openharmony-tpc/chromium_third_party_cros_system_api

## Basic Information

- **Project Name**: chromium_third_party_cros_system_api
- **Description**: 第三方软件cros_system_api
- **Primary Language**: Unknown
- **License**: BSD-2-Clause
- **Default Branch**: master
- **Homepage**: https://gitee.com/openharmony-sig/chromium_third_party_cros_system_api
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 5
- **Created**: 2023-08-11
- **Last Updated**: 2026-07-17

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

## 🚨 **重要提示 | IMPORTANT**
>
> **⚠️ 此代码仓已归档。新地址请访问 [chromium_third_party_cros_system_api](https://gitcode.com/openharmony-tpc/chromium_third_party_cros_system_api)。| ⚠️ This repository has been archived. For the new address, please visit [chromium_third_party_cros_system_api](https://gitcode.com/openharmony-tpc/chromium_third_party_cros_system_api).**
>
---
>
This directory (`platform2/system_api`) contains constants and definitions
like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files.
No implementation should be added.

When writting a .proto file make sure to use:

```
option optimize_for = LITE_RUNTIME;
```

This will force usage of a lite protobuf instead of a full/heavy weight
protobuf. The browser only links against the light version, so you will get
cryptic link errors about missing parts of Message if you define a protobuf here
and then try to use it in Chrome. Currently CrOS links against the full
protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you
mean. "Required is Forever" and very rarely should actually be used. Consult
[Protocol Buffer Basics: C++](http://code.google.com/apis/protocolbuffers/docs/cpptutorial.html)
for a detailed of this issue.