-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation error #4
Comments
I do not use Windows nor heard of Quick Start section
Is |
And what you use to compile? |
I use GCC. |
You mean gcc on linux? |
Yes, Arch Linux. |
Okay, I have a VPS with debian, I will try there, and you need an specific version of gcc? |
Is possible that you can share the command line to compile the bot, gui and plugin? I have all installed but first time compiling on linux, just need to know what command line I need to use please ^^ |
Cool but of course it would be nice if you get build on Windows :) was the |
As you said, the answer is no, here is the log C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe -G "Ninja" -DCMAKE_INSTALL_PREFIX:PATH="C:\Users\Donato\CMakeBuilds\f242219b-f993-b533-bb49-e9263402c529\install\x64-Debug (default)" -DCMAKE_CXX_COMPILER="C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/HostX64/x64/cl.exe" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\COMMUNITY\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" "C:\Users\Donato\bylihis_joblogger" returned with exit code: 1 But I don't know where to put that variable "CMAKE_TOOLCHAIN_FILE" |
Is this StackOverFlow answer helpful? https://stackoverflow.com/a/50888508/3101793 |
I did all the things but is still not working with visual studio on windows, same error about msgpack. Other thing, have more luck doing this on debian, I put the "cmake ." and then the "make" but an error appears: |
I created a PR #5 which makes it build with Visual Studio 2017. Could you "review" it by testing it? And regarding that error which you faced on Debian, it probably needs to be:
|
Thank you, I tried with VS and now the things are going better, but at the end one error and two warnings appears: ERROR1: The CMakeSettings.json contain: CMake Warning at C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.12/Modules/FindBoost.cmake:847 (message): |
I solved the verbosity error changing the "buildCommandArgs":"-v" to "buildCommandArgs": "-v:m"But now, I have a lot of errors:
|
I forgot to mention about the Which Windows version you're using? |
Windows 10 LTSC, I installed windows 8.1 sdk and the warnings disappear, but still have like 170+ errors. I will try in another machine with windows 10 pro. |
Weird.. Anyway the error seems like a linking issue; it tries to link OpenSSL libraries while the symbols already came from libeay32.lib and ssleay32.lib. EDIT: I meant vice versa with the linking.. |
Seems that I might have screwed up with
I updated PR with |
No, I don't get that error, but maybe the problem with me is due to the windows version, Im installing now a normal windows 10 pro and will do all again to see if that works. I will come back when I have tested this on the new environment to let you know. I would like to give you a big thanks for all your time and help, I really appreciate it. |
Something there is different, just have to figure out what as I don't see "install specific version of Windows" as a real solution. Let me know how your test go. If still same error then give me full log of the build (preferably in pastebin as it's so huge with all the errors). |
I follow all the steps in a new windows install, can you check this pastebin? I can see the two files compiled, ets2-job-logger.exe (7.741kb) and ets2-job-logger.dll (53kb), I did double clic on .exe and put the mark on "Install ETS2 plugin" set the path, also the api url and apikey, then press OK and say "Error: Plugin file missing, check your program installation" I checked inside ETS2 installed path, and don't create the plugins folder (to put the ets2-job-logger.dll inside). I created the dir manually and put inside the ets2-job-logger.dll and still saying that the plugin file is missing. Maybe is not detecting in the correct way the SO. |
Also, is possible that you can upload a compiled version for windows? So in the meanwhile I can start working in the way to receive the information on the web please ^^! |
That looks like a successful build 👍
On Windows the plugin (ets2-job-logger.dll) is expected to be found from same directory with the .exe. It will be then copied to the ETS2 directory whenever the checksum of the plugin in ETS2 directory do not match the checksum of the plugin next to .exe when the program is started. The PR can be merged as it seems that there is no more errors when compiling? |
no more compilation error! 👍 But I did all you waid about missing file, and still saying missing plugin file, this is my step by step. I have one folder called joblogger, inside the .exe and .dll. I double clic on .exe and check install ETS2, browse the path steamapps/common/EuroTruck Simulator 2/. I put the api url and api key, then I press OK and error apears "Plugin file missing" and from there, every time when I double clic on .exe say the same and close. |
Could you create new issue for that? I'll merge the PR and close this issue. EDIT: I had forgotten.. The .dll on Windows is expected to be in |
Hello there,
Im trying to compile this in Visual Studio 2017, Im installer msgpack and all dependencies with vcpkg but is still saying that the msgpack is not found.
Add the installation prefix of "msgpack" to CMAKE_PREFIX_PATH or set
"msgpack_DIR" to a directory containing one of the above files. If
"msgpack" provides a separate development package or SDK, be sure it has
been installed.
The text was updated successfully, but these errors were encountered: