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

Detect overlap between Dylan and C-Source files in a project #1581

Open
housel opened this issue Apr 26, 2024 · 2 comments
Open

Detect overlap between Dylan and C-Source files in a project #1581

housel opened this issue Apr 26, 2024 · 2 comments

Comments

@housel
Copy link
Member

housel commented Apr 26, 2024

Since project builds will use the basename of both Dylan and C source filenames to determine the object file name in the build output, the project-manager should detect duplicated basenames across the Files and C-Source-Files in a project and reject projects that contain a conflict.

@cgay
Copy link
Member

cgay commented Apr 26, 2024

It feels pretty natural to me to use both foo.dylan and foo.c in a project. What about adding some uniquifier to the .o file corresponding to the Dylan source file?

(This makes me wonder... why does OD only sometimes do that? For example, "10=locators.o" but "strings.o")

@waywardmonkeys
Copy link
Member

Directories / subdirectories cause that, I think.

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

No branches or pull requests

3 participants