forums.ps2dev.org

[dlanor]

I'd like both a general answer and a specific one to some issues raised in the subject line.

I'll start with the specific case:
uLaunchELF normally uses the current PS2SDK version of usbd.irx for its access to mass: (with a slightly modified usb_mass.irx), while also allowing the loading of external USBD.IRX files, though finding such is of course left to each user (for the usual legal reasons). Lately several users have asked for the PS2SDK usbd.irx as a separate file, so they can use it with other homebrews too, that don't have any internal driver. But since PS2SDK isn't distributed in binary form, but only as source, I'm not sure how to do it properly. Is it even allowed, and if so, exactly what files must I then include with the IRX binary ? Is it enough just to add some AFL text file, or what ?

I'd also like to know the general policy on sharing already compiled PS2SDK binary releases, with 'newbie' programmers who find this stuff a little daunting... That too is a subject which has come up on several occasions. Fortunately those guys were finally able to compile it on their own, but I know that others may need more help to get started. So, are we allowed to share the binary distribution ?

By this I mean the entire 'PS2DEV/PS2SDK/' folder in the state it has when freshly compiled and after completing "make release". As I see it, that should be a form valid for release as-is, but I'd like to have that officially confirmed.

Best regards: dlanor

[ooPo]

I can't speak for everyone, but it seems that there are already projects distributing precompiled parts of the ps2sdk with their programs. I can't imagine there would be any problems with you or anyone else doing the same.

Making sure you credit where you received the code from would probably smooth over any future objections if any were to arise, too.

As for legal responsibilities, there is a license file included with the ps2sdk source. You should be able to read that to get an idea of what you can and can not do.

[dlanor]