Add o segment type

[mkst]

If there's a way to do this already im all ears.. but this is more granular than using the lib segment (and I am struggling to link against libultra.a in a piecemeal fashion, so just wanted to cherry-pick individual objects from it)

[emoose]

fyi in SH there was some issue with this line:
out_path = options.opts.build_path / f"{self.name}"
for [0x1234, o, lib/libthing/obj] that would output build/src/lib/libthing/obj.o in the ld, but some reason even using [0x1234, o, ../../lib/libthing/obj] would still result in build/src/lib/libthing too, not really sure why the ../ got ignored.

In your o.py extension I changed to out_path = Path(f"{self.name}"), and that let the ../../ start to work (though not really sure why that ../../ was still needed for it?)

(also when we were using [0x1234, lib, lib/libthing, obj], that was able to pull from our repo root instead of using build/src/ folders, maybe something can be copied from the lib segment handler?)

[mkst]

For the lib segment there is an explicit splat setting for the lib directory (rather than using the build_dir).

You can do a simple cp in your makefile to move objects into the build directory... I think it's more correct that these .o files are expected to be "built"

[emoose]

Ah right, guess for us lib_dir had just defaulted to repo root then.

I think it's more correct that these .o files are expected to be "built"

Makes sense, I don't mind adding a copy to the build dir for it, was just a bit surprised that using ../ wasn't seeming to have any affect at all, can't really see what would even be stopping that, odd.

[ethteck]

could you bump the version (there's 3 places, you can find/replace it) and add to the changelog?

[AngheloAlf]

I don't think recommending auto for this segment type would be a great idea, because it could mess up the size calculation of the previous subsegment. This can be problematic if people wants to disassemble the previous subsegment while linking this object.

[AngheloAlf]

This introduces a new feature so this should be bumped to 0.39.0 instead of just a patch bump

[AngheloAlf]

It would be nice to mention that this segment can only be used as a subsegment and not as a top-level segment.

Also, where is the object expected to be? In the build folder? Relative to the src, asm, lib, etc folder?
Maybe we should introduce a new setting for this? Something like o_path