Closed badduck32 closed 2 years ago
they managed to fix it by using Bazel version 5.1.1 I have tried this too, but still no luck.
Please don't install Bazel. You should always prefer Bazelisk.
I'm not sure, but this kind of compile error can be caused by the Bazel version or the compiler version and
sometimes solve the issue.
If those methods don't work, you can at least download the package from the release page or fork this repository and run the Package workflow (if you want to build the plugin with custom options).
Hello, thank you so much for taking your time to reply.
Please don't install Bazel. You should always prefer Bazelisk.
I don't use Bazel, I use Bazelisk, but I set the version of Bazel to 5.1.1 by changing the .bazelversion file. Sadly that didn't change anything.
reinstalling Visual Studio C++ or setting Bazel environment variables (cf. the 6th step in https://github.com/homuler/MediaPipeUnityPlugin/wiki/Installation-Guide#windows-10) sometimes solve the issue.
I have tried reinstalling Visual Studio C++, but now Visual Studio Build Tools 2019 disappeared from the "Installed" tab in Visual Studio installer: But I'll try some more things today to fix that problem. Also, regarding the Bazel variables, this is how they were (and still are) set up when I ran the build script:
set BAZEL_VS=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
set BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC
set BAZEL_VC_FULL_VERSION=14.29.30133
set BAZEL_WINSDK_FULL_VERSION=10.0.19041.0
python build.py build --desktop cpu -vv
(I will check the version of Visual C++ when I get it installed again and change the variable if needed accordingly)
If those methods don't work, you can at least download the package from the release page or fork this repository and run the Package workflow (if you want to build the plugin with custom options).
I don't 100% understand what you mean here (I'm not very experienced with mediapipe or unity packages), but my only goal is to get pose and face tracking working in Unity. Is this .tgz file a package that I can install into my Unity project to get all of this to work, or do I still need to build this repository using the installation guide?
Thank you so much again for your help
Is this .tgz file a package that I can install into my Unity project to get all of this to work, or do I still need to build this repository using the installation guide?
See https://github.com/homuler/MediaPipeUnityPlugin/wiki/Getting-Started#build-and-install-a-local-tarball-file and try importing it to your project, then you'll see what I mean.
I'm not sure, but this kind of compile error can be caused by the Bazel version or the compiler version and
- reinstalling Visual Studio C++ or
- setting Bazel environment variables (cf. the 6th step in https://github.com/homuler/MediaPipeUnityPlugin/wiki/Installation-Guide#windows-10)
sometimes solve the issue.
I have tried reinstalling visual studio build tools entirely and switched to other versions of visual studio build tools, but still nothing... (now the error changed to pose_renderer_cpu.inc(51): error C2001: newline in constant)
Then please download the built package or build the plugin on GitHub Actions (cf. https://github.com/homuler/MediaPipeUnityPlugin/issues/689#issuecomment-1206052587). It seems to me that this is not an issue of this project but of your environment.
Plugin Version or Commit ID
v0.10.1
Unity Version
2021.3.3f1
Your Host OS
Windows 10 Home
Target Platform
UnityEditor
[Windows Only] Visual Studio C++ and Windows SDK Version
Visual Studio C++: 14.29.30133 Windows SDK: 10.0.19041.0
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Command Sequences
I ran python build.py build --desktop cpu -v in the root directory of the repository
Log
Additional Context
I have seen another issue describing almost the exact same problem, and they managed to fix it by using Bazel version 5.1.1 I have tried this too, but still no luck. I get a very similar error saying that cl.exe failed, but then in a different script.