# Managing scattered codebase

**URL:** <https://discourse.myhdl.org/t/managing-scattered-codebase/568>\
**Category:** Support\
**Created:** [September 30, 2024, 4:12pm UTC](https://discourse.myhdl.org/t/managing-scattered-codebase/568 "2024-09-30T16:12:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vpascucci](https://avatars.discourse-cdn.com/v4/letter/v/b77776/32.png) [@vpascucci](https://discourse.myhdl.org/u/vpascucci)\
**Post date:** [September 30, 2024, 4:12pm UTC](https://discourse.myhdl.org/t/managing-scattered-codebase/568/1 "2024-09-30T16:12:25Z")

</div>

Hello,

I am trying to figure out a lean workflow with myhdl. My first instinct is to try and replicate my VHDL workflow. There I have my codebase scattered around several repositories, which are then included as needed in a new project. So my sources are divided in many different folders and subfolders, each with their own tests. All files are included in my testing and synthesis projects with a relative path from the project folder/file.

In myHDL I would replicate this by having all the various myhdl sources import other modules by name, and then have one or more “top-level” python scripts that add all the necessary folders to PYTHONPATH, and then run the conversion, test and/or cosimulation.

Is this a “normal” workflow? does anyone have suggestions on how to keep code and tests portable and reusable?
