CppCommon | Cross-platform C common library for Linux , OSX , Windows

ADTF does not deploy QtCharts binaries because the license is incompatible. Qt is basically LGPL licenesed which works fine with ADTF license. But some components are licensed under GPL, QtCharts is one of it. You are not allowed to use QtCharts with ADTF because then you violate the combined work rule described within GPL. GPL is not working with commercial and closed source licenses, only with open source GPL compatible licenses like GPL itself, MPL or others. Anyway, because the binary is missing you are getting the error, that some dependencies are missing. But even when you put the binary there, it is not allowed, neither private nor commercial. Its incompatible and thats why ADTF tries to protect the customer and delivers only LGPL content. You even not allowed to use commercial Qt with ADTF using open source Qt because Qt declines mixing oss with commercial license even thats the same binary (politics...). Only chance, buy qtcharts standalone from qt marketplace then its compatible with LGPL. But you have to put the binary yourself. Or you link static, which is allowed with commercial/marketplace license from Qt.

Ok, better should have searched 3 minutes longer. But for sake of completeness, here is the solution:

https://discourse.vtk.org/t/vtk-9-and-java-vtk-jar-not-automatically-generated-also-location-of-wrapper-dlls/3354/19

The essence:

The VS cmake does not know how to build java files so the last stage of building the jar file has to be done manually since vtk 9.0.0

The relevant code from the link

This seems to be a known bug, it's because you have spaces in your user name Acer Aspire :

https://github.com/flutter/flutter/issues/73644

https://github.com/flutter/flutter/issues/75611

There seemed to be an error in my linking of the path to the library where I didn't include the library .lib. Only include the path and not the path and lib file in the directory.

Follow these steps

1. Open Atom IDE.
2. Open settings, and open Settings or preferences.
3. Search for platform-io-terminal in the package search and install it
4. Make sure that the plugin publisher is Platform-IO
5. Install it.
6. Restart the IDE or your computer.

MSB3073 exited with code 3 - Post Build Event in Visual Studio 2017

The issue is related to your dynamic library project and not related to VS.

And when you want to register a com dll, the dll project should contain a ID to register into system. However, the dynamic library project does not have the ID by default. So this type of project cannot used as DLLs that will to be registered.

If you still want to use dynamic library project, you should implement DllRegisterServer to add the ID.

You can use ATL projects which contain the ID as dll projects .

This is a similar issue about it.

Solution

1) Instead, you should create ATL projects.

2) Then, in the command, you should remove /c which was abandoned so far.

Or use like this command:

regsvr32 /n /i "$(TargetPath)" as command in post-build event.

=====================

Update 1

Since your project is an old WRT project, you can just create a new WRT runtime component project in VS2017 and then migrate the content of your old project into the new one. It will save you a lot of time and avoid a lot of tedious mistakes.

1) Please install C++/WinRT vs extension first.

2) Then create a new windows runtime componment project and then migrate your old project's content into the new one.

In my side, the project can works well with command regsvr32 /n /i "$(TargetPath)".

An Internal compiler error is always a bug with the compiler. In this case, it's prevented building of a library that is needed later in the build process.

Your options are limited. I suggest trying a different version of Visual Studio.

You should also report this to Microsoft.

Couple of errors here...

1. Your custom command output and depends of the same file, generate.py
   note: you can see a make error in the trace

2. By default add_custom_command will the current source dir as working directy while custom target is run in the current build dir.
   i.e. both are running in different directory -> two different pipenv used...

3. You muse use pipenv run python instead of pipenv run ${Python3_EXECUTABLE}...

4. here my Dockerfile to run some tests

You do not link against DLL libraries. These files are for the run-time loader. Typically, DLLs will be paired with a .lib import library, which you can use for linking. The CMake syntax to import and link against a DLL with a paired .lib is as follows (use IMPORTED_IMPLIB also):