NaughtyZZ / 3D_face_dense_registration

Towards Fine-Grained Optimal 3D Face Dense Registration: An Iterative Dividing and Diffusing Method (IJCV2023)
https://github.com/NaughtyZZ/3D_face_dense_registration/tree/main
52 stars 4 forks source link

Cannot compile facedenseregister.cpp #5

Closed qaz8788817 closed 8 months ago

qaz8788817 commented 8 months ago

Hi, I have some problem with using VS2019 to compile facedenseregister.cpp in VC++(with initializations by NICP). And my dependencies are all latest version. Here is the error output: image And it also show some warnings about: image

Would you mind to provide your libigl source code for me? I can't thank you enough.

NaughtyZZ commented 8 months ago

I have already compiled theprogram into a *.exe demo. Here is the igl package I use. igl.zip

qaz8788817 commented 8 months ago

I have already compiled theprogram into a *.exe demo. Here is the igl package I use. igl.zip

But after I execute like this: image

And nothing happened. I don't know why.

Here is the executable file's folder: image

Thank you.

NaughtyZZ commented 8 months ago

I test it just now in several computers and it's OK in the Windows system. The excutation path should be a pure English one? Is the VS runtime environment compatible? You may need some time to debug the source files in other systems. 无标题

qaz8788817 commented 8 months ago

I test it just now in several computers and it's OK in the Windows system. The excutation path should be a pure English one? Is the VS runtime environment compatible? You may need some time to debug the source files in other systems.我剛剛在幾台電腦上測試了一下,在Windows系統中是沒問題的。執行路徑應該是純英文的吧? VS運作環境是否相容?您可能需要一些時間來調試其他系統中的來源檔案。 无标题

Yes, the path is all English. I will try to fix VS runtime environment. Thanks for your help! ^____^

qaz8788817 commented 8 months ago

Sorry to bother you again. I've installed the depandencies for several times, and I still cannot install them successfully. Could you please tell me more details about the VS runtime environment?

Thank you.

NaughtyZZ commented 8 months ago

Mine is window 10, x64, vs2015. I think these details are not useful to you. Does you environment support other programs?

qaz8788817 commented 8 months ago

My machine is like a new computer of Windows 10. Could you please tell me what I need to install or pay attention to before I run the *.exe? And how did you install them? I have installed MKL(using .exe from intel), Eigen(I tried vcpkg. In the VS2019, I can run a simple Eigen program), but I cannot compile libigl success in CMAKE.

Thank you.

NaughtyZZ commented 8 months ago

So the problem is that the igl library is not successfully installed. The runtime environment for vs2019 (some dll files) may differ from vs2015, so you need either to compile the source file first in you environment (I guess) or use some other dll files (compatible to vs2015) to run the *exe demo.

qaz8788817 commented 8 months ago

Execeuse me. Here is my steps for using CMAKE in libigl.

  1. I clone the libigl in my desktop and use system administrator to open CMake.
  2. Check the source code path is "C:/User/xxx/Desktop/libigl", and build path is "C:/User/xxx/Desktop/libigl/build".
  3. Run configure, then it shows me some warning like: image and image
  4. Then I use these ways to fix them: image and image
  5. Delete the cache and configure again. It shows me configuration is done.
  6. Then, I generate it.

After above steps, I go to the CMake prefix path such like "C:/Program Files (x86)/libigl", there is no folder named like this in Program Files (x86). And the "external" folder does not appear.

Does this mean I failed in CMake?

Thank you.

NaughtyZZ commented 8 months ago

I am not good at debugging this issue. I suggest that you can refer to the orignial tutorial at [Libigi](https://libigl.github.io/tutorial/) or ask problem at the original project https://github.com/libigl/libigl. I can see in the tutorial that the igl library are not compatible with x86 programs. image

qaz8788817 commented 8 months ago

Okay, thanks for your help. I repost my question to the original project.