I even would prefer to not hardcode the SDK but I was unable to list key
entries from the registry.
Usually all installed SDKs are listed as subkeys of
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows CE Tools\\SDKs
in this case it is SDK_AM335X_SK_WEC2013_V310.
I think the test
On Wed, Oct 22, 2014 at 10:53 AM, Bach, Pascal wrote:
Am I right that when using the reg tool I need to include
the Wow6432Node again?
Possibly. I'm not particularly familiar with it, but there
are two of them:
C:\Windows\System32\reg.exe
C:\Windows\SysWOW64\reg.exe
Perhaps they take
---
Tests/CMakeLists.txt | 30 ++
1 file changed, 30 insertions(+)
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index 25cc846..fc3359e 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -1835,6 +1835,36 @@ ${CMake_BINARY_DIR}/bin/cmake
On 10/21/2014 05:24 AM, Pascal Bach wrote:
---
Tests/CMakeLists.txt | 30 ++
1 file changed, 30 insertions(+)
The Wow6432Node path component should not be needed because
CMake is aware of how to lookup different registry views.
Also we can fold the lookup into
Subject: Re: [cmake-developers] [PATCH] WINCE: Run Tutorial steps 1-4 as
tests for Windows CE
On 10/21/2014 05:24 AM, Pascal Bach wrote:
---
Tests/CMakeLists.txt | 30 ++
1 file changed, 30 insertions(+)
The Wow6432Node path component should not be needed
On 10/21/2014 09:26 AM, Bach, Pascal wrote:
Your revision looks better ;)
I even would prefer to not hardcode the SDK but I was unable to list key
entries from the registry.
Usually all installed SDKs are listed as subkeys of
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows CE
