https://github.com/intelxed/xed/issues/new
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/libxed.so (Linux) or xed.lib (Windows) 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:/python3/python " before "./mfile.py" if on windows.
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 <whatever the kit is called>
cd examples
./mfile.py
See source build documentation for more information.
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.
In order to contribute, please:
- Read the Contribution Agreement
- Sign your commit message to show your agreement
- Submit a Pull-Request