[webkit-help] Questions on Webkit compliation on Windows
Muralidharan Narayanan
murali.n at motorola.com
Tue Nov 23 02:42:03 PST 2010
Hello Brent and Adam,
I am unable to compile webkit on windows with VS 2005 expression edition.
Any suggestions about what to do for my error with regards to
".....msimg32.dll ignored; no imports found from msimg32.dll...."
This is the full link error
> LINK : warning LNK4199: /DELAYLOAD:msimg32.dll ignored; no imports found
from msimg32.dll
> WebCore_debug.lib(
RenderingAllInOne.obj) : error LNK2019: unresolved external symbol
__imp___CrtDbgReportW referenced in function "public: class
std::_Temp_iterator & __thiscall std::_Temp_iterator::operator=(class
WebCore::RenderLayer * const &)" (??4?$_Temp_iterator at PAVRenderLayer
@WebCore@@@std@@QAEAAV01 at ABQAVRenderLayer@WebCore@@@Z)
>
> WebCore_debug.lib(Gradient.obj) : error LNK2001: unresolved external
symbol __imp___CrtDbgReportW
> WebCore_debug.lib(CSSFontSelector.obj) : error LNK2001: unresolved
external symbol __imp___CrtDbgReportW
> WebCore_debug.lib(CSSGradientValue.obj) : error LNK2001: unresolved
external symbol __imp___CrtDbgReportW
>
>
D:\BACKUPS\Projects\BrowserSupport\WebKit-r70732\WebKitBuild\bin\WebKit.dll
: fatal error LNK1120: 1 unresolved externals
Thanks
Murali
On Fri, Nov 19, 2010 at 10:28 AM, Muralidharan Narayanan <
murali.n at motorola.com> wrote:
> Thanks Brent. See my comments below.
>
> On Fri, Nov 19, 2010 at 10:11 AM, Brent Fulgham <bfulgham at gmail.com>wrote:
>
>> Hi,
>>
>> On Nov 18, 2010, at 2:49 AM, Muralidharan Narayanan wrote:
>>
>> > Regarding the above I observed that there were differences with regards
>> to directories as well. For example, WebKitTools directory is present in
>> nightly source while it is not present in code checked out using svn
>> command. Don't know what to infer from that. It was just my observation.
>> Similarly for case of WebKit2 directory
>>
>> Something is not right here. The nightly checkout absolutely has the
>> WebKitTools directory. Perhaps something is going wrong during your
>> checkout?
>>
>>
>
> Thanks. Perhaps that may be the case. But I didn't try out repeated SVN
> checkout. if nightly source code is what I could use for development, I
> shall stick to that without concerning with others I guess.
> Thanks
>
>
>
>> > Ok. This seem to work. However, I am getting this below error. Do you
>> know what I should do to fix this.
>> > .........
>> > ........
>> > Compiling manifest to resources...
>> > Linking...
>> > Creating library
>> D:\BACKUPS\Projects\BrowserSupport\WebKit-r70732\WebKitBuild\lib\WebKit.lib
>> and object
>> D:\BACKUPS\Projects\BrowserSupport\WebKit-r70732\WebKitBuild\lib\WebKit.exp
>> >
>> > LINK : warning LNK4199: /DELAYLOAD:msimg32.dll ignored; no imports found
>> from msimg32.dll
>> > WebCore_debug.lib(RenderingAllInOne.obj) : error LNK2019: unresolved
>> external symbol __imp___CrtDbgReportW referenced in function "public: class
>> std::_Temp_iterator & __thiscall std::_Temp_iterator::operator=(class
>> WebCore::RenderLayer * const &)" (??4?$_Temp_iterator at PAVRenderLayer
>> @WebCore@@@std@@QAEAAV01 at ABQAVRenderLayer@WebCore@@@Z)
>> >
>> > WebCore_debug.lib(Gradient.obj) : error LNK2001: unresolved external
>> symbol __imp___CrtDbgReportW
>> > WebCore_debug.lib(CSSFontSelector.obj) : error LNK2001: unresolved
>> external symbol __imp___CrtDbgReportW
>> > WebCore_debug.lib(CSSGradientValue.obj) : error LNK2001: unresolved
>> external symbol __imp___CrtDbgReportW
>> >
>> >
>> D:\BACKUPS\Projects\BrowserSupport\WebKit-r70732\WebKitBuild\bin\WebKit.dll
>> : fatal error LNK1120: 1 unresolved externals
>> > Project : warning PRJ0018 : The following environment variables were not
>> found:
>> > $(PRODUCTION)
>>
>> It looks like it's not linking to the debug runtime library. Are you
>> building with Visual Studio? Are you using VS Express?
>>
>
>
> I am using VS 2005 Express edition.
>
>
> Thanks again
> Murali
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-help/attachments/20101123/2fefb852/attachment.html>
More information about the webkit-help
mailing list