Hacking Trying to Compile Luma Nightlies

[Dracari]

i see starting w/ 7.1 it needs firmtool as part of its progress, it gets most of teh way done then

make: firmtool: Command not found
make: *** [out/boot.firm] Error 127
c:\Users\xiond\Downloads\Work\Luma3DS>

i allready ran "python setup.py install" so should be installed and in path.
here's how my path looks like.

 

[Joom]

And where did it install to? I have no idea how installing Python scripts works on Windows. At the very least you could just put firmtool in the working directory.

Also, since we're on the subject, could someone see if this works for them? I just updated my build environment for the new Luma release scheme, but I haven't updated my 3DS to B9S yet, so I have no idea if what I compile works or not, especially since I'm getting a sed error at the beginning of the build. Below is the latest commit.

Edit: Turns out OS X's sed is just dumb. Fixed it by installing gnu-sed with Homebrew and editing the Makefile to use gsed. Note to all of you compiling on OS X.

 

[Dracari]

And where did it install to? I have no idea how installing Python scripts works on Windows. At the very least you could just put firmtool in the working directory.

Also, since we're on the subject, could someone see if this works for them? I just updated my build environment for the new Luma release scheme, but I haven't updated my 3DS to B9S yet, so I have no idea if what I compile works or not, especially since I'm getting a sed error at the beginning of the build. Below is the latest commit.

Edit: Turns out OS X's sed is just dumb. Fixed it by installing gnu-sed with Homebrew and editing the Makefile to use gsed. Note to all of you compiling on OS X.

On Windows C:\python27\Scripts

 

[Joom]

On Windows C:\python27\Scripts

Are you able to use it normally from CMD?

 

[Dracari]

Are you able to use it normally from CMD?

yept but when its calle dby the makefile it acts as it isnt there.
ok i added it to C:\devkitPro\devkitARM\bin now it seems it .

 

[Joom]

yept but when its calle dby the makefile it acts as it isnt there.

Are you compiling it with cygwin or something? Does your bashrc have your PATH variables set properly? Also, have you tried just putting the script in the working directory (the same directory as the makefile)?

 

[Dracari]

Are you compiling it with cygwin or something? Does your bashrc have your PATH variables set properly? Also, have you tried just putting the script in the working directory (the same directory as the makefile)?

re read above , and no just a basic setup from when it was AuReiNand and didnt require cygwin, just python required libs and the command line window.

 

[Joom]

re read above , and no just a basic setup from when it was AuReiNand and didnt require cygwin, just python required libs and the command line window.

It'd be a lot better and simpler to build it with cygwin, but meh.

 

[Ryccardo]

Why not just use the Msys2 shell included with devkitpro, and putting all tools (3dstool, makerom, firmtool etc) in devkitpro\msys\bin\ ?