Update on SSSDK

so who uses this toolchain except me ?
I do, I forked your github repo and created branches for each GCC versions supported : Branches · willll/Saturn-SDK-GCC-SH2
The latest version is 13.2.0 :

/opt/saturn/toolchain/bin/sh-elf-gcc -v
Using built-in specs.
COLLECT_GCC=/opt/saturn/toolchain/bin/sh-elf-gcc
COLLECT_LTO_WRAPPER=/opt/saturn/toolchain/libexec/gcc/sh-elf/13.2.0/lto-wrapper
Target: sh-elf
Configured with: ../../source/gcc-13.2.0/configure --build=i686-pc-linux-gnu --target=sh-elf --host=i686-pc-linux-gnu --prefix=/opt/saturn/toolchain --enable-languages=c,c++,lto --disable-bootstrap --with-gnu-as --with-gnu-ld --disable-shared --disable-threads --disable-multilib --disable-libmudflap --enable-libssp --enable-lto --disable-install-libiberty --disable-nls --with-newlib --enable-offload-target=sh-elf --enable-decimal-float=no --program-prefix=sh-elf- --with-cpu=m2 --with-sysroot=/opt/saturn/toolchain/sysroot
Thread model: single
Supported LTO compression algorithms: zlib
 
so who uses this toolchain except me ?
Hi, I have to decide between jo-engine and sssdk. Jo-Engine seems to be sorted out and in big quotes "production ready", but I don't really know? So the elephant in the room for me is which engines is more performant while keeping the technical side of this old console away from me. Not that I don't like to dive into architecture but I want to stage a multi platform launch so I would appreciate a little abstraction of the hardware. Jo-Engine has an abstraction which I would call sufficient. Not that I really want to use Jo-Engine but I would rather like to see what the competition has to offer? So if you could link me some details to the sdk, I would appreciate it. Best regards pizza_dox_9999
 
Hi, I have to decide between jo-engine and sssdk. Jo-Engine seems to be sorted out and in big quotes "production ready", but I don't really know? So the elephant in the room for me is which engines is more performant while keeping the technical side of this old console away from me. Not that I don't like to dive into architecture but I want to stage a multi platform launch so I would appreciate a little abstraction of the hardware. Jo-Engine has an abstraction which I would call sufficient. Not that I really want to use Jo-Engine but I would rather like to see what the competition has to offer? So if you could link me some details to the sdk, I would appreciate it. Best regards pizza_dox_9999

For what you describe you probably want Jo-Engine for the abstraction it offers, I believe most consider it easier like your understanding of it. I don't have a link off-hand to an in-depth description of SSSDK, but you could always look at the sames to get an idea:

 
For what you describe you probably want Jo-Engine for the abstraction it offers, I believe most consider it easier like your understanding of it. I don't have a link off-hand to an in-depth description of SSSDK, but you could always look at the sames to get an idea:

Thank you very much for the answer. I will take your advise and stick with Jo-Engine. Best regards pizza_dox_9999
 
Back
Top