Might as well just go with cygwin then if that's your logic, ha ha
I love Linux though any excuse
As nice as that is, it's only the installer process, not the installer package. That installer can't talk to the SourceForge servers to download the rest of its resources right now, so it's useless until they come back online. Thanks for trying though.
What are you talking about? Did you even open it? It's a zip file. Of my already installed (and in my path, and working) gnuwin32 Make. In fact, it's the whole damn thing. All you need, really, are the 3 files in the gnuwin32/bin folder.
My bad, it looked about the same size as the installer, which has no resources, so I assumed it was.
No no, make release just dies from the themes. I don't care about the rest of it for now though, I just need the rxTools.dat. I'll figure it out later.
well, ok, but you shouldn't have to place convert.exe anywhere, as long as after your path cleanup C:\Program Files\ImageMagick-6.9.1-Q16 is still in your path. It can go after the other mingw and devkit stuff.
Yeah, that'll be ideal once I finish debugging my modified MSET downgrader, but for now, I only need the rxTools.dat, ha ha. I'm honestly not sure why I'm getting the "Invalid Parameter - 90" error though on make release, I guess it's just gonna be stupid for me, w/e
No offense, but I don't see what the big deal is with the mset downgraders. All anybody needs to do is download the version they want with 3dnus and install it with the latest version of FBI. Or using an old version of FBI, delete the current one first, then install the old one. Done.
It's not meant as a necessity, and to you and me, sure, it's no big deal to do it manually. It's a user experience feature though, and it'll help the noobs that have no idea what to look for. Plus, it's something I CAN do, so if I can contribute with it, I figure might as well, ha ha.
That's because I didn't show it all.
But then you need to include where to put the gnuwin32 make.exe (not in your path so you dropped it into the mingw/bin folder or in your rxtools folder...)That's because I didn't show it all.
Here's my path that makes everything work (Make, Make release and Make theme on the latest v3.0-Alpha0):
c:\MinGW\bin;c:\devkitPro\msys\bin;c:\devkitPro\devkitARM\bin;C:\Program Files\ImageMagick;C:\ProgramData\Oracle\Java\javapath;C:\Python27\; ... ; C:\Program Files (x86)\Git\cmd
Disregard "C:\ProgramData\Oracle\Java\javapath;" and "; ... ; " as they aren't needed here.
You really only need one Python dir ("C:\Python27\;" in my case)
I'm at work so I can't look at it, but I had a similar problem with all the other tools before I had my path in the correct order. If you could build without problems before, just look in tools/toolsrc for a font tool folder or something. If there is a make file in there, build it from there with make, and move the .exe to /tools. If only a .c file is there, then copy and modify a build.bat from one of the other toolsrc folders...So can this be updated, so we can compile it again?
Latest github version (23/07/2015)
That's why I said to grab a build.bat from a different tool and modify it. There is one in toolsrc\addxor_tool. If you can't look at the .bat file and figure it out, you have no business trying this anyway. Just grab the latest build from github.
