ISE backend support for general "project set" commands about edalize HOT 4 CLOSED

Have you seen the support for loading arbitrary tcl files by setting the file type to tclSource ? There's an example of how this is used for the ISE backend to set a TCL command that turns on a different HDL parser in this target with the use of apf27/options.tcl

Would that help in your case?

from edalize.

I believe I've seen that before and promptly forgot so thanks for the reminder! I think that will work for this case.

Unfortunately I'd already gotten ahead of myself! See GCHQDeveloper560/edalize@43a3620. The second commit adding this feature is probably not useful. However, the first commit (0728f4d) just converts the existing behaviour to a template. I put it out there in case you think it's a little cleaner than the TCL approach, but it probably just exchanges messy TCL for messy Jinja. I'm fine with taking the change or leaving it!

from edalize.

Have you had the chance to check if using tclSource helps with your case?

Regarding the TCL to jinja conversion I'm still undecided. I have not had a purely positive experience of converting to jinja so I'm kind of leaning towards keeping the TCL as is. But now I know where to find a patch if I was to change my mind

from edalize.

Using tclSource works for me, and I'm fine with leaving the TCL out of Jinja if that's your preference.

from edalize.