And just pull in the function with an `include, you mean ?
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
Yes
Philipp Wagner
@imphil
it's too bad icarus verilog is not supporting any recent SV standards, so it's become pretty much unusable on my side
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
thats unfortunate its pretty fast
Created a pr to fix it
openrisc/mor1kx#57
Plus I have an old PR still open
openrisc/mor1kx#56
@olofk what are your tips for managing local development versions of cores with fusesoc? I have my local versions ahead of fusesoc-cores and orpsoc-cores in my PATH
but... sometimes if I don't have the versions just right it takes the non local versions
So I have to be very careful and always do fusesoc core-info and watch which versions are pulled in
Olof Kindgren
@olofk
Yeah, same here
You can keep multiple workspaces with different fusesoc.conf
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
ah, that might be nice
Olof Kindgren
@olofk
Or if you're just working on a specific core, you can pull that one in with fusesoc --cores-root=/path/to/core sim ...
Ghost
@ghost~5910ddcfd73408ce4f5dfa87
that is good too, I didn't know
need to read the manual
Thanks, I thought I would ask while I have your attention :)
Olof Kindgren
@olofk
Reading the manual won't help you much :)
I think it would be nice to extend list-cores to also show locations of the cores. That way you don't have to run core-info for every single one