jaynuine/weegie
1
0
Fork 0
Code Issues 10 Pull requests Projects 1 Releases Wiki Activity

subs & deps distinction #13

New issue
Open
opened 2026-05-23 03:55:34 +00:00 by jaynuine · 2 comments
jaynuine commented 2026-05-23 03:55:34 +00:00
Owner
Copy link

inclusion direction

subs point inwards, they depend on the unit referencing them, whereas deps point outwards, and the current node requires the units they mention as parts of itself, which means it should aggregate the variable instances of each dep recursively such as UNITS for final compilation

inclusion direction subs point inwards, they depend on the unit referencing them, whereas deps point outwards, and the current node requires the units they mention as parts of itself, which means it should aggregate the variable instances of each dep recursively such as UNITS for final compilation
jaynuine commented 2026-06-18 00:00:33 +00:00
Author
Owner
Copy link

rather than passing variables such as units upwards, one may partially link all objects produced at a stage of the tree using ld -r and append that filepath to the root makefile's units

rather than passing variables such as units upwards, one may partially link all objects produced at a stage of the tree using `ld -r` and append that filepath to the root makefile's units
jaynuine commented 2026-06-18 14:42:13 +00:00
Author
Owner
Copy link

to prevent filename collision perhaps the resulting unified object should be named after the invoked makefile ?
so Makefile -> Makefile.o, node.mk -> node.mk.o
we wouldn't want to risk there already existing a node.o file which would cause relinking issues as different stages of the build process alternate in overwriting the same file, and this clearly conveys that this "belongs" to the similarly named makefile, and that it is not a regular object file

to prevent filename collision perhaps the resulting unified object should be named after the invoked makefile ? so `Makefile` -> `Makefile.o`, `node.mk` -> `node.mk.o` we wouldn't want to risk there already existing a `node.o` file which would cause relinking issues as different stages of the build process alternate in overwriting the same file, and this clearly conveys that this "belongs" to the similarly named makefile, and that it is not a regular object file
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaynuine/weegie#13
No description provided.