Black Goku Yes, just edit the defines that would point to JSL !SharedSubroutineDefines to instead a label that would point to its code (a subroutine within the sprite code ASM) or Pixi's routines folder (must be %SubroutineFilenameFromRoutinesFolder()). And then move (cut/copy, then paste) the code to its code or in the routines folder.
I prefer the shared subroutines patch because it makes it accessible on any ASM resource (like have a bar for the HUD and as a sprite) than just uberasm tool or pixi. Another reason is that you cannot call a subroutine within another, separate subroutine file in a daisy chain -like fashion:
Originally posted by uberasm tool - readme.txt
The second one is that you can't call other libraries codes from a
library file. For example, if you have a windowing HDMA code and you
need to call a sqrt routine, which is located on the math library, you
can't do that, because UberASM Tool can't guess what labels each file
will generate nor what labels each library .asm file will depend from
each other. So unfortunately the library files are pretty much
isolated from each one.