Expat Build error with VS2019 about ets2-job-logger HOT 14 OPEN

@Lihis installed VS2017 and the CMake extentsion but now getting a different error:

`Expat/2.2.6@pix4d/stable: WARN: Can't find a 'Expat/2.2.6@pix4d/stable' package for the specified settings, options and dependencies:

• Settings: arch=x86_64, build_type=Debug, compiler=Visual Studio, compiler.runtime=MDd, compiler.version=16, os=Windows
• Options: disable_getrandom=True, shared=False, static_crt=False
• Dependencies:
• Package ID: eb4102e772b530edfbc4b0e1be0c1f346423e000`

Managed to bypass it with --build missing

from ets2-job-logger.

I would say that this is not our issue but rather Conan/Expat issue related to Visual Studio 2019 as with Visual Studio 2017 there is no problems. Will you be able to resolve this by yourself? If it is issue on Conan or Expat feel free to link the related issue. Or open pull request if we need to change something to make it work with VS2019.

from ets2-job-logger.

I would say that this is not our issue but rather Conan/Expat issue related to Visual Studio 2019 as with Visual Studio 2017 there is no problems. Will you be able to resolve this by yourself? If it is issue on Conan or Expat feel free to link the related issue. Or open pull request if we need to change something to make it work with VS2019.

Thank you for the quick response and I'll see if there are any fixes available otherwise I will install VS2015.

Thank you for your help.

from ets2-job-logger.

@Lihis Not sure which package you are using but found out that the main Expat is now deprecated: https://github.com/bincrafters/conan-expat

Updated version is: https://github.com/libexpat/libexpat

I hope this helps to resolve the issue.

from ets2-job-logger.

wxWidgets seems to be the one pulling in the Expat as a dependency. Does it work with VS2019 if you make Conan to pull in the latest stable release of Expat a.k.a 2.2.9?

Answering the question about VS2015 in the different issue; like I said above, building should work in Visual Studio 2017.

from ets2-job-logger.

If help, I compiled the gui and plugin like 10 minutes ago without problems, following the instructions on readme for windows. Using Visual Studio 2017 x64 + Visual Studio Tools. As said in the instructions, I used conan to install dependencies.

from ets2-job-logger.

That's good. Unfortunately I can't help much with Windows stuff so I'll edit the title to indicate that this is VS2019 specific issue and leave this open for now.

from ets2-job-logger.

If help, I compiled the gui and plugin like 10 minutes ago without problems, following the instructions on readme for windows. Using Visual Studio 2017 x64 + Visual Studio Tools. As said in the instructions, I used conan to install dependencies.

I've followed the instructions and used VS2017 but still have issues.

from ets2-job-logger.

Comparing the output from AppVeyor build and what you had pasted above and I see the compiler.version is different. In AppVeyor it is 15 while you have 16. Is it so that version 16 is shipped with VS2019 while version 15 is shipped with VS2017?

Also the error message in the first message does not tell much, except execution failed, but who knows why it failed, there wasn't any details?

from ets2-job-logger.

@Lihis
I didn't want to open another issue as this is still related to Windows 10 but using VS 2017

After doing the following step Edit CMake options via CMake -> Change CMake settings -> CMakelists.txt

These are the options that is prompted, which one am I suppose to select?

Also a few other errors which I think are not suppose to be there

from ets2-job-logger.

Even with the CMake GUI version it has an issue finding a file and with a command.

from ets2-job-logger.

@DubStepMad hey, you need to select x64-Release and then, follow the intructions that are inside the readme for windows build.

from ets2-job-logger.

hey, you need to select x64-Release and then, follow the intructions that are inside the readme for windows build.

If one follows the instructions in readme shouldn't they choose x64-Debug as it guides for debug build?

from ets2-job-logger.

hey, you need to select x64-Release and then, follow the intructions that are inside the readme for windows build.

If one follows the instructions in readme shouldn't they choose x64-Debug as it guides for debug build?

Yes, x64-Debug if they want to build a debug build or release for a release build. Also they can choose x64-Debug and as is explained in the readme, after the debug release works, they can replace all the debug for release in the cmake-settings and in the conan install command line.

from ets2-job-logger.