I have, I even removed Jakester's source because it contained another main.c
Vanadium:
Delete main.c and put in another one
? Elaborate, please.
antb:
treating warnings as errors depends on how anal you want to be about standards.
Considering Microsoft can't actually write error messages in English and some people on this site are expecting me to know what every one of the errors mean, I think I have received the privilege to be anal.
1. Open where your mod is on your computer, 2. Right mouse click on main.c and click delete, 3. Download a fresh source, 4. Take the main.c out of it and drop it into your mod, 5. Have a look at the errors and realise they are simple.
Considering Microsoft can't actually write error messages in English and some people on this site are expecting me to know what every one of the errors mean, I think I have received the privilege to be anal
Those warnings are verbose enough to tell you exactly what the problem is. Like I said, if you want to trawl through the source and get a completely clean compilation your welcome to. Otherwise if it doesn't say error, its not an error.
Warning != Error
Again, Warnings have no effect on the program compiling.
1. Open where your mod is on your computer, 2. Right mouse click on main.c and click delete, 3. Download a fresh source, 4. Take the main.c out of it and drop it into your mod, 5. Have a look at the errors and realise they are simple.
1. Do what you say, remove main.c and replace it 2. Get the same errors 3. Look at main.c and find absolutely nothing wrong, since there's 50 lines that contain "0x5" antb So English is 1>._main.c(1): error C2143: syntax error : missing '{' before 'constant'? I still haven't received anyone who can actually tell me what these mean in English, and to me that says that it isn't telling me exactly what the problem is.
I am bumping this up to avoid making a lot of topics. It is of the same topic. I fixed most errors in the source that involved undeclared identifiers (the source had left out "int" before a lot of lines in powder.h) but there are a few problems in powder.c: http://pastebin.com/duMBr96e The errors involving the sprk file also appear in the other element files. However I'm a bit nervous to remove them. The ones in powder.c are my main concern at the moment, if people can focus on that it''d be appreciated. If you need to see the powder.c file it is here: http://pastebin.com/90ZP8ABY Any warnings in those are accidental and not important.
these were all fixed in irc, like 5 minutes before you got there, just wait for an updated version, it is visual studio being retarded about the new code.