OLD | NEW |
(Empty) | |
| 1 # Linux Syscall Support (LSS) |
| 2 |
| 3 Every so often, projects need to directly embed Linux system calls instead of |
| 4 calling the implementations in the system runtime library. |
| 5 |
| 6 This project provides a header file that can be included into your application |
| 7 whenever you need to make direct system calls. |
| 8 |
| 9 ## How to include linux\_syscall\_support.h in your project |
| 10 |
| 11 You can either copy the file into your project, or preferably, you can set up |
| 12 Git submodules to automatically pull from our source repository. |
| 13 |
| 14 ## Projects that use LSS |
| 15 |
| 16 * [Chromium](https://www.chromium.org/) |
| 17 * [Breakpad](https://chromium.googlesource.com/breakpad/breakpad) |
| 18 * [Native Client](https://developer.chrome.com/native-client), in nacl\_bootstra
p.c |
| 19 |
| 20 ## How to get an LSS change committed |
| 21 |
| 22 ### Review |
| 23 |
| 24 You get your change reviewed, you can upload it to |
| 25 [Rietveld](https://codereview.chromium.org) |
| 26 using `git cl upload` from |
| 27 [Chromium's depot-tools](http://dev.chromium.org/developers/how-tos/depottools). |
| 28 |
| 29 ### Testing |
| 30 |
| 31 Unfortunately, LSS has no automated test suite. |
| 32 |
| 33 You can test LSS by patching it into Chromium, building Chromium, and running |
| 34 Chromium's tests. |
| 35 |
| 36 You can compile-test LSS by running: |
| 37 |
| 38 gcc -Wall -Wextra -Wstrict-prototypes -c linux_syscall_support.h |
| 39 |
| 40 ### Rolling into Chromium |
| 41 |
| 42 If you commit a change to LSS, please also commit a Chromium change to update |
| 43 `lss_revision` in |
| 44 [Chromium's DEPS](https://chromium.googlesource.com/chromium/src/+/master/DEPS) |
| 45 file. |
| 46 |
| 47 This ensures that the LSS change gets tested, so that people who commit later |
| 48 LSS changes don't run into problems with updating `lss_revision`. |
OLD | NEW |