Skip to content
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

Allow multiple extensions for assembly file types #947

Open
cosmikwolf opened this issue Oct 29, 2024 · 2 comments
Open

Allow multiple extensions for assembly file types #947

cosmikwolf opened this issue Oct 29, 2024 · 2 comments

Comments

@cosmikwolf
Copy link

cosmikwolf commented Oct 29, 2024

🍍
Some libraries sometimes have .s and .S files that come together (like threadx for example), and it looks like the function find_build_input_file strips the extension from the file name, and then tries to re-add using the :extension: selection. It appears that there is not support for multiple extensions here.

I think it would make a lot of sense to allow someone to put a list of extensions for filenames like so:

:extension:
  :header: .h
  :source: .c
  :assembly:
    - .s
    - .S
    - .asm
@mkarlesky
Copy link
Member

Hi again, @cosmikwolf. Yes, this is a frequently reported limitation. We are sorry about that. Everyone suggests the same solution in the project configuration. We totally agree. Supporting multiple file extensions for a single file type and doing so in the way you've suggested is in the backlog. The difficulty is simply that Ceedling began life in a much simpler form. An intentional design constraint was supporting just a single file extension per file type. I won't go into all the details as to why. That early decision along with Ceedling's early architecture made supporting multiple file extensions quite difficult to implement. With the giant 1.0.0 release almost ready to publish, we've drastically reworked big pieces of internal architecture. With those changes, adding support for multiple file extensions will be quite a bit easier in enhancements to Ceedling after 1.0.0.

@mkarlesky mkarlesky pinned this issue Oct 30, 2024
@mkarlesky
Copy link
Member

mkarlesky commented Oct 30, 2024

Related: #294 #765 #617

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants