Opened 11 years ago
Last modified 10 years ago
#10874 new bug
Not all non-packaged directories are created by default
Reported by: | waddlesplash | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Build System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Example: /system/non-packaged/bin/x86
does not exist on an
"x86gcc2h" system. It can be created with make
and then it works fine, but it should be there automatically. In fact, most hybrid directories are missing. Same goes for ~/config/non-packaged/
.
Change History (5)
comment:1 by , 11 years ago
comment:3 by , 10 years ago
Milestone: | R1 → R1/alpha5 |
---|
comment:4 by , 10 years ago
Milestone: | R1/alpha5 → R1/beta1 |
---|
comment:5 by , 10 years ago
Component: | File Systems → Build System |
---|---|
Milestone: | R1/beta1 → Unscheduled |
Owner: | changed from | to
I'm not sure how to create those, it should probably happen in build/jam/images/definitions/common-tail but we need to detect that a secondary arch is being used, and which is it. I'm not sure how to get that information from the ArchitectureRules.
Note:
See TracTickets
for help on using tickets.
The bin one isn't really needed, putting the binaries in the bin/ folder will work just as well. We added the dir to the packaged side only to allow installing gcc2 and gcc4 versions of the same binary side by side.
We still need them for lib and add-ons, however. Are these also missing?