yosysSynthesisReport()
should not hardcode the FuseSoC version
#10
Labels
yosysSynthesisReport()
should not hardcode the FuseSoC version
#10
The current usage pattern is:
logPath
should be explicitly set by a user, so their Jenkinsfiles will fall apart once the FuseSoC version changes in the LCCI Image (which is not even parameterizable). My suggestion would be to calculate a default log path inside the Pipeline step. If needed, we can expose version environment variables for tools in the LCCI images.The text was updated successfully, but these errors were encountered: