[SOLVED] does DIR-NOTFOUND bad?

[A_Jay]

Hello
I want to know why cmake still don’t detect the directory of certain things such as SofaDistanceGrid, SofaSphFluid and metis even after manually set the path multiple times. It still gives the result of DIR-NOTFOUND. It shows no error after configuring but I want to know does affect the next process in MSVC?

[Hugo]

hey @ajay

Could you please explain with more details which cmake configure step you are refering to? which version of SOFA are you using? Could you share the error message?

Thx

Hugo

[A_Jay]

Hello @Hugo

I received the message after I finished configuring in CMake. I used the Cmake ver. 3.18.5 and SOFA 20.06.01. To the be clear configuration process finished with no error message. However, at the SofaDistanceGrid, SofaSphFluid and metis will show at the value section “NAME_NOTFOUND”. I tried to set the path again but resulted in no success as it still shows the same thing. But it does not show any error during the configuring process in Cmake. I am just wondering is this a bug? And will this affect the next step using the MSVC?

[A_Jay]

@Hugo

I have a list of them here:

https://drive.google.com/file/d/1b32s8gjQ6_tM082GeX8ge9EVVdyEWU9i/view?usp=sharing

How can I fix this? Because I feel like it will affect the result

[Hugo]

Dear @ajay,

This should be no problem. You will be able to compile.
I will see exactly why these code do not define their DIR variable.

Best,

Hugo

[Hugo]

Dear @ajay,

When a package (2) is searched by a package (1) (because 1 has a dependency on 2), CMake has actually several ways to find it:
– using the SOFA_ROOT variable
– using the CMAKE_PREFIX_PATH variable
– using the config.h.in

If the package (2) is found using one of the two first ways, the CMake variable NAME_DIR will be set to NOT_FOUND by CMake. CMake should rather inform that the package was found another way.

In four words: no worry, it works.

Best

Hugo

[Author]

Posts