/install/bin`. But it is empty. I see all the config.cmake files which find\_package() is looking for is inside `C:\cmb\RelWithDebInfo\install\lib\cmake`. But I didn’t even add `C:\cmb\RelWithDebInfo\install\lib` to my PATH.
Thanks,
Yang
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [July 14, 2022, 3:16pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/2 "2022-07-14T15:16:38Z")
Hi Yang,
Basically this is just how the superbuild is setup to work. Each project in the superbuild is designed to install everything needed into the `build/install` directory, so that any project that depends on it can find the headers/libs needed. So ParaView puts all the headers, libs, dlls and binaries it built into the `install` dir, and then SMTK looks there because it is set up that way by the superbuild.
This convenience is broken for dependencies if you choose to do a “developer build”, because that project no longer installs its headers/libs into the superbuild’s `build/install` directory. So you need to tell any dependencies explicitly where that project is. For example, if you do a developer build of SMTK, if you then want to build aeva-session which depends on it, you would need to add `-Dsmtk_DIR:PATH=C:/cmb/smtk/build` with the SMTK build dir to your cmake command.
HTH,
Aron
---
### Author:  [@Yang](https://discourse.kitware.com/u/Yang)
#### Post date: [July 14, 2022, 4:48pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/3 "2022-07-14T16:48:27Z")
Thanks! I think I got it. To quote from find\_package() [documentation](https://cmake.org/cmake/help/latest/command/find_package.html), `Path entries ending in `/bin`or`/sbin` are automatically converted to their parent directories:` So, this is a cmake feature. I was scratching my head on why it finds `build/install/lib` as I only added `build/install/bin` to my PATH.
Regarding the developer build, if I choose developer mode, does it allow me to use Debug configuration? It seems like superbuild only supports Release and RelWithDebInfo
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [July 14, 2022, 4:55pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/4 "2022-07-14T16:55:56Z")
The `PATH` environment variable is not used by CMake, I don’t think - it is just used when running your app to find DLLs. I think the docs are referring to `CMAKE_MODULE_PATH`, which is set by the superbuild.
As for using Debug, not on Windows, unfortunately - you must choose either the debug runtime or the release runtime consistently for all libraries in your project, otherwise you get linking errors. The best bet is to go with RelWithDebInfo for everything. This limitation does not apply on Mac/Linux.
---
### Author:  [@Yang](https://discourse.kitware.com/u/Yang)
#### Post date: [July 14, 2022, 4:57pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/5 "2022-07-14T16:57:28Z")
I am having the issue which doesn’t load OpencascadeSession. I enabled OpenCascadeSession in superbuild and but when I loaded that plugin in the application, I got the following message.
I am using RelWithDebInfo configuration and this message doesn’t help much. I was wondering that if debug configuration could throw out more information?
---
### Author:  [@Yang](https://discourse.kitware.com/u/Yang)
#### Post date: [July 14, 2022, 5:30pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/6 "2022-07-14T17:30:45Z")
Then I don’t understand it.
when I build superbuild project, it will add `build/install/lib` to CMAKE\_MODULE\_PATH such that an external project, e.g., aeva-session, can find the dependencies. Is this correct?
I just tested it. If I removed build/install/bin from PATH and reconfigure aeva-session, it can’t find smtk package. What I have observed so far:
`build/install/bin` in PATH environment variable → can find dependencies
`build/install/bin` not in PATH environment variable → can’t find dependencies
Just curious what is going on under the hood.
---
### Author:  [@aron.helser](https://discourse.kitware.com/u/aron.helser)
#### Post date: [July 14, 2022, 6:06pm UTC](https://discourse.kitware.com/t/how-does-cmake-find-all-the-dependencies-installed-by-cmb-superbuild/862/7 "2022-07-14T18:06:19Z")
Huh, I didn’t know that, interesting. What I believe is happening is that by adding to your PATH you are making those projects available as system projects - i.e. installed globally, like you might install a system Python or system Qt. This works, but makes it harder to swap versions for multiple builds.
I don’t think a Debug build will help with the OpenCascade plugin load. It looks like it’s missing a dependency. I think if you make a dummy project and dummy debug config to launch the app, it should tell you more. If not, you can look at the open cascade DLL with a dependency walker, like depends.exe, to see what it might be missing.