devkitPro

binutils updated to 2.44
gcc updated to 15.1.0
newlib updated to 4.5.0

Recommended and supported installation for all our releases is via devkitPro pacman

After some discussion with RTEMS we have agreed to resolve this matter by including the necessary licensing and copyright notice from RTEMS for the derivative code. See https://github.com/devkitPro/libogc/pull/210

Register FAT driver statically instead of on first call to fatInit

Recommended and supported installation for all our releases is via devkitPro pacman

I think you probably updated while we were still rolling some releases and hadn't yet rolled a new libctru. Everything should be working now assuming you have all the latest updates. sudo dkp-pacman -Syu to make sure.

It's difficult to know how to deal with this one. As far as I know currently Apple are not at all keen on 3rd party installers so the likelihood of getting this package signed seems somewhat low. We do have instructions to install the package from a terminal using sudo installer -pkg /path/to ...

Don't redefine the DEVKITPRO & DEVKITARM variables when compiling. These should be set in your environment already.

Run the following command to ensure your devkit install is up to date and all required components are installed.

Code: Select all

sudo dkp-pacman -S nds-dev --needed

As many of you will by now be aware there is some drama around the licensing of some historical code contained within libogc. When accusations some time ago were made that RTEMS code had been "stolen" by Shagkur and added to libogc without attribution or licensing no evidence was provided to us ...

You have extra repositories in your pacman.conf. Reduce these to just core, extra, dkp-libs and dkp-linux. I'm not really sure what the first two are so double check that those were already in your system installed pacman.conf

# An example of a custom package repository. See the pacman manpage for ...

It was a minor packaging hiccup, sorry. The package signing failed and the release process missed the error which then resulted in no signature file being uploaded. Apologies for the inconvenience.

/opt/devkitpro is not user writable. If you want to compile the examples copy them somewhere that's writable.

devkitPro

Search found 2057 matches

devkitPPC release 47

Re: libogc license controversy

libfat-nds 2.0.1

Re: Arm11 Exception when running homebrew that uses romfs files.

Re: macOS .pkg installer signing broken

Re: Cannot compile Examples

libogc license controversy

Re: cant install 3ds-dev with pacman on fedora

Re: cannot install libctru

Re: Cannot compile Examples