-
Notifications
You must be signed in to change notification settings - Fork 258
[v1] Build failed on Windows #493
Comments
Can you include the |
Sorry for Japanese text because my develop environment is Japanese. error.txt is empty. 2018/01/25 16:48:38 にビルドを開始しました。 ビルドに失敗しました。
経過時間 00:00:14.52 |
Yes, that's what's causing the issue. A unicode character has made its way into the source file, and your codepage (I assume it's a Japanese codepage) doesn't have it. So the compiler can't process it. But I tried to compile with a different code page and it worked just fine. Maybe I picked the wrong one. But I wonder if you have an older version of that file? What does line 2081 of v1\deps\iot-sdk-c\iothub_client\src\iothubtransporthttp.c look like for you? Also, what commit ID is reported when you do the following command?
|
The 2081 line is ... 2079 { I tried delete the 2081 and re-write '}' but it didn't work. Result of 'git log --oneline -1 -- iothubtransporthttp.c' |
Reopening because this won't be fixed in iot-edge until we cut a release that updates our submodule reference to the C SDK. |
Fixed in the latest release: 2018-01-31 |
Latest version(25 Jan. 2018) set can't be build on Windows.
-- Build files have been written to: C:/e/s/v1/deps/iot-sdk-c/build
-- Installing azure_iot_sdks. Please wait...
CMake Error at gatewayFunctions.cmake:170 (message):
Error installing azure_iot_sdks: 1
Call Stack (most recent call first):
modules/dependencies.cmake:39 (findAndInstall)
modules/CMakeLists.txt:6 (include)
-- Configuring incomplete, errors occurred!
See also "C:/e/s/v1/build/CMakeFiles/CMakeOutput.log".
See also "C:/e/s/v1/build/CMakeFiles/CMakeError.log".
CMakeError.log
"C:\e\s\v1\build\CMakeFiles\CMakeTmp\cmTC_63d23.vcxproj" (既定のターゲット) (1) ->
(ClCompile ターゲット) ->
C:\e\s\v1\build\CMakeFiles\CMakeTmp\CheckSymbolExists.c(7): error C2065: '_M_AMD64': 定義されていない識別子です。 [C:\e\s\v1\build\CMakeFiles\CMakeTmp\cmTC_63d23.vcxproj]
-- sorry for Japanese string.
I use a directory which's name is very sort so that I don't think this is not a path length problem
The text was updated successfully, but these errors were encountered: