fusesoc icon indicating copy to clipboard operation
fusesoc copied to clipboard

Allow for targets without a tool

Open saw235 opened this issue 5 years ago • 2 comments
trafficstars

I am trying to somehow integrate some existing aldeclint script into my local swervolf project without messing with the backend edalize. For example, I have the following in the *.core file

targets:
  aldeclint:
    hooks :
      post_run : [run_aldec]

but no matter how I do it, I am restricted by the need for tools to be specified under the aldeclint target

ERROR: No tool was supplied on command line or found in 'swervolf' core description

Is there some other way to do this?

saw235 avatar Jan 31 '20 12:01 saw235

Hi,

I just started experimenting with adding a generic tool that makes it easier to hook into other toolchains. Check out the https://github.com/olofk/edalize/tree/generic_tool branch and let me know if there is something in particular you would need

olofk avatar Feb 15 '20 21:02 olofk

I have a case similar to this, I have a generator to run that takes some VHDL files and generates C/C++ headers from the constants within the VHDL files (for software to interact with the FPGA image). I'm currently having to provide both a toplevel & a tool:

targets:
  default:
    generate: [export_headers]
    filesets: [fileset_a, fileset_b]
    toplevel: fake_toplevel
    default_tool: modelsim

would your proposed generic_tool work in this instance too? I only need to be able to perform run --setup --noexport, no build needs to take place just need to trigger the generator(s)

GCHQDeveloper028 avatar Jul 08 '20 11:07 GCHQDeveloper028