Open Readon opened 3 months ago
Realistically.. wouldnt someone that uses the template project want to use either sbt or mill and only rarely both? So this would only complicate things.
IMHO there is already a LOT to figure out when starting with scala and spinal, adding another file does not help much.
Realistically.. wouldnt someone that uses the template project want to use either sbt or mill and only rarely both? So this would only complicate things.
IMHO there is already a LOT to figure out when starting with scala and spinal, adding another file does not help much.
Yes, it could be a backup example only.
The history is that in SpinalHDL/SpinalHDL mill is imported, but the existing version control is to use a symlink for version.sc, which is too complicate to use under Windows.
I just find the solution, and think might ease the version bump each time spinalhdl's new version release.
I agree that we should keep it as simple as possible as this is a template. Maybe we can merge this PR in a separated branch ?
Example to support both sbt and mill in one project, and specified version in unified conf file.