Bug 29584 - [Qt] Can not build for VS2008
Summary: [Qt] Can not build for VS2008
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2009-09-21 08:49 PDT by Tor Arne Vestbø
Modified: 2010-03-09 03:59 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tor Arne Vestbø 2009-09-21 08:49:36 PDT 
This bug report originated from Nokia internal issue QT-1853


--- Comments ---

Function: BuildSystem

Version: 4.5.2

Platform: Vista
Quad-core Intel, 4 meg, NVidia 9400 GT, Vista 64bit SP2.

Compiler: MSVC
VS 2005, VS 2008 sp1

Short description: Can not build for VS2008

Did:
configured Qt for build with VS2008, no Qt3 support and MySQL support. Configure runs sucessfully. When I run nmake I get errors:
QNetworkReplyHandler.obj : error LNK2001: unresolved external symbol "public: virtual struct QMetaObject const * __thiscall WebCore::FormDataIODevice::metaObject(void)const " (?metaObject@FormDataIODevice@WebCore@@UBEPBUQMetaObject@@XZ)
FrameLoaderClientQt.obj : error LNK2019: unresolved external symbol "protected: void __thiscall QWebPage::unsupportedContent(class QNetworkReply *)" (?unsupportedContent@QWebPage@@IAEXPAVQNetworkReply@@@Z) referenced in function "public: virtual void __thiscall WebCore::FrameLoaderClientQt::download(class WebCore::ResourceHandle *,struct WebCore::ResourceRequest const &,struct WebCore::ResourceRequest const &,class WebCore::ResourceResponse const &)" (?download@FrameLoaderClientQt@WebCore@@UAEXPAVResourceHandle@2@ABUResourceRequest@2@1ABVResourceResponse@2@@Z)

I get these errors when I build for either VS2005 or VS2008.

Expected to see:
Expected Qt to build for VS2008 or VS2005.

Got instead:
Compile errors

More details:
I can compile 2009.01 (and prior versions) with no issues. This issue was also reported as a comment on the blog post for ver 4.5.2.