[For discussion] How should Apio handle subdirectories?

[zapta]

The goal of this is issue is to figure out the requirements for multiple directories support in Apio, and it was triggered by user requests such as this one #495

Q0: Do we want to support project subdirectories or do we want to stay with the current single directory model?

Q1: Should apio define directory types, each with its own semantic, such as such as srcs, lib, test, etc, or should it treat all subdirectories in the same way, identifying elements such as synthesized modules, testbenches, etc, similar to what it does today.

Q2: If apio will define multiple directory type semantic, what those types should be? E.g. src for synthesizeable, test for testbenches, etc.

Q3: If we will got with the approach of multiple directory types, how do you see the transition from the current 'catch-all' single directory type?

IMPORTANT Please be aware that this issue is NOT about 'the best' project structure but what range of project structures apio should support.

@Obijuan, @cavearr, what do you think?

---

EDIT: Related documents from the internet

• https://www.ece.ucdavis.edu/~bbaas/180/tutorials/file.organization.html

[cavearr]

Hi @zapta! i'm resply you later or tomorrow with a meditated response.

I'm implementing in Icestudio the support for multiple directory structure and could be good joining the same criteria.

How do you think if we use "Discussions" instead of issues for this kind of things? i think could be better distinguish the objetive of the content , issues for bugs, development stuff an discussions for "discussiones" :) (this is a suggest)