You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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")
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.
The text was updated successfully, but these errors were encountered: