3.21 is the version I am using of HuC (downloaded the one you sent me with similar concerns)
I got both from zophar.net
OK, thanks!
If you're starting from new, I'd really recommend using the new version of HuC that's discussed in the forum thread here, it has a lot of improvements.
You don't need that old version of Magic Kit, and can delete it, HuC already includes a much newer version of it.
The concern is when I try to even launch the compiler (HuC or Magic kit) it doesnt launch. With HuC it simply opens and closes before I can type anything (so I tried dragging the .C file to it and it creats assembly files). Magic Kit says "The version of this file is not compatible with the version of Windows you're running."
That old version of Magic Kit won't run because it's a 16-bit executable that won't run under Windows 7.
HuC includes a 32-bit version that will run under Windows 7, but ... you seem to be expecting that HuC (and PCEAS) will act like a windowed application or an IDE (like Visual Studio).
They don't. They are command-line applications, just like the GCC compilers on Linux (and most traditional compilers).
Generally, to use the compiler, you open up a Command Prompt, navigate to the correct directory, and then type "huc whatever-your-file-is.c".
Was not advised I would need to setup a windows path before launching HuC.
The other files with my .C file are HuC, Isolink, Nesasm, pceas, pcxtool.
OK, if your .c file is in the same directory as the HuC executables, then you won't need to set up a PATH.
That's not good long-term, but you can work like that for a short while, until you're more familiar with the whole command-line environment.
The PCE_Include, is that in the program file or in a separate file? (like setting file for HuC)
And this is why your compile is failing. An error message is being printed in that box that flashes up, but you can't see it because the window closes too fast.
That's why people open up a command prompt ... it stays open, and you can see the error message.
You need to set up the PCE_INCLUDE enviroment variable so that HuC knows where to find all the include files and libraries that it needs to compile your C file.
Am I missing something?
Yep ... lots about how traditional development environments work.
But it's not your fault, it's that there is a real lack of decent HuC documentation.
You might want to take a look here ...
http://obeybrew.com/tutorials.htmlAnd here ...
http://www.archaicpixels.com/HuC_SetupAnd I should add something to HuC to do a simple drag-n-drop-build for people that aren't comfortable with batch files and makefiles.