Error with compiling.

[aHoHuMeH]

Hi guys I am new here i try to make my server but i got this error with compiling let's see what give me

[lmame]

Yep you're right, I just tried and it seems the first error is rather the:
"#endif without #if" on file worldmap.cpp, line 67.
And it's true, a #if is missing.

It seems it was the case also on the previous rev as well, it seems it has been deleted on rev 162.

Try this:
BEFORE:

Line number On/Off | Expand/Contract | Select all

1.  
2. if(GServer->Config.Spawntype == 0)
3.  

ADD:

Line number On/Off | Expand/Contract | Select all

1.  
2. #ifdef USEIFO
3.  

[PurpleYouko]

OMG someone using an osprose server.............

If you are using rev 162 then this is the least of your worries. there is a load of stuff in there that will crash the hell out of your server.
162 is the result of me copying selected parts of my KTRose server into the osprose SVN and accidentally taking some stuff that shouldn't be there at all.

config.spawntype is one such thing.
There should be no such config variable in standard osprose code.

163 fixes those issues but apparently still has a very minor problem with linking due to an unresolved link to a function that doesn't exist.

I just uploaded 164 which should compile perfectly. it did for me anyway.

Please make sure you do a complete rebuild as i changed some headers in this rev.

[vze3z5]

So PY, we should use 164?

[rl2171]

In most cases, the newer builds are better.

The latest 164 osprose is such a build.

[PurpleYouko]

So PY, we should use 164?

Yeah.
164 compiles properly and has all the latest stuff.
Any earlier versions are inferior

[JDoeBoy]

Ok, I just tried compiling the osprose server for the first time. I used CodeBlocks and had all the plugins installed for it. When I was finnished compiling the world server, I got warnings. Do I worry about warnings or not? I used the svn build 165 that I downloaded today. My warnings are attached.

Thanks
JD

[XxXshidoXxX]

don't worry about it its nothing

[PurpleYouko]

Warnings like that are no big deal. It's just letting us know that some not so good type conversions have been used and to be a bit more careful with what we program in future.
It will still run just fine.

I almost always compile with warning messages disabled so i never get these at all.