Multi-project support in same or separate repo?

[jrrk2]

xc7k325-blinky-nextpnr only supports one project at the moment. Opened a new branch:
project_select in git@github.com:jrrk2/xc7k325t-blinky-nextpnr.git to allow picosoc to be built using the same Makefile. This invalidates the name of the project, so this is just a placeholder to discuss what should be done to make it scalable.

This new project builds fine and flashes on an Apple OSX M1 machine.

[unbtorsten]

I suggest waiting for @rwhitby to finish refactoring the make procedure, cf. #18. Either way, it may be reasonable to create a separate repo for the picosoc process (and other designs in the future)?

[rwhitby]

rwhitby#1 has files distinguished by ${PROJECT_NAME} and ${BOARD}, so multiple projects in the same directory should be possible. Whether or not that is a good idea is a separate question :-)

[unbtorsten]

Looks good. :) At minimum, this makes the Makefile flexible enough to be used for other projects.
Can you change its first line from

PROJECT_NAME = blinky

to

PROJECT_NAME ?= blinky

That way, the project name can be set when calling make.

[jrrk2]

OK done, but I think command line variable overrides take priority over =, = takes priority over the environment, and environment takes priority over ?=

[rwhitby]

Looks good. :) At minimum, this makes the Makefile flexible enough to be used for other projects. Can you change its first line from

PROJECT_NAME = blinky

to

PROJECT_NAME ?= blinky

That way, the project name can be set when calling make.

Done

[rwhitby]

See #33 for how this can be done in the same repo.