1. apxmachit

    OP apxmachit Member
    Newcomer

    Joined:
    Jul 22, 2020
    Messages:
    11
    Country:
    United States
    I have been trying to get the toolchain working for a while now.

    The first method I used was WSL. It produced corrupted ELF files which when converted to RPX (through elf2rpl on command line) shows an error on the Wii U.

    After trying to look at the toolchain to figure out what's wrong to no avail I instead tried to go with the Msys2 route. It installed fine, downloaded the wiiu-dev packages and cmake. However I could not use commands such as elf2rpl, powerpc-eabi-gcc etc (this all worked on WSL). I did check if they were downloaded and they were. Also when compiling samples it failed since it couldn't find the header source files. They were also downloaded.

    At this point I'm not sure what to do. I have Windows 10 post-anniversary update with the latest versions of everything. Any help would be appreciated.
     
  2. godreborn

    godreborn GBAtemp Legend
    Member

    Joined:
    Oct 10, 2009
    Messages:
    18,852
    Country:
    United States
  3. neoninteger

    neoninteger Member
    Newcomer

    Joined:
    Apr 22, 2020
    Messages:
    22
    Country:
    Australia
    It's been a while since I last tried building stuff on Windows, but I think what's missing is that you haven't set the system's PATH variable to include the directories for devkitPro tools.

    I know that the Linux versions (including WSL) include shell profile scripts which automatically run when you open a shell like bash, and set the PATH variable for that shell accordingly. But I don't remember if something like that is possible to automate under MSYS, and so you may need to manually set the PATH variable accordingly. None of dkP's instructions appear to mention this, so it's just a wild guess based on past experience.

    Somewhere in Settings or Control Panel, you should be able to find an Environment Variables page, which should show you what the PATH variable is set to. It is a semicolon-separated list of folders which the command prompt will look in to find programs. If it doesn't contain "C:\devkitPro\devkitPPC\bin" and "C:\devkitPro\tools\bin" (or whatever the paths are supposed to be), try adding them in, restarting your command prompt and seeing what happens.

    Just out of curiosity, what are you actually trying to build? In most cases, calling the compiler and elf2rpl commands manually shouldn't be necessary, as there is usually a CMake script or Makefile that handles building the project. If you're building your own project, the ELF corruption may be due to missing linker scripts?
     
  4. apxmachit

    OP apxmachit Member
    Newcomer

    Joined:
    Jul 22, 2020
    Messages:
    11
    Country:
    United States
    This seems useful but I’m trying to compile C or C++ apps to RPX not mess with the ARM right now.

    I checked my environment variables and I had all of them from the tutorial and the ones you listed. I also had added WUT_ROOT and its bin. I tried exporting the environment variables in the shell directly but that also didn’t work.

    I am trying to build a hello world file from the wut examples. When I called make with WSL it generated an ELF but failed at making an RPX. I manually made one with elf2rpl. Regardless they were both corrupted. When I called make with Msys2 it couldn’t find the linker source files.
     
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - [devkitPro, commands, compile