I'm trying to get debugging working for a Windows CE 6.0 application but I cannot even start the debugging process. I can run a "Hello World" application OK but when I try to run my app which is linked against another DLL I don't get any error but debuggin does not start. The DLL is present in the same folder as the executable.
This are the logs from VS2005.
1>------ Deploy started: Project: protobuf_lite, Configuration: Release SDK3 (ARMV4I) ------
2>------ Deploy started: Project: libus_cqlink_msg, Configuration: Release SDK3 (ARMV4I) ------
3>------ Deploy started: Project: libus_cqlink_nw, Configuration: Release SDK3 (ARMV4I) ------
4>------ Deploy started: Project: libus_cqlink_cli, Configuration: Release SDK3 (ARMV4I) ------
5>------ Deploy started: Project: CtrlClientWinCE, Configuration: Release SDK3 (ARMV4I) ------
========== Deploy: 5 succeeded, 0 failed, 0 skipped ==========
I also checked dependencies on Executable on Win CE device using peinfo.exe.
This is the log from peinfo.e
Necessary library file(s):
libus_cqlink_cli.dll Is loadable
COREDLL.dll Is loadable
commctrl.dll Is loadable
ole32.dll Is loadable
OLEAUT32.dll Is loadable
Imports Table:
libus_cqlink_cli.dll
OrigFirstThunk: 0016D3AC (Unbound IAT)
ForwarderChain: 00000000
First thunk RVA: 0016E710
Ordn Name
11 ?instance#USPlatformMgr#cs##SAPAV12#XZ (Bound to: 0016D3E4)
COREDLL.dll
I can not figure out what's wrong I am doing.
Please suggest.
Windows CE devices are very often configured with minimal free space for Storage Memory. While using debugger VS must copy some files to Storage Memory (ie. \Windows folder), and if there is not enough space it fails. The solution is to increasing memory level for Storage Memory, its in control panel -> System Properties -> Memory on your device.
Related
I'm working on a solution in Visual Studio 2017 where there are several projects intended to separate functionality. Those projects are then added as dependencies of other projects.
I'm trying to build a 64-bit exe of the top level project but for some reason some 32-bit dlls are leaking into the build.
------ Build started: Project: LeadtoolsLib, Configuration: Debug x64 ------
LeadtoolsLib -> C:\Users\its-rowc\source\Workspaces\Imaging\LeadTools\bin\x64\Debug\IQLeadtools.dll
------ Build started: Project: LeadtoolsLib, Configuration: Debug Any CPU ------
LeadtoolsLib -> C:\Users\its-rowc\source\Workspaces\Imaging\LeadTools\bin\Debug\IQLeadtools.dll
------ Build started: Project: WebServicesWrapper, Configuration: Debug x64 ------
WebServicesWrapper -> C:\Users\its-rowc\source\Workspaces\Imaging\WebServicesWrapper\bin\x64\Debug\WebServicesWrapper.dll
------ Build started: Project: IQHyland, Configuration: Debug x64 ------
IQHyland -> C:\Users\its-rowc\source\Workspaces\Imaging\IQHyland\bin\x64\Debug\IQHyland.dll
------ Build started: Project: PDFConverter, Configuration: Debug x64 ------
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools.Codecs", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools.Codecs.Fax", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools.Codecs.Tfx", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools.Codecs.Tif", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools.Pdf, Version=19.0.0.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
PDFConverter -> C:\Users\its-rowc\source\Workspaces\Imaging\PDFConverter\bin\x64\Debug\PDFConverter.dll
------ Build started: Project: DocProcessor, Configuration: Debug x64 ------
DocProcessor -> C:\Users\its-rowc\source\Workspaces\Imaging\DocProcessor\bin\x64\Debug\DocProcessor.exe
------ Build started: Project: IQHylandTest, Configuration: Debug x64 ------
IQHylandTest -> C:\Users\its-rowc\source\Workspaces\Imaging\IQHylandTest\bin\x64\Debug\IQHylandTest.exe
------ Build started: Project: IQHylandUnitTest, Configuration: Debug x64 ------
IQHylandUnitTest -> C:\Users\its-rowc\source\Workspaces\Imaging\IQHylandUnitTest\bin\x64\Debug\IQHylandUnitTest.dll
========== Build: 8 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
The general hierarchy is as follows:
PDFConverter .exe (64-bit exe with some incompatible 32-bit dlls)
IQHyland
LeadtoolsLib
Leadtools.dll (32-bit!)
WebServicesWrapper
IQHyland .dll (only 64-bit gets built)
LeadtoolsLib
Leadtools.dll (64-bit)
LeadtoolsLib .dll (both 32 and 64 bit get built, why?)
WebServicesWrapper .dll (only 64-bit gets built)
The issue is that at the top level, the 32-bit .dlls from the LeadtoolsLib project are being included rather than the 64-bit dlls.
PDFConverter depends on IQHyland which depends on LeadtoolsLib, however PDFConverter also directly depends on LeadtoolsLib, which I imagine might be causing the issue, though I still don't know why it wouldn't get the 64-bit version of the dlls considering PDFConverter itself it a 64-bit target.
When I do the build, only 64-bit targets are built EXCEPT for LeadtoolsLib which has both 32-bit and 64-bit targets built. I don't know why the build thinks the 32-bit version is required by anything.
Any idea?
Edit:
Configuration manager
Not shown "WebServicesWrapper /Debug/x64/ build checked.
2>------ Build started: Project: WebServicesWrapper, Configuration: Debug x64 ------
1> LeadtoolsLib -> C:\Users\its-rowc\source\Workspaces\Imaging\LeadTools\bin\x64\Debug\IQLeadtools.dll
3>------ Build started: Project: IQHyland, Configuration: Debug x64 ------
2> WebServicesWrapper -> C:\Users\its-rowc\source\Workspaces\Imaging\WebServicesWrapper\bin\x64\Debug\WebServicesWrapper.dll
3> IQHyland -> C:\Users\its-rowc\source\Workspaces\Imaging\IQHyland\bin\x64\Debug\IQHyland.dll
4>------ Build started: Project: PDFConverter, Configuration: Debug x64 ------
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Leadtools", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
4> PDFConverter -> C:\Users\its-rowc\source\Workspaces\Imaging\PDFConverter\bin\x64\Debug\PDFConverter.dll
========== Build: 4 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
When solving this we needed to identify where dependencies are coming from.
There are 2 types of dependencies in Visual Studio: Assembly references (like the dependencies you specify by "Browse..." dialog), and Project references.
To see both types of references you can open Project -> Add Reference...
One way to see just the direct dependencies is to search for "HintPath" in all of project files, e.g. "git grep HintPath" might show something like:
...
myproject.csproj: <HintPath>...\path\to\LeadtoolsLib.dll</HintPath>
...
If you include both Project and Assembly reference for the same assembly, the system might prefer one over the other (in this case the 32-bit library direct reference was preferred for one of the projects).
I've been trying to install OpenMVG on windows 10 using this guide.
the build isn't passing.
https://github.com/openMVG/openMVG/blob/master/BUILD
first i built a vs 2017 compatible project using CMake
then compiled it using vs 2017.
here is the build output.
1>------ Build started: Project: INSTALL, Configuration: Release Win32 -----
1>-- Install configuration: "Release"
1>CMake Error at cmake_install.cmake:31 (file):
1> file INSTALL cannot make directory "C:/Program Files
1> (x86)/openMVG/include/openMVG_dependencies": No such file or directory
1>
1>
1>-- Installing: C:/Program Files (x86)/openMVG/include/openMVG_dependencies
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: The command "setlocal
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P cmake_install.cmake
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmErrorLevel
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" exited with code 1.
1>Done building project "INSTALL.vcxproj" -- FAILED.
2>------ Skipped Deploy: Project: ZERO_CHECK, Configuration: Release Win32 ------
2>Project not selected to build for this solution configuration
3>------ Skipped Deploy: Project: cxsparse, Configuration: Release Win32 ------
3>Project not selected to build for this solution configuration
4>------ Skipped Deploy: Project: fast, Configuration: Release Win32 ------
4>Project not selected to build for this solution configuration
5>------ Skipped Deploy: Project: lemon (OpenMVG\3rdParty\lemon\lemon), Configuration: Release Win32 ------
5>Project not selected to build for this solution configuration
6>------ Skipped Deploy: Project: lib_clp (OpenMVG\3rdParty\lib_clp\lib_clp), Configuration: Release Win32 ------
6>Project not selected to build for this solution configuration
7>------ Skipped Deploy: Project: openMVG_features, Configuration: Release Win32 ------
7>Project not selected to build for this solution configuration
8>------ Skipped Deploy: Project: stlplus, Configuration: Release Win32 ------
8>Project not selected to build for this solution configuration
9>------ Skipped Deploy: Project: zlib, Configuration: Release Win32 ------
9>Project not selected to build for this solution configuration
10>------ Skipped Deploy: Project: openMVG_numeric, Configuration: Release Win32 ------
10>Project not selected to build for this solution configuration
11>------ Skipped Deploy: Project: ceres (OpenMVG\3rdParty\ceres\ceres), Configuration: Release Win32 ------
11>Project not selected to build for this solution configuration
12>------ Skipped Deploy: Project: lib_CoinUtils (OpenMVG\3rdParty\lib_CoinUtils\lib_CoinUtils), Configuration: Release Win32 ------
12>Project not selected to build for this solution configuration
13>------ Skipped Deploy: Project: lib_Osi (OpenMVG\3rdParty\lib_Osi\lib_Osi), Configuration: Release Win32 ------
13>Project not selected to build for this solution configuration
14>------ Skipped Deploy: Project: lib_OsiClpSolver (OpenMVG\3rdParty\lib_OsiClpSolver\lib_OsiClpSolver), Configuration: Release Win32 ------
14>Project not selected to build for this solution configuration
15>------ Skipped Deploy: Project: tiff, Configuration: Release Win32 ------
15>Project not selected to build for this solution configuration
16>------ Skipped Deploy: Project: png, Configuration: Release Win32 ------
16>Project not selected to build for this solution configuration
17>------ Skipped Deploy: Project: openMVG_system, Configuration: Release Win32 ------
17>Project not selected to build for this solution configuration
18>------ Skipped Deploy: Project: openMVG_multiview, Configuration: Release Win32 ------
18>Project not selected to build for this solution configuration
19>------ Skipped Deploy: Project: jpeg, Configuration: Release Win32 ------
19>Project not selected to build for this solution configuration
20>------ Skipped Deploy: Project: openMVG_matching, Configuration: Release Win32 ------
20>Project not selected to build for this solution configuration
21>------ Skipped Deploy: Project: openMVG_image, Configuration: Release Win32 ------
21>Project not selected to build for this solution configuration
22>------ Skipped Deploy: Project: vlsift, Configuration: Release Win32 ------
22>Project not selected to build for this solution configuration
23>------ Skipped Deploy: Project: openMVG_kvld, Configuration: Release Win32 ------
23>Project not selected to build for this solution configuration
24>------ Skipped Deploy: Project: openMVG_matching_image_collection, Configuration: Release Win32 ------
24>Project not selected to build for this solution configuration
25>------ Skipped Deploy: Project: easyexif, Configuration: Release Win32 ------
25>Project not selected to build for this solution configuration
26>------ Skipped Deploy: Project: openMVG_sample_pano_converter, Configuration: Release Win32 ------
26>Project not selected to build for this solution configuration
27>------ Skipped Deploy: Project: openMVG_sample_robustHomography_guided, Configuration: Release Win32 ------
27>Project not selected to build for this solution configuration
28>------ Skipped Deploy: Project: openMVG_sample_robust_estimation_Homography, Configuration: Release Win32 ------
28>Project not selected to build for this solution configuration
29>------ Skipped Deploy: Project: openMVG_sample_multiview_robustHomography, Configuration: Release Win32 ------
29>Project not selected to build for this solution configuration
30>------ Skipped Deploy: Project: main_svgSample, Configuration: Release Win32 ------
30>Project not selected to build for this solution configuration
31>------ Skipped Deploy: Project: openMVG_sample_features_affine, Configuration: Release Win32 ------
31>Project not selected to build for this solution configuration
32>------ Skipped Deploy: Project: openMVG_main_exif_Parsing, Configuration: Release Win32 ------
32>Project not selected to build for this solution configuration
33>------ Skipped Deploy: Project: openMVG_multiview_test_data, Configuration: Release Win32 ------
33>Project not selected to build for this solution configuration
34>------ Skipped Deploy: Project: openMVG_sample_cameras_undistoBrown, Configuration: Release Win32 ------
34>Project not selected to build for this solution configuration
35>------ Skipped Deploy: Project: openMVG_sample_features_kvld, Configuration: Release Win32 ------
35>Project not selected to build for this solution configuration
36>------ Skipped Deploy: Project: openMVG_sample_features_siftPutative, Configuration: Release Win32 ------
36>Project not selected to build for this solution configuration
37>------ Skipped Deploy: Project: openMVG_sample_geodesy_show_exif_gps_position, Configuration: Release Win32 ------
37>Project not selected to build for this solution configuration
38>------ Skipped Deploy: Project: openMVG_sample_image_matching, Configuration: Release Win32 ------
38>Project not selected to build for this solution configuration
39>------ Skipped Deploy: Project: openMVG_sample_main_features_repeatability_dataset, Configuration: Release Win32 ------
39>Project not selected to build for this solution configuration
40>------ Skipped Deploy: Project: openMVG_sample_multiview_robustFundamental, Configuration: Release Win32 ------
40>Project not selected to build for this solution configuration
41>------ Skipped Deploy: Project: openMVG_sample_multiview_robustFundamental_guided, Configuration: Release Win32 ------
41>Project not selected to build for this solution configuration
42>------ Skipped Deploy: Project: openMVG_lInftyComputerVision, Configuration: Release Win32 ------
42>Project not selected to build for this solution configuration
43>------ Skipped Deploy: Project: openMVG_sfm, Configuration: Release Win32 ------
43>Project not selected to build for this solution configuration
44>------ Skipped Deploy: Project: openMVG_main_ListMatchingPairs, Configuration: Release Win32 ------
44>Project not selected to build for this solution configuration
45>------ Skipped Deploy: Project: openMVG_main_ColHarmonize, Configuration: Release Win32 ------
45>Project not selected to build for this solution configuration
46>------ Skipped Deploy: Project: openMVG_main_ComputeFeatures, Configuration: Release Win32 ------
46>Project not selected to build for this solution configuration
47>------ Skipped Deploy: Project: openMVG_main_ComputeMatches, Configuration: Release Win32 ------
47>Project not selected to build for this solution configuration
48>------ Skipped Deploy: Project: openMVG_main_ComputeSfM_DataColor, Configuration: Release Win32 ------
48>Project not selected to build for this solution configuration
49>------ Skipped Deploy: Project: openMVG_main_ComputeStructureFromKnownPoses, Configuration: Release Win32 ------
49>Project not selected to build for this solution configuration
50>------ Skipped Deploy: Project: openMVG_main_ConvertList, Configuration: Release Win32 ------
50>Project not selected to build for this solution configuration
51>------ Skipped Deploy: Project: openMVG_main_ConvertSfM_DataFormat, Configuration: Release Win32 ------
51>Project not selected to build for this solution configuration
52>------ Skipped Deploy: Project: openMVG_main_ExportCameraFrustums, Configuration: Release Win32 ------
52>Project not selected to build for this solution configuration
53>------ Skipped Deploy: Project: openMVG_main_ExportUndistortedImages, Configuration: Release Win32 ------
53>Project not selected to build for this solution configuration
54>------ Skipped Deploy: Project: openMVG_main_FrustumFiltering, Configuration: Release Win32 ------
54>Project not selected to build for this solution configuration
55>------ Skipped Deploy: Project: openMVG_main_GlobalSfM, Configuration: Release Win32 ------
55>Project not selected to build for this solution configuration
56>------ Skipped Deploy: Project: openMVG_main_IncrementalSfM, Configuration: Release Win32 ------
56>Project not selected to build for this solution configuration
57>------ Skipped Deploy: Project: openMVG_main_SfMInit_ImageListing, Configuration: Release Win32 ------
57>Project not selected to build for this solution configuration
58>------ Skipped Deploy: Project: openMVG_main_SfM_Localization, Configuration: Release Win32 ------
58>Project not selected to build for this solution configuration
59>------ Skipped Deploy: Project: openMVG_main_evalQuality, Configuration: Release Win32 ------
59>Project not selected to build for this solution configuration
60>------ Skipped Deploy: Project: openMVG_main_exportKeypoints, Configuration: Release Win32 ------
60>Project not selected to build for this solution configuration
61>------ Skipped Deploy: Project: openMVG_main_exportMatches, Configuration: Release Win32 ------
61>Project not selected to build for this solution configuration
62>------ Skipped Deploy: Project: openMVG_main_exportTracks, Configuration: Release Win32 ------
62>Project not selected to build for this solution configuration
63>------ Skipped Deploy: Project: openMVG_main_geodesy_registration_to_gps_position, Configuration: Release Win32 ------
63>Project not selected to build for this solution configuration
64>------ Skipped Deploy: Project: openMVG_main_openMVG2CMPMVS, Configuration: Release Win32 ------
64>Project not selected to build for this solution configuration
65>------ Skipped Deploy: Project: openMVG_main_openMVG2MESHLAB, Configuration: Release Win32 ------
65>Project not selected to build for this solution configuration
66>------ Skipped Deploy: Project: openMVG_main_openMVG2MVE2, Configuration: Release Win32 ------
66>Project not selected to build for this solution configuration
67>------ Skipped Deploy: Project: openMVG_main_openMVG2MVSTEXTURING, Configuration: Release Win32 ------
67>Project not selected to build for this solution configuration
68>------ Skipped Deploy: Project: openMVG_main_openMVG2NVM, Configuration: Release Win32 ------
68>Project not selected to build for this solution configuration
69>------ Skipped Deploy: Project: openMVG_main_openMVG2PMVS, Configuration: Release Win32 ------
69>Project not selected to build for this solution configuration
70>------ Skipped Deploy: Project: openMVG_main_openMVG2openMVS, Configuration: Release Win32 ------
70>Project not selected to build for this solution configuration
71>------ Skipped Deploy: Project: openMVG_sample_multiview_robustEssential, Configuration: Release Win32 ------
71>Project not selected to build for this solution configuration
72>------ Skipped Deploy: Project: openMVG_sample_multiview_robustEssential_ba, Configuration: Release Win32 ------
72>Project not selected to build for this solution configuration
73>------ Skipped Deploy: Project: openMVG_sample_multiview_robustEssential_spherical, Configuration: Release Win32 ------
73>Project not selected to build for this solution configuration
74>------ Skipped Deploy: Project: ALL_BUILD, Configuration: Release Win32 ------
74>Project not selected to build for this solution configuration
========== Build: 0 succeeded, 1 failed, 73 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 73 skipped ==========
and there is no deploy option enabled in the configuration manager for ALL_BUILD and INSTALL.
I have Jenkins up and running with one job, building one big VS solution using devenv.
Console log output looks like the normal VS output (changed example):
Microsoft (R) Visual Studio Version 9.0.101010.2.
Copyright (C) Microsoft Corp. All rights reserved.
1>------ Build started: Project: MyProject, Configuration: Release Win32 ------
2>------ Build started: Project: MyProject2, Configuration: Release Win32 ------
1>Compiling...
3>------ Build started: Project: MyProject3, Configuration: Release Win32 ------
3>Compiling...
3>Compiling...
1>Main.cpp...
2>Project.cpp...
Is there any possibility to have separated log (project by project) in Jenkins. Or maybe some plugin to track each project build log. Because when build fails it's hard to follow log tree to find all project occurrences.
There is Collapsing Console Sections plugin. It allows to define start/end points of "sections", once the log has those, they are marked on the console log and can be collapsed for easier reading
I ran into this problem recently (few days ago everything was working fine): Visual Studio 2012 started to refuse to build native WP8 projects.
Today, I created new solution from template 'Windows Phone Direct3D App (Native Only)' to check if my newly created DLLs will be properly supported on WP. I tried to compile this project, first without any changes or additional references - pure code generated by VS. However, it failed with given error.
I know very well what does it mean and what could be the possible reason, but I can't understand, hovewer, where does it come from in this case.
Weird thing: this only happens in 'Win32' configuration, ARM compiles fine:
1>------ Build started: Project: PhoneDirect3DApp, Configuration: Debug ARM ------
.......
Build Summary
-------------
00:11.742 - Success - Debug ARM - PhoneDirect3DApp\PhoneDirect3DApp.vcxproj
but Win32 does not:
1>------ Build started: Project: PhoneDirect3DApp, Configuration: Debug Win32 ------
.......
1>LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
Build Summary
-------------
00:09.725 - Failed - Debug Win32 - PhoneDirect3DApp\PhoneDirect3DApp.vcxproj
My standard (native C++/Win32) projects also work as expected (in both Win32 and x64 platform targets).
Project configuration: (in both platforms)
Linker::Input:
d3d11.lib;%(AdditionalDependencies)
Linker::Ignore:
ole32.lib;%(IgnoreSpecificDefaultLibraries)
VC++ Directories:
Microsoft.ARM.Cpp.User:
$(WP80ToolSetPath)lib\arm;$(WindowsSDK_LibraryPath_ARM);
Microsoft.Win32.Cpp.User:
$(VCInstallDir)lib;$(VCInstallDir)atlmfc\lib;$(WP80ToolSetPath)lib\x86;$(WindowsSDK_LibraryPath_x86)
Any ideas what else could be wrong or configured incorrectly? I'm running out of ideas, I have never seen something like this before.
By the way, I have noticed one more change: when I was trying to compile WP8 projects in ARM configurtion before, there was always an error, saying "building ARM application on desktop is not supported" (or something like that). Now ARM compiles with no problem. Is it normal?
Finally, I have found the reason of my problems: as I suspected, internal Visual Studio configuration has been broken.
I did all standard steps, that can be performed in case of LNK1104, however:
- kernel32.lib was in valid location
- all include and library directories was correct
- standard *.props files were attached to each project
However, the cause was lying elsewhere.
All paths are defined using standard macros. One of them is $(WindowsSDK80Path), which is used to build include/library paths. On my system, this macro was defined as
C:\Program Files (x86)\Windows Phone Kits\8.0
instead of
C:\Program Files (x86)\Windows Kits\8.0
And that's it. I do not know, when or how, this problem arosed. Visual Studio repair via orginal installer was sufficient method to fix everything. All projects compile now without any problems.
I am trying to test WFP(Windows Filtering Platform) sample provided by microsoft. While testing I got error.
While building it builds well: With following message:
Build started: Project: package (Package\package), Configuration: Win8 Debug Win32 ------
Inf2Cat task was skipped as there were no inf files to process
========== Build: 1 succeeded, 0 failed, 5 up-to-date, 0 skipped ==========
And While running the exe file I got an error. as:
"Cannot Verify Digital signature of the file.......".
how to resolve this.
Code From: msdn
I am using Windows 8 Release Preview machine with Visual studio 2012.