-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Allow to control the order of the source files. #452
Comments
Could it be possible to allow more complex project structure? not only file ordering. There is an open request #227 to allow using several subdirectories. In my project I have For example in
Or if required to control the order of files
Then when apio is searching for the source and test files. It can check that properties. If they are not specify it should default to the current directory as it's doing now. And if specify it could check if there are files or directories and build from there. I have modify the bellow function to, for now, hardcode some values. I can run
|
Thanks @fmodesto, this is a very good idea. Generally speaking we follow platformio conventions and it does support separate src/lib/test directories and nest directories. In the next release we plan to have these initial steps:
Once apio.ini will be mandatory, we will be in a better place to add project options. |
Moved from #176 (comment)
"I also find this request useful. It would be also nice if there is a way to specify the source files order. The current order seems to be alphabetical, which may not work in some cases. An example is building picosoc. One needs to list picosoc.v before picorv32.v so one cannot use apio build as is. The current workarounds are using Makefile or using apio raw or modifying SConstruct script or renaming the original files. Maybe having a possibility to have an ordered list of all sources in a config file could be beneficial. If the ordered list of sources is missing then existing alphabetical order of all sources could work."
The text was updated successfully, but these errors were encountered: