mirror of
https://github.com/RPCSX/xed.git
synced 2024-11-23 11:39:40 +00:00
x86 encoder decoder
27e3ad03f1
Change-Id: I1981761e98f9b2a159250d41d95c79953ac78e91 (cherry picked from commit 3fbfb7cb64196669b72506952d8e6943ef33b701) |
||
---|---|---|
datafiles | ||
docsrc | ||
examples | ||
include | ||
misc | ||
pysrc | ||
scripts | ||
src | ||
tests | ||
.gitignore | ||
.travis.yml | ||
appveyor.yml | ||
ci.py | ||
LICENSE | ||
mfile.py | ||
README.md | ||
VERSION | ||
xed_build_common.py | ||
xed_mbuild.py |
Intel X86 Encoder Decoder (Intel XED)
Doxygen API manual and source build manual:
Bugs:
Intel internal employee users/developers:
Everyone else:
https://github.com/intelxed/xed/issues/new
Abbreviated building instructions:
git clone https://github.com/intelxed/xed.git xed
git clone https://github.com/intelxed/mbuild.git mbuild
cd xed
./mfile.py
then get your libxed.a from the obj directory. Add " --shared" if you want a shared object build. Add " install" if you want the headers & libraries put in to a kit in the "kits" directory. Add "C:/python27/python " before "./mfile.py" if on windows.
How to build the examples:
There are two options:
-
When building libxed you can also build the examples, from the main directory (above examples):
./mfile.py examples
and the compiled examples will be in obj/examples.
-
Build a compiled "kit" and the build the examples from within the kit:
./mfile.py install cd kits cd cd examples ./mfile.py
See source build documentation for more information.
Binary size?
Concerned about large libraries or binaries? There are several options:
- Consider building with "--limit-strings"
- Strip the binaries
- Consider doing an encoder-only or decoder-only build if you only need one or the other.