Ryzom

These options are part of VS's global config and not a part of the solution/project files. If you start messing with peoples global compiler config you have a large chance of breaking someones production projects.

Anyone who's used C++ should have no problem setting the libraries up and getting the compiles to work. For those folks who are not C++ programmers perhaps a binary package would be more appropriate -- click a batch file and you have a server. If you can't setup the compiler properly you have very little chance of modding such a large codebase.

While I agree there are some issues right now, we need to give the devs some time. You cannot expect newbies to jump onto the bleeding edge, they need to sit back and wait for the pros to get everything compiled and running, scripts written, and articles typed up into the wiki. Things will be much easier in a month or two -- just give it time.

If you have D:\SOURCECODE\mpo\code\nel\include linked the ones below it should not be required to be in the list also. Unless VS is messing up on you.

Your Include files link should look very similar to the following

G:\DirectX SDK\Include
G:\Qt\4.6.2\include
G:\SourceCode\Working\code\nel\include
G:\SourceCode\Working\code\nel\src
G:\SourceCode\Working\code\external\include
G:\Microsoft Visual Studio 9.0\VC\atlmfc\include

Library files:
G:\SourceCode\Working\code\external\lib
G:\SourceCode\Working\code\nel\lib
G:\Qt\4.6.2\lib
G:\DirectX SDK\Lib\x86
G:\Microsoft Visual Studio 9.0\VC\atlmfc\lib

Source files:
G:\SourceCode\Working\code\nel\src\ligo
G:\Qt\4.6.2\src

Executable files:
G:\Qt\4.6.2\bin

These should be the only directories you need to link up if you haven't changed \ added anything to VS

It\s worth noting I have the source downloaded from the SVN saved to the following path
G:\SourceCode\Working

You will need to make changes to the paths above depending on where you have it saved at and where you have QT installed.

That setup allows me to compiled everything on the SVN. (Tools, Server, and Client) Thats with MS Visual Studio 2008. (Non-Express edition) The Express edition you might need to add one or two more paths to the list.

well the reason I did

D:\SOURCECODE\mpo\code\nel\src
D:\SOURCECODE\mpo\code\nel\include
D:\SOURCECODE\mpo\code\nel\include\nel
D:\SOURCECODE\mpo\code\nel\include\nel\sound

was because it had sub directories in sub directories and with things like the world editor gave me errors and such. When I added them like this for example I got rid of the errors. Now it might be my VS acting up though but it was the reason I did it.

But does it cause more issues to have it like that or should it be fine? If I'm causing more problems Id hate for that to happen.

I don't think it would cause any issues (could if a certain source file is looking for something in a specific spot) but I would be more worried why VS is not moving through the sub folders like it should be.

If you include \code\nel\include that should also add all the files / folder below that directory. You should not need to add all the sub folders and locations below that directory.

Okay once they fix the darn nel build not sure if you rebuilt it in the last 24 hours but it does not compile anymore. I will redo all my paths and see what happens :)

what is the qt 4.6.2 that you are using? I am having some build errors as well as I do not see the stlport include line.