Closed ger-benjamin closed 4 months ago
Those files should be generated when the C# code is compiled. Make sure you followed the instructions exactly. A common mistake is to forget to build Reinterop before opening the project in Unity, at which point Unity will (annoyingly) delete the .meta file associated with the Reinterop.dll. After that, building Reinterop won't help, because the now deleted .meta file told Unity how to use it properly. You'll need to build Reinterop, restore that file from git, let Unity compile the plugin source files, and then you can compile the C++ code.
This is all very complicated though. It's probably much easier to fix whatever compilation problem you had with the pre-built version.
I'm going to close this because there's nothing actionable on our side. If you're still having trouble, please post to the community forum.
I build the Reinterop part without issue I think... I'll try again, maybe take a closer look to the logs, or re-try the pre-built version.
I understand that you close it. Let see if other people will re-open it. Thanks, and have a nice day.
I build the Reinterop part without issue I think...
Did you do that before opening the project in Unity for the first time, though?
In any case, if files like DotNet/System/String.h
are missing, it means the code generation that runs as part of the C# compilation didn't happen or didn't work. So open Unity back up, let it compile your project, and see if there are any errors in the console.
Did you do that before opening the project in Unity for the first time, though?
Well, unity was running, but this cesium-unity project was NOT loaded in unity. Cesium-unity was (and still is) in a new folder, not currently linked anywhere. I've wanted to try to load it after the "Build for the Editor" part.
Now you mention it, I've skipped the first line of this section, as it says it will leads to error:
To start the Cesium for Unity build process, open the cesium-unity-samples project in the Unity Editor.
So, I'll try to load it first, and then run the build commands.
Yes ok, it's better now. Then I had these kind of errors:
[ 97%] Building CXX object Runtime/CMakeFiles/CesiumForUnityNative-Runtime.dir/src/CesiumRasterOverlayUtility.cpp.o
In file included from /home/xxx/Documents/git/unity-cesium/cesium-unity-samples/Packages/com.cesium.unity/native~/Runtime/src/CesiumPropertyTablePropertyImpl.cpp:3:
/home/xxx/Documents/git/unity-cesium/cesium-unity-samples/Packages/com.cesium.unity/native~/Runtime/src/CesiumPropertyTablePropertyImpl.h:53:7: error: ‘std::int64_t’ has not been declared
53 | std::int64_t featureID,
| ^~~
/home/xxx/Documents/git/unity-cesium/cesium-unity-samples/Packages/com.cesium.unity/native~/Runtime/src/CesiumPropertyTablePropertyImpl.h:56:8: error: ‘int8_t’ in namespace ‘std’ does not name a type
56 | std::int8_t GetSByte(
| ^~~~~~
/home/xxx/Documents/git/unity-cesium/cesium-unity-samples/Packages/com.cesium.unity/native~/Runtime/src/CesiumPropertyTablePropertyImpl.h:61:8: error: ‘uint8_t’ in namespace ‘std’ does not name a type
61 | std::uint8_t GetByte(
| ^~~~~~~
etc...
...
But adding #include <cstdint>
in cesium-unity-samples/Packages/com.cesium.unity/native~/Runtime/src/CesiumPropertyTablePropertyImpl.h
solves this last issue.
I think this last issue was due to my version of c++...
Anyway, it's fully working now. Again, sorry for the noise, the error was "me misreading the doc". And thanks for the (very quick) help.
Hi everyone,
I'm wanted to try unity-cesium. I first tried to install the Cesium-Unity from the package-manager of unity, but I had compilation error. So I've tried to build this project myself... without success. It says I miss some headers file. I'm on a debian based sytsem (Pop!_OS), so ~
Ubuntu 22.04
, withcmake version 3.22.1
,dotnet version 8.0.204
I've followed https://github.com/CesiumGS/cesium-unity/blob/main/Documentation~/developer-setup.md And I had no error before this commande:
cmake --build build -j14 --target install --config Debug
During this operation, I've error like:
And here's the build stacktrace (3th execution, same errors but smaller that the first on successful part).
Any idea ? Thanks in advance :-)