lxbuildenv is a Python module that takes care of setting up your build environment for LiteX. It is simple to use, cross-platform, and self-contained.
|
ℹ️
|
The initial setup process is, admittedly, a little rough. Patches are welcome. |
You can execute lxbuildenv.py directly. Run python lxbuildenv.py --init to create a new project. This will perform the following steps:
-
Ask you for a main entrypoint name, if
--mainwas not set -
Create a git repository, if one does not already exist, unless
--no-gitwas set -
Create a
bindirectory and populate it, if--no-binwas not set -
Create an initial template program
From this point onwards, you do not need to invoke lxbuildenv.py. However, it must still be present in order for your program to run.
The purpose of lxbuildenv.py is to make it easier to get started on a project. It’s also designed to help you work on support libraries. It tries to use system dependencies whenever possible, including using system Python and system compilers.
As such, lxbuildenv.py does some tricky things with PYTHONPATH. It also re-executes itself to ensure PYTHONHASHSEED is set. Additionally, it ensures you have any dependencies installed already.
It does not download dependencies for you — for certain software that’s not even legally allowed. Instead it makes sure the software exists and is usable, and where to obtain it if it’s not available.
The lxbuildenv.py script adds several command line arguments to your program. These all begin with --lx-. To list all parameters provided by lxbuildenv.py, run --lx-help.
|
|
Because it adjusts the import path, you must import lxbuildenv before you import any other packages.
|
Dependencies are specified by adding a variable in your main file called LX_DEPENDENCIES. The fact that this is a variable rather than some other method should set off alarm bells and tell you something funny is going on in lxbuildenv.py. This is true.
As part of its initialization, lxbuildenv.py will read in your program and look for this variable. It will then check any dependencies you’ve specified to ensure they are met, and may patch up the environment if necessary. For example, if you specify vivado as a dependency, lxbuildenv will make sure it can run the vivado program, and will add /opt/Xilinx/…/ or C:\\Xilinx\... to the PATH as necessary.
To list all possible dependencies, run python lxbuildenv.py --lx-print-deps. If you want to try building something without having all the necessary dependencies, add --lx-ignore-deps to your build.