[Feature Request] Support multiple build env variations.

[cavearr]

@zapta, @Obijuan this is a suggestion for improve tha Apio ini file:

Add the ability in Apio.ini of add defines to use into verilog files.

For example:

[env]
board = Sipeed-Tang-Nano-1k
top-module = main
defines =
-KEY1=VALUE1
-KEY2=VALUE2

This defines will be passed as yosys argument with -D option.

In other hand could be interesting the capability of passing defines in build command as argument for example:

apio build --defines KEY1=VALUE1,KEY2=VALUE2

In other way we could define multiple target boards to use the same file for multiple targets, for example:

[env]
board = Sipeed-Tang-Nano-1k
top-module = main

[env:Alhambra-ii]
defines =
-myBoard=ALHAMBRA

[env:Fomu]
defines =
-myBoard=FOMU
-LED=RGB

We could do :

apio build => This only will apply env block

or

apio buils --env Fomu. => This will apply env + env:Fomu blocks

[JohannesSchramm]

I like the proposed ideas, it is similar to the ini file from platformio, which i use quite a lot.

I would also like to see a testbench argument that could be used instead of the --testbench option on the command line.

E.g.

testbench = top_tb.v

[zapta]

@cavearr, @JohannesSchramm, these are very good ideas and in the spirit of platformio. The next step is making apio.ini required and the central source of project configuration, eliminating the configuration flags such as --board and --fpga. This will make adding new project controls much more maintainable.

@cavearr, this is related to item 2 here #453. Any news related to items 2-5?

[cavearr]

Hi @zapta today or tomorrow i'm finishing icestudio integration and testing and we could remove the flags.

About the config file i could do it if you have other tasks , count with me, if we decide go in this way i'm advance in Icestudio part to have an apio.ini editor to customize the apio.ini for icestudio projects.

Let's go team!

[zapta]

Hi @cavearr, I can do it and already have a pending change for part of the works but am waiting for OK from you for items 2-5.

[zapta]

@cavearr

1. Please ignored my previous post. I was referring to a different feature.
2. Please rename this issue to [Feature Request] Support multiple build env variations.

[cavearr]

Done!