I've just checked my C:/Windows/SysWOW64 directory and it does not contain
a driver_root directory. It would have been a good catch if that was the
cause.
On 27 September 2012 19:20, Andreas Schenk
wrote:
> I had the same problem recently. Do you have a *driver_root* directory in*
> **C:/Windo
I had the same problem recently. Do you have a/driver_root/ directory in/
//C:/Windows/SysWOW64/?
On 64-bit Windows systems the System32 directory contains the 64bit DLLs.
For 32-bit executables (like cmake for example), the WOW64 subsystem
automatically redirects
System32 directory access to
Once the driver project has converted to using cmake that is what I plan to
do - use find_path() to look for driver_root/CMakeLists.txt. But in the
meantime I'm stuck using find_file() instead which works but it looks like
a bug that I need to specify the NO_DEFAULT_PATH option to avoid getting an
On Tue, Aug 28, 2012 at 6:59 PM, Glenn Coombs wrote:
> I need to test for the presence of a directory called driver_root. I
> couldn't see a find_directory() command in the help
I cannot comment about your issues concerning find_file, but if you know
the name of a file contained in the director
I need to test for the presence of a directory called driver_root. I
couldn't see a find_directory() command in the help so I am using the
following lines in my CMakeLists.txt:
message("1 DRV_ROOT_CHECK: ${DRV_ROOT_CHECK}")
if (DEFINED ENV{DRV_ROOT})
find_file(DRV_ROOT_CHECK drive