-
Notifications
You must be signed in to change notification settings - Fork 46
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
How can I compile the tf_mesh_render?I couldn't generate the 'rasterize_triangles_kernel.so'. #43
Comments
In the README.md, we give detailed steps. Totally follow this and you can get the .so |
I have met this problem as well, and a feasible solution is:
|
@jiaxiangshang In the README.md , i did not see any about how to get the .so . so could you tell this clearly? thanks |
How about the solution step above your question?
|
你好,
非常感谢那么晚还有你的回信。但我在你的项目文件夹下的目录中,并没有发现这个存在的路径,可能我build的时候直接提示失败了吧。
…--------------原始邮件--------------
发件人:"jiaxiangshang ***@***.***>;
发送时间:2022年4月28日(星期四) 晚上10:22
收件人:"jiaxiangshang/MGCNet" ***@***.***>;
抄送:"刘旭 ***@***.***>;"Comment ***@***.***>;
主题:Re: [jiaxiangshang/MGCNet] How can I compile the tf_mesh_render?I couldn't generate the 'rasterize_triangles_kernel.so'. (#43)
-----------------------------------
How about the solution step above your question?
I have met this problem as well, and a feasible solution is:
download and install the bazel == 0.10.0 from bazel-0.10.0-released-link;
cd thirdParty/tf_mesh_renderer/ && bazel build ...
cp bazel-out/k8-fastbuild/genfiles/mesh_renderer/kernels/rasterize_triangles_kernel.so ./mesh_renderer/kernels/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Then, solve the build problems? |
thanks for you answer, but it seems that I can't get the rasterize_triangles_kernel.so file after bazel build, or I get the rasterize_triangles_kernel.so file in some other folder under other bazel and gcc version, but it can't be used in the end. |
No description provided.
The text was updated successfully, but these errors were encountered: