Compiling something else than TFS

[liqeen]

After numerous of hours I finally compiled TFS 1.3 pepega, but when I am trying to compile that by downloading it with powershell

GitHub - Qwizer/realmap11: Servidor de Tibia mapa global na verão 10/11.9

Servidor de Tibia mapa global na verão 10/11.9. Contribute to Qwizer/realmap11 development by creating an account on GitHub.

github.com

and anything other than TFS it drops me a error:
"cannot open file 'libbost_system-vc-141-mt-1_64.lib'"
Does someone know how to fix it?

 

[LazyBear]

What software are you using to compile the server? Are the libraries correctly linked in that project? Are you trying to compile in x86 or x64?

 

[liqeen]

What software are you using to compile the server? Are the libraries correctly linked in that project? Are you trying to compile in x86 or x64?

Im using vcpkg & mvs 2017 so far I did everything like it is in compiling tutorial here:

Compiling on Windows (vcpkg)

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

github.com

Are the libraries correctly linked in that project? - Well didn't linked anything, just downloaded libraries by vcpkg and compiled.
I'm using release x64 to compile

 

[LazyBear]

vcpkg is a challenging and fastest way to compile, but not for everyone. I'd suggest you take an alternative way in case it keeps giving the same issue later.

In that case, are you sure you've installed correctly libraries for x64 in Powershell?

vcpkg install boost-iostreams:x64-windows boost-asio:x64-windows boost-system:x64-windows boost-filesystem:x64-windows boost-variant:x64-windows boost-lockfree:x64-windows luajit:x64-windows libmariadb:x64-windows pugixml:x64-windows mpir:x64-windows cryptopp:x64-windows

Now you must make sure that vcpkg is linking your installed libraries for your projects. Check it out here: microsoft/vcpkg (https://github.com/microsoft/vcpkg) (The best way to use installed libraries with CMake is ...). When you next launch .sln project, you will see at the beginning it starts to include all libraries installed from your vcpkg file, if that happens, it means that libraries are pretty much linked to all your projects (which by default TFS should include vcpkg, I believe).

 

[liqeen]

vcpkg is a challenging and fastest way to compile, but not for everyone. I'd suggest you take an alternative way in case it keeps giving the same issue later.

In that case, are you sure you've installed correctly libraries for x64 in Powershell?

vcpkg install boost-iostreams:x64-windows boost-asio:x64-windows boost-system:x64-windows boost-filesystem:x64-windows boost-variant:x64-windows boost-lockfree:x64-windows luajit:x64-windows libmariadb:x64-windows pugixml:x64-windows mpir:x64-windows cryptopp:x64-windows

Now you must make sure that vcpkg is linking your installed libraries for your projects. Check it out here: microsoft/vcpkg (https://github.com/microsoft/vcpkg) (The best way to use installed libraries with CMake is ...). When you next launch .sln project, you will see at the beginning it starts to include all libraries installed from your vcpkg file, if that happens, it means that libraries are pretty much linked to all your projects (which by default TFS should include vcpkg, I believe).

Ye it loads libraries whenever I start a new project, and I am sure I've installed libraries correctly.
Btw when I click CTRL+F in vcpkg folder and look for "_system" I can see a lot of 142 vc libraries and only two of 140, should it be like this?

 

[LazyBear]

Not really, v140 is for Visual Studio 2015, v141 is for 2017 and v142 for 2019.

So now the error is obvious, it cannot really open any library for v141. I'd suggest you find a way to install such, or if you have Visual Studio 2019 then change in properties Platform Toolset to v142. I have no clue where you can find v141 libraries for vcpkg, but try googling it. Another way would be, changing these libraries name to v141 instead of v142. Give it a try with a backup made earlier.

 

[liqeen]

Not really, v140 is for Visual Studio 2015, v141 is for 2017 and v142 for 2019.

So now the error is obvious, it cannot really open any library for v141. I'd suggest you find a way to install such, or if you have Visual Studio 2019 then change in properties Platform Toolset to v142. I have no clue where you can find v141 libraries for vcpkg, but try googling it. Another way would be, changing these libraries name to v141 instead of v142. Give it a try with a backup made earlier.

Well I tried to compile with 2019 but still gives me the same error, even after retargeting the project several times, tried also with name changing still no sucess.

 

[rwxsu]

Did you do .\vcpkg integrate install after installing with vcpkg? (close Visual Studio first)

 

[liqeen]

Did you do .\vcpkg integrate install after installing with vcpkg? (close Visual Studio first)

Yes I did, I was following the tutorial step to step like it says and it works but only for TFS 1.3 nothing else

 

[LazyBear]

Try to take a look here, looks like that vcpkg finds the latest VS version it can find.

vcpkg/docs/users/triplets.md at master · microsoft/vcpkg

C++ Library Manager for Windows, Linux, and MacOS. Contribute to microsoft/vcpkg development by creating an account on GitHub.

github.com

How to build package for mulitple versions of Visual Studio / multiple toolsets? · Issue #1207 · microsoft/vcpkg

Is it possible to build e.g. boost for multiple toolsets (140 and 141) with vcpkg? (If 140 and 141 is a bad example because they are compatible, think of 141 and 150) Perhaps the triplet could be e...

github.com

 

[liqeen]

Did you do .\vcpkg integrate install after installing with vcpkg? (close Visual Studio first)

He actually fixed it with teamviewer, great guy

 

[rwxsu]

He actually fixed it with teamviewer, great guy

Fix: Use Visual Studio 2015 Community (he already had it installed) and follow step by step: mattyx14/otxserver (https://github.com/mattyx14/otxserver/wiki/Compilling-on-Windows)

The reason it was looking for v141, is because he had opened the project in VS2017 and clicked upgrade.

v140 is for Visual Studio 2015, v141 is for 2017 and v142 for 2019.