On Thu, Oct 1, 2009 at 10:02 PM, Bala <[email protected]> wrote: > > Hi All, > > I tried to build chromium by following the Windows Build Instructions > for the first time today :). But unfortunately after opening the > chrome.sln file when I build the project, I got three build errors. > All the build errors reported the same problem "The binary is not a > valid windows image" > > Build O/P snippet: > 4>------ Build started: Project: chrome_dll, Configuration: Debug > Win32 ------ > 4>Embedding manifest... > 4>mt.exe : general error c101008d: Failed to write the updated > manifest to the resource of file ".\Debug\chrome.dll". The binary is > not a valid Windows image.
It turns out this failure is usually caused by anti-virus software activities. Disable it from scanning the source dir and try again. Huan > 4>Build log was saved at "file://C:\Bala\chromium\chromium.r27598\home > \chrome-svn\tarball\chromium\src\chrome\Debug\obj\chrome_dll > \BuildLog.htm" > 4>chrome_dll - 1 error(s), 0 warning(s) > 5>------ Build started: Project: generate_profile, Configuration: > Debug Win32 ------ > 5>Embedding manifest... > 5>mt.exe : general error c101008d: Failed to write the updated > manifest to the resource of file ".\Debug\generate_profile.exe". The > binary is not a valid Windows image. > 5>Build log was saved at "file://C:\Bala\chromium\chromium.r27598\home > \chrome-svn\tarball\chromium\src\chrome\Debug\obj\generate_profile > \BuildLog.htm" > 5>generate_profile - 1 error(s), 0 warning(s) > . > . > 7>------ Build started: Project: browser_tests_dll, Configuration: > Debug Win32 ------ > 7>Embedding manifest... > 7>mt.exe : general error c101008d: Failed to write the updated > manifest to the resource of file ".\Debug\browser_tests.dll". The > binary is not a valid Windows image. > 7>Build log was saved at "file://C:\Bala\chromium\chromium.r27598\home > \chrome-svn\tarball\chromium\src\chrome\Debug\obj\browser_tests_dll > \BuildLog.htm" > 7>browser_tests_dll - 1 error(s), 0 warning(s) > > After googling I found this link "http://www.wintellect.com/CS/blogs/ > jrobbins/archive/2009/01/24/the-case-of-the-corrupt-pe- > binaries.aspx". > > The workaround as stated in the blog is to change linker option from / > DYNAMICBASE:NO to /DYNAMICBASE. But the projects which reported errors > (chrome_dll, generate_profile and browser_test_dll) all have their > linker option set to /DYNAMICBASE only. > > So, please let me know how to resolve this build error? > > Waiting avidly for your reply :) > > Thanks, > Bala. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
