Minimal verif changeset for public main

[Fi50]

PR just to add the Makefile flags, can remove OFOConfigs.scala if preferred.

(I only added the label to see if it's enough to pass require release notes but guess not. V_v)

[elamdf]

where is RUN_TYPE_FLAG going to be read? I hesitate on principle to rely on script-exported environment variables for things that change...

[Fi50]

It's read in the generator >_< which is terrible decision but I think when I was doing this I couldn't find a way to:

• find any useful existing env environment
• find a way to get the tool/flow/etc targets
• get the directory being run from directly

I'm sure there's gotta be a way, I just didn't find it so this was the bandage fix to move on with, am super open to alternatives!

[elamdf]

related: ucb-eecs151tapeout/ofot-generator#3

[elamdf]

ofot-chipyard/variables.mk

Line 222 in 1585985

export SBT_OPTS ?= -Dsbt.ivy.home=$(base_dir)/.ivy2 -Dsbt.global.base=$(base_dir)/.sbt -Dsbt.boot.directory=$(base_dir)/.sbt/boot/ -Dsbt.color=always -Dsbt.supershell=false -Dsbt.server.forcestart=true

you might be able to append SBT_OPTS with -D so it's not persistent in your environment after running the make command. I asked in chipyard channel too, so maybe let's wait for jz to show us da wae <_<

[elamdf]

can an issue be made about creating sim vs syn CONFIGs as a better alternative to the env variable hacking? else LGTM

[Fi50]

Made issue: #45
Leaving it to you to merge when happy :D

[elamdf]

LGTM!