Compiling TFS 1.6 compiling error

[Mjmackan]

Trying to compile TFS 1.6 (The Forgotten Server 1.6 (https://otland.net/threads/the-forgotten-server-1-6.289173/)) with the help of this tutorial: Compiling on Windows (vcpkg) (https://github.com/otland/forgottenserver/wiki/Compiling-on-Windows-%28vcpkg%29)

Everything went smooth but when Im trying to compile i am getting several errors as shown in picture. I have been searching around now for a day and wont seem to get any further so any help would be appreciated.

 

[Sorky]

seems like you didnt install boost

 

[Gesior.pl]

Everything went smooth but when Im trying to compile i am getting several errors as shown in picture. I have been searching around now for a day and wont seem to get any further so any help would be appreciated.

1.6 does not auto-install required libraries in Visual Studio (in required versions, it installs 'newest' from vcpkg, not version required by TFS), because it misses these lines from 1.7 (maybe some more, I'm not sure):

forgottenserver/vc17/theforgottenserver.vcxproj at master · otland/forgottenserver

A free and open-source MMORPG server emulator written in C++ - otland/forgottenserver

github.com

After you add these lines and re-run VS, it will use vcpkg.json file to detect required vcpkg libraries versions and install them before compilation.

 

[Mjmackan]

seems like you didnt install boost

Boost is installed.

1.6 does not auto-install required libraries in Visual Studio (in required versions, it installs 'newest' from vcpkg, not version required by TFS), because it misses these lines from 1.7 (maybe some more, I'm not sure):

forgottenserver/vc17/theforgottenserver.vcxproj at master · otland/forgottenserver

A free and open-source MMORPG server emulator written in C++ - otland/forgottenserver

github.com

After you add these lines and re-run VS, it will use vcpkg.json file to detect required vcpkg libraries versions and install them before compilation.

Tried it, didn't change anything unfortunately.

 

[Wazzup88]

can you check inside your vcpkg for that boost/beast/core error.hp and make sure it exists? if not you will need to install that library.
.\vcpkg install boost-beast (windows- run in terminal inside your vcpkg folder) then you will need to redirect your "vc17" or build folder to the new vcpkg using the toolchain command.

 

[Mjmackan]

can you check inside your vcpkg for that boost/beast/core error.hp and make sure it exists? if not you will need to install that library.
.\vcpkg install boost-beast (windows- run in terminal inside your vcpkg folder) then you will need to redirect your "vc17" or build folder to the new vcpkg using the toolchain command.

Its something there, not sure what to look for really or in which folders.




As in just vcpkg folder there isnt much:

 

[Wazzup88]

Its something there, not sure what to look for really or in which folders.

View attachment 93453


As in just vcpkg folder there isnt much:
View attachment 93455

i wish i could help you more but honestly these compiling things can turn into a nightmare to solve. even my personal project took atleast 10 hours of my time to compile properly, after updating all libraries and having to edit source files to use newer version of boost and fixing the linking with cmakelists etc. its a lot of trouble. fortunately for you, you only have 12 errors there so I think you could do it, but it will be hard to find a specific answer here that fixes your problem, sometimes when you fix one, another will arise. but like gesior said, this one comes with a vcpkg.json which should fix your libraries for you. although it is telling you there is no file or directory for that error.cpp, so it either doesn't exist or your linking isn't finding the library.

 

[Mjmackan]

i wish i could help you more but honestly these compiling things can turn into a nightmare to solve. even my personal project took atleast 10 hours of my time to compile properly, after updating all libraries and having to edit source files to use newer version of boost and fixing the linking with cmakelists etc. its a lot of trouble. fortunately for you, you only have 12 errors there so I think you could do it, but it will be hard to find a specific answer here that fixes your problem, sometimes when you fix one, another will arise. but like gesior said, this one comes with a vcpkg.json which should fix your libraries for you. although it is telling you there is no file or directory for that error.cpp, so it either doesn't exist or your linking isn't finding the library.

Hehe yeah I had more errors before, took me a while to correct but now it seems like im stuck.
Don't get why we don't just include correct vcpkg package, this is annoying.

Edit: Maybe I have been adding the directory at the wrong place?
I added them here at configuration properties -> vcpkg -> installed directory

 

[Wazzup88]

Hehe yeah I had more errors before, took me a while to correct but now it seems like im stuck.
Don't get why we don't just include correct vcpkg package, this is annoying.

Edit: Maybe I have been adding the directory at the wrong place?
I added them here at configuration properties -> vcpkg -> installed directory
View attachment 93463

Its very annoying. I have used the “correct” vcpkg as other people that compiled it easily, and it still didn’t work for me. Usually when i link it i use a command like this ‘
DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_BUILD_TYPE=Release’. This is just an example don’t use it. But it basically builds all your .sln and other files using that path you specify. But sometimes it is necessary to edit those properties in the tfs project like you are doing

 

[Gesior.pl]

Maybe I have been adding the directory at the wrong place?

You should run ./vcpkg integrate install in vcpkg directory and it should be enough to make VS detect where is vcpkg.
You should use TFS master branch, not 1.6: GitHub - otland/forgottenserver: A free and open-source MMORPG server emulator written in C++ (https://github.com/otland/forgottenserver)
Right now only Release x64 build works in Visual Studio, but that's default.