Getting started with SMS development

[JuddMan]

check out my latest guide:
http://www.adam.com.au/kellyjones/sms/docs/

this sums up how to do in 10 - 30 minutes what i have been trying to figure out on my own (in spare time) for about 4 days.

it will take you from vanilla XP box to a compiled SMS.ELF fresh from the SVN source.

the rest is up to you.

[suloku]

[UPDATE]

EDIT: nevermind, I don't know why but I had a cygwin1.dll in windows\sistem directory, now all works. (dammit, this drove me mad some time ago and didn't find a solution)

I could compile SMS with no problems, now for ule!


I'm having problems when compiling...

"This problem is probably due to using incompatible versions of the cygwin DLL. Search for cygwin1.dll using the Windows Start->Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL."

Can't figure out how to solve this, I already removed cygwin from my system (couldn't instal ps2toolchain in there anyways)

[/UPDATE]

Thanks, maybe with that I'll be able to set a fully working environment under windows.

I mean an environment that ca compile both ule and sms, because my actual environment under linux is a little messed up.

[JuddMan]

ule needs a modified toolchain, and the modifications need the toolchain to be recompiled. as the toolchain provided with that installer is only the binary, it won't be possible to recompile to add the ulaunchelf specific changes.

and whether SMS will build correctly with those changes, i don't know.

[dlanor]

ule needs a modified toolchain, and the modifications need the toolchain to be recompiled. as the toolchain provided with that installer is only the binary, it won't be possible to recompile to add the ulaunchelf specific changes.

Excuse me, but I'm not aware of any uLE-specific changes to the toolchain. We do have several patches for embedded subprograms (like ps2ftpd) and various libs, such as PS2SDK, gsKit and libjpg etc, but none at all for the toolchain itself.

A fully working binary-only installation of the toolchain should be capable of recompiling any normal program or lib (including PS2SDK). If that doesn't work, then the installation is either not fully working, or incorrectly used.

and whether SMS will build correctly with those changes, i don't know.

I can build a working SMS ELF with the same setup used to develop uLE.

Best regards: dlanor

[JuddMan]

Sorry. I thought those things were part of the toolchain.
Anyhow, i should have just said I havent figured out how to integrate the modifications that come with ULE source into that particular installation.

[dlanor]

Sorry. I thought those things were part of the toolchain.

Well, as I see it the 'toolchain' is the basic setup of compilers and other tools that allow us to compile programs at all, by the standard PS2Dev methods. In addition to those basic tools we also need various configuration files and libs, but very few of those can be considered integral parts of the toolchain. PS2SDK in particular is a great example of something we need for virtually all PS2 programming, but which is definitely NOT a part of the basic toolchain. (If it were, then the toolchain would be unable to compile PS2SDK from scratch without having a previous version. But doing so works just fine.)

Anyhow, i should have just said I havent figured out how to integrate the modifications that come with ULE source into that particular installation.

It's not at all hard really. So I'll describe it again here.

You're already aware of the folder named "Changed source for external projects" in each uLE release. That folder contains one subfolder for each lib or unrelated project that uLE needs to have modified for perfect functionality.

If you inspect these subfolders you will find a seemingly redundant amount of additional subfolder levels, in many cases with just one or two files residing at the deepest level. This usage is NOT redundant however, as it is necessary to mimic the folder structure of the original lib sources, in order to ensure that those files end up at the correct destination when updating the libs.

For most of those cases (excepting only ps2client), this means that you need to copy all the contents of such a subfolder into the main source folder of that lib project, allowing all files at all folder levels involved to overwrite their old counterparts in that lib source directory. After which you should recompile that lib project. Note also that for some projects it is not enough just to use "make all", as both gsKit and PS2SDK also need a "make release" after the main compilation.

For ps2client similar procedures should be used, except that it should be compiled so as to run on a PC, obviously, for which I prefer to use MinGW rather than Cygwin or other compilers, but that's up to you. However, since I've only tested the ps2client changes with MinGW I'm not sure if other compilers, 'like the flavour'

Best regards: dlanor