C:\code\zget>zget
Welcome to ZGet v4.2
Found GCC in "c:\MinGW". checking for validity...
Found ZSNES MinGW compiler in "c:\MinGW\" !!
Would you like to be able to make DOS builds of ZSNES? (y/N): n
Update ZSNES source? (y/N): y
Update to a particular revision? (y/N): n
At revision 4569.
Download/Update ZSNES documentation? (y/N): n
Create/Update changelog.txt? (y/N): n
Compile for you? (y/N): y
Clean out object files from previous ZSNES builds first? (y/N): y
Note: Answering yes to the following question can make the compile
process take an hour (1 GHz CPU) or more depending on your PC.
Use release grade optimization? (y/N): n
Optimize ZSNES build for your CPU's architecture? (y/N): y
CPU Architecture detected as: "athlon-xp"
g++ -O3 -s -o parsegen.exe parsegen.cpp -lz
gcc -O3 -march=athlon-xp -ffast-math -fomit-frame-pointer -fno-unroll-loops -Wall -Wno-unused -I. -D__WIN32__ -o chips/dsp1emu.obj -c chips/dsp1emu.c
nasm -O1 -f win32 -D__WIN32__ -o chips/fxemu2.obj chips/fxemu2.asm
objfix chips/fxemu2.obj
nasm -O1 -f win32 -D__WIN32__ -o chips/sfxproc.obj chips/sfxproc.asm
objfix chips/sfxproc.obj
nasm -O1 -f win32 -D__WIN32__ -o chips/fxemu2b.obj chips/fxemu2b.asm objfix chips/fxemu2b.obj
etc....
So, anyone know why it works fine when called from zget but not manually? I have tried reinstalling the MinGW several times, tested a couple different versions of g++, nothing, it all crashes when using manual commands, and it all works using zget... oh and yes, i made sure the darn thing is in my path. Anyway, any insight would help a lot, thanks
Last edited by EmuGuru on Sun Feb 04, 2007 2:58 am, edited 1 time in total.
Deathlike2 wrote:It's simple, you need to set the proper path for MinGW. (eg. C:\MinGW\bin)
bah! it's there, perfect and all, otherwise, g++ wouldn't throw me an error about installation, it would simply say "command or file not found" for make and g++. that was my first thought too, this is driving me nuts!
Well, that does make some sense, I've had other "path" dependent apps fail because of long paths, so I fixed that issue, and inadvertantly removed the ati shit, been meaning to for a while, anyway, then i get this.... what is so strange is that it works fine inside of zget, which should be calling the exact same line as me.... weird. in linux I know there is a .conf file that can be checked to make sure that cc1plus is in the internal path of MinGW, but i don't know about the win32 port of MinGW.
As do I, using the ZGet's bundle for MinGW is much simpler to me than setting it all up myself. When in Linux, I like actually setting the stuff up properly, but in Windows, I don't particularly like messing with it. At any rate, I am currently using ZGet to re-get the MinGW bundle, I will test again, and I like that .bat file ^_^ I was using one very similar to that one... till this morning grrrrr lol
edit::
Ok, I re downloaded and installed the mingw bundle using zget, still, it compiles fine in zget, not manually though, i'm gonna be ticked if it's something really simple lol
allows zsnes to compile just fine it seems (well other than the fact that right now, the dsp code is getting worked on). Still, it seems to me that this is a cheating way to make it work, since the libexec should be found by g++ to begin with, anyone know if there is a config file in the win32 version of MinGW that sets this variable? or is it hardcoded into the .exe's?
Last edited by EmuGuru on Sun Feb 04, 2007 5:49 pm, edited 1 time in total.
Update: fyi for anyone who cares, the mentioned path above is working like a charm. I am compiling like normal now with both the paths set, weird. anyway thanks for the time and info guys.
EmuGuru wrote:Here's something interesting, I might have fixed the problem temporarily, but still not permanently. changing the path from
C:\MinGW\bin;C:\MinGW\libexec\gcc\mingw32\3.4.5;
to
C:\MinGW\bin;C:\MinGW\libexec\gcc\mingw32\3.4.5;
allows zsnes to compile just fine it seems (well other than the fact that right now, the dsp code is getting worked on). Still, it seems to me that this is a cheating way to make it work, since the libexec should be found by g++ to begin with, anyone know if there is a config file in the win32 version of MinGW that sets this variable? or is it hardcoded into the .exe's?
so changing it to what it already was fixed it? theres no difference at all between the 2.
Core i7 920 @ 2.66GHZ | ASUS P6T Motherboard | 8GB DDR3 1600 RAM | Gigabyte Geforce 760 4GB | Windows 10 Pro x64