893010 - Fail to link xul.dll in VS 2013

Status: RESOLVED WORKSFORME

(Firefox for Metro Graveyard :: Build Config, defect)

Description

[Xavier Fung]

Cannot link xul.dll using Visual Studio 2013 and got unresolved symbols. This happens when --enable-metro is present in mozconfig.

253:07.34    Creating library xul.lib and object xul.exp
253:07.34
253:07.34 LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of othe
r libs; use /NODEFAULTLIB:library
253:07.34
253:07.34 LINK : warning LNK4199: /DELAYLOAD:VCCORLIB110.DLL ignored; no imports
 found from VCCORLIB110.DLL
253:07.34
253:07.34 nsWinMetroUtils.obj : error LNK2019: unresolved external symbol __imp_
_CryptProtectData@28 referenced in function "public: virtual enum tag_nsresult _
_stdcall mozilla::widget::nsWinMetroUtils::StoreSyncInfo(class nsAString_interna
l const &,class nsAString_internal const &,class nsAString_internal const &)" (?
StoreSyncInfo@nsWinMetroUtils@widget@mozilla@@UAG?AW4tag_nsresult@@ABVnsAString_
internal@@00@Z)
253:07.34
253:07.34 nsWinMetroUtils.obj : error LNK2019: unresolved external symbol __imp_
_CryptUnprotectData@28 referenced in function "public: virtual enum tag_nsresult
 __stdcall mozilla::widget::nsWinMetroUtils::LoadSyncInfo(class nsAString_intern
al &,class nsAString_internal &,class nsAString_internal &)" (?LoadSyncInfo@nsWi
nMetroUtils@widget@mozilla@@UAG?AW4tag_nsresult@@AAVnsAString_internal@@00@Z)
253:07.34
253:07.34 xul.dll : fatal error LNK1120: 2 unresolved externals

xul.dll can be linked if --enable-metro is not present in mozconfig.

Comment 1

[Xavier Fung]

Cannot reproduce this using VS2013 RC. Sorry for the bug spam.