Hey @philipsdm1,
That is strange, expected behavior would be e.g.
master [/home/lukas/work/repo/tsfpga]$ python3 examples/build.py --generate-registers-only
Generating registers in /home/lukas/work/repo/tsfpga/generated/registers
master [/home/lukas/work/repo/tsfpga]$What python version are you using?
What is the output of python3 examples/build.py --list-only?
--generate-registers-only argument? Because the "No projects matched this filter" printout comes from the parallel build runner, which means that build.py proceeded to try and create or build a project. This should not happen when the --generate-registers-only flag is given. It should exit on line 112 of build.py
Hi @LukasVik ,
I just cloned the repo to my downloads folder
cd to tsfpga folder and entered
python examples/build.py --generate-registers-only
No projects matched this filter:
Generating registers in /Users/userName/.pyenv/versions/3.7.9/lib/python3.7/site-packages/generated/registers
My python version is 3.7.9
What is the output of python3 examples/build.py --list-only?
$ python3 examples/build.py --list only
No projects matched this filter: only
Listed 0 builds
Hi @LukasVik ,
I just cloned the repo to my downloads foldercd to tsfpga folder and entered
python examples/build.py --generate-registers-only
No projects matched this filter:
Generating registers in /Users/userName/.pyenv/versions/3.7.9/lib/python3.7/site-packages/generated/registersMy python version is 3.7.9
Is it possible that there is an invisible character somewhere? I get the same result as you if I add an invisible character at the end of the line:
ludde@VivadoSlachter:~/work/repo/tsfpga$ python3 examples/build.py --generate-registers-only ㅤ
No projects matched this filter: ㅤ
Generating registers in /home/ludde/work/repo/tsfpga/generated/registersI have looked into it now and made some fixes.
The fact that you get printouts related to
/Users/userName/.pyenv/versions/3.7.9/lib/python3.7/site-packages/ indicates to me that you have the tsfpga package installed via pip as well, apart from the repo checkout. This is not illegal in any way, though a little bit unusual. The examples scripts in the repo could not handle this due to the way we handled PYTHONPATH. This if fixed in tsfpga/tsfpga@461dc10Additionally this illustrated that there were files missing from the pip release. Namely the module_*.py that defines the example build projects, as well as many other files. I have fixed that in tsfpga/tsfpga@ffb483f
A new release version will be published as soon as CI passes.
https://pypi.org/project/tsfpga/
https://tsfpga.com/release_notes.html
https://pypi.org/project/tsfpga/
https://tsfpga.com/release_notes.html
With the latest tsfpga release, the VHDL modules are now split out to the standalone project
hdl_modules: https://hdl-modules.com/ https://gitlab.com/tsfpga/hdl_modules/Note that the modules are still bundled with each PyPI release of tsfpga.
https://pypi.org/project/tsfpga/
https://tsfpga.com/release_notes.html
https://hdl-modules.com/release_notes.html
tsfpga.registers package is now split out to the standalone project hdl_registers:https://hdl-modules.com/
https://gitlab.com/tsfpga/hdl_modules/
Note that the tsfpga PyPI package depends on hdl_registers, so if you install tsfpga via pip the change is transparent.
https://pypi.org/project/tsfpga/
https://tsfpga.com/release_notes.html
https://pypi.org/project/hdl-registers/
https://hdl-registers.com/release_notes.html
https://pypi.org/project/hdl-registers/
https://hdl-registers.com/release_notes.html