Questions, bug reports, features requests, ... about the Oric Software Development Kit. Please indicate clearly in the title the related element (OSDK for generic questions, PictConv, FilePack, XA, Euphoric, etc...) to make it easy to locate messages.

I am starting to get warmed up to code a bit on the Oric using the OSDK but since I live in a macOS world I wanted to know if there was a Linux/macOS version available which contains the recent v1.1 OSDK changes?

Searching on Duck Duck Go for "+oric osdk linux" does not return much either.

Does anyone know if Iss's Linux version is still available somewhere?
If none exist anymore, I will create one from the recent OSDK version and make it available for test somewhere before bringing it back to DBug's SVN.

Because of lack of interest I removed it from the public repository else I'm using it every day .
But there is no problem to compile and use OSDK from SVN under Linux.

What I've done is to create a makefile based solution which provides an easy way to deal with 'projects' (or kind of). Projects can contain many parts (programs build from C, assembler, basic sources, binary files, TAP's etc) and the result can be Sedoric or FloppyBuilder based image. The same makefiles can be used with OSDK and with CC65.

No, they are not, and IMHO this is not good idea. Let's keep OSDK "as is".
As I said it's easy to build OSKD for Linux - there are already Makefiles.
Checkout http://miniserve.defence-force.org/svn/public/, go to pc/tools/osdk/main/ directory and try 'make'.
May be some tweaking and 3-rd party libraries (freeimage, nanosvg, etc.) are needed,but in common it should work.
Try it and post your result, I can help if you need. .

As I said it's easy to build OSKD for Linux - there are already Makefiles.
Checkout http://miniserve.defence-force.org/svn/public/, go to pc/tools/osdk/main/ directory and try 'make'.
May be some tweaking and 3-rd party libraries (freeimage, nanosvg, etc.) are needed,but in common it should work.
Try it and post your result, I can help if you need. .

Ok, I will use that, thanks. Get ready for questions.

As discussed with DBug privately recently I will likely create a GitHub copy of the OSDK.
I have no intentions to fork it ever, this is just simpler for me to work with and it will mirror the SVN (manually first, automatically later).

I've not done anything about the osxdk except giving my benediction for the fork

I refuse to huse github / bitbucket or any hosted repository for various reasons (religious, conceptual, pernnity, etc...) in general, and I dislike git as a source control system in particular (I see the point of how it's useful for a distributed work such as the Linux Kernel, but for a simple versionning without branches with just a moderate number of changes/files and non professional developers, it's just absolutely overkill for no obvious benefits compared to SVN or even CVS).

Basically, I've no problem with anyone forking anything, it's actually good for making sure we get distributed copies, the only thing is that I keep the SVN as my own master repository.

I'm fine with giving SVN write access to serious people doing sane changes, so they can propagate their changes if they want them in the next "official" osdk