litghost
litghost
> It means that you provide your own dependencies, instead of using external distributions. You build them from source and static link them to the library. I am asking for...
We have documentation on how to do this: https://github.com/SymbiFlow/prjxray/blob/master/docs/db_dev_process/newpart.rst Feel free to take a shot! GitHubSymbiFlow/prjxrayDocumenting the Xilinx 7-series bit-stream format. - SymbiFlow/prjxray
No new documentation has been written since this bug was filled
I think this issue is really highlights how little testing and documentation exists on some of the larger fuzzers. Smaller issues could help here.
There has been an intermittent kokoro failure where the `/tmp` disk is not mounted. I don't believe this is a something that is fixable on the outside.
Ya. It looks like the disk is there, but just needs to be partitioned and formatted. Huh. Maybe a race condition?
Another instance of `/tmp` failure with logging: https://source.cloud.google.com/results/invocations/4cf2fe46-8e69-4325-8bf7-b4fa264637ac/log Develop your code on the Google Cloud Platform.
So I think you are confusing two aspects. If you want to regenerate the prjxray-db database, you need Vivado. However if you are simply using the database to generate bitstreams,...
Note: `get_bel_pins` must be invoked on a placed BEL instance, and cannot be called otherwise.
The makefile should be updated to do the right thing. The idea was that the makefile should enter the environment as needed without additional user action.