• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

OTClient redemtion latest error in windows compiling?

epsilon2

New Member
Joined
Feb 20, 2009
Messages
47
Reaction score
4
LUA:
The command "C:\otclient\vc17\vcpkg_installed\x64-windows-static\tools\protobuf\protoc --proto_path=../src/protobuf --cpp_out=generated ..\src\protobuf\appearances.proto" exited with code 3.

I get this error during descripted vcpkg comilation on windows 10 and 11.
Any small fix or do i have to wait till meha fix building ?
 
Any small fix or do i have to wait till meha fix building ?
Isn't it related to problem with Release build after building Debug on Windows?
I had something about 'protobuf' in error after building Debug and trying to build Release then.

WARNING - right now (2024-12-23) OTCR vcpkg version does not work (as described below), so maybe switch build to Debug and try to compile again

For me this fixed problem:
  • close Visual Studio
  • open OTC sub-folder vc17
  • remove folders: generated, otclient and vcpkg_installed
  • open Visual Studio
It should download and recompile C++ libraries again and then OTCR should build Release again.



I tried to run it now with clean vcpkg and it fails on 7zip packed into invalid .7z file:
Code:
1>Additional packages (*) will be modified to complete this operation.
1>A suitable version of 7zip was not found (required v24.9.0).
1>Downloading https://github.com/ip7z/7zip/releases/download/24.09/7z2409.exe
1>Extracting 7zip...
1>EXEC : CMake error : Problem with archive_read_next_header():
1>EXEC : CMake error : Problem extracting tar: C:\vcpkgs\vcpkg_mehah\downloads\7z2409.7z
1>'CMake' failed while extracting C:\vcpkgs\vcpkg_mehah\downloads\7z2409.7z.

Problem extracting tar: C:\vcpkgs\vcpkg_mehah\downloads\7z2409.7z
I've checked this file and it's not valid 7z archive (7zip 24.09 cannot open this file).
 
Debug builds don't work because vcpkg is forced to use release because of CMake configuration... most likely fix is to just remove this line..


Ofc this also means you would need to go ahead and delete the vcpkg_installed folder again, so that it can correctly fetch dependencies.
 
Last edited:
Debug builds don't work because vcpkg is forced to use release because of CMake configuration... most likely fix is to just remove this line..
Not related. Problem is with Visual Studio build on Windows, which uses VS project, not CMake.
Build using cmake creates 2 vcpkg_installed directories: build/linux-release/vcpkg_installed and build/linux-debug/vcpkg_installed
I build new as described, and it still does not compile. Seams like it is a new broken build.
"vcpkg" is broken, if you run "git pull" on old version of vcpkg to get newest version:
After git pull in vcpkg directory you must run again bootstrap-vcpkg.bat (same as you do when you install vcpkg for first time).
 
It's not just windows that debug builds are failing on because of this issue...
Debug and release builds with CMake work on Linux. I've tested it, before I posted that your answer is not related.
You can configure and build CMake debug and release builds in any order and it works - I tested this too.

SET from CMakeLists.txt is in less important scope than CMake cache, which is set by CMakePresets.json:
Doc:
 
Debug and release builds with CMake work on Linux. I've tested it, before I posted that your answer is not related.
You can configure and build CMake debug and release builds in any order and it works - I tested this too.

You keep acting like I only post stuff just to post stuff or something, idk what the hell your problem is, but I don't just make shit up. I had a friend just a day before this thread was openened, tell me about them having this same problem with debug builds being broken ON LINUX.

Here is the image he sent me of it failing to build.

1735686910080.webp

Since he showed me this error, and its with debug builds, and the error is saying something about protobuf JUST LIKE OP'S PROBLEM, I connected the two to mean that the build was just broken on linux, which apparently according to you it's not.... but all that really means is that you two are clearly running different OS's, so why don't you chill your superiority complex!

I don't know what your problem is, but I have had enough, I'm completely done responding to you or even acknowledging your existence on posts here or github, I wash my hands of you!
Let this be a lesson for you, you aren't smarter than everyone else in the world, everyone else in the world is not inferior to you, and you need to grow the hell up!
 
Last edited:
Back
Top