| commit | 08056836f2b4a5747daff75435d10d649bed22f6 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Wed Oct 07 20:59:57 2015 |
| committer | Mike Frysinger <vapier@chromium.org> | Wed Oct 07 20:59:57 2015 |
| tree | 459531b2c35e585e0377c3bc592f6eaef7b02d6d | |
| parent | 9292030109847793f7a6689adac1ddafb412fe14 [diff] |
migrate site/wiki docs over Now that we've moved to GoB from code.google.com, import the docs. This is a merge of three pages: https://code.google.com/p/linux-syscall-support/ https://code.google.com/p/linux-syscall-support/wiki/HowToContribute https://code.google.com/p/linux-syscall-support/wiki/ProjectsUsingLSS The svn logic was updated to git, and some more links added. R=mseaborn@chromium.org Review URL: https://codereview.chromium.org/1393083002 .
Every so often, projects need to directly embed Linux system calls instead of calling the implementations in the system runtime library.
This project provides a header file that can be included into your application whenever you need to make direct system calls.
You can either copy the file into your project, or preferably, you can set up Git submodules to automatically pull from our source repository.
You get your change reviewed, you can upload it to Rietveld using git cl upload from Chromium's depot-tools.
Unfortunately, LSS has no automated test suite.
You can test LSS by patching it into Chromium, building Chromium, and running Chromium's tests.
You can compile-test LSS by running:
gcc -Wall -Wextra -Wstrict-prototypes -c linux_syscall_support.h
If you commit a change to LSS, please also commit a Chromium change to update lss_revision in Chromium's DEPS file.
This ensures that the LSS change gets tested, so that people who commit later LSS changes don't run into problems with updating lss_revision.