[
https://issues.apache.org/jira/browse/XERCESC-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186278#comment-16186278
]
Roger Leigh commented on XERCESC-2114:
--------------------------------------
[~mat] That's very interesting. If you have a chance to retry building 3.1
with VS vs 3.2 with CMake I'd be very interested what the compiler flag
discrepancy might be, so we can add back the missing flag (or remove the extra
flag etc.).
> Link failure with Xalan-C
> -------------------------
>
> Key: XERCESC-2114
> URL: https://issues.apache.org/jira/browse/XERCESC-2114
> Project: Xerces-C++
> Issue Type: Bug
> Components: Build
> Affects Versions: 3.2.0
> Environment: VS2013 on Windows Server 2012R2
> Reporter: Roger Leigh
>
> Testing latest rc1 with xalan and VS2013:
> [Build
> log|https://ci.openmicroscopy.org/view/Files/job/OME-FILES-CPP-DEV-merge-win-superbuild/VSARCH=x64,VSCONFIG=Release,VSVERSION=12,label=maxquant-ome/714/console]
> Using [this
> patch|https://raw.githubusercontent.com/ome/ome-cmake-superbuild/master/packages/xalan/patches/win-vc12.diff]
> to build Xalan with VS2013 (it's just the upgraded project files).
> {noformat}
> 12:29:32 (Link target) ->
> 12:29:32 XalanDiagnosticMemoryManager.obj : error LNK2001:
> unresolved external symbol "__declspec(dllimport) unsigned __int64 const
> `public: static unsigned __int64 __cdecl
> xercesc_3_2::XMLPlatformUtils::alignPointerForNewBlockAllocation(unsigned
> __int64)'::`2'::alignment"
> (__imp_?alignment@?1??alignPointerForNewBlockAllocation@XMLPlatformUtils@xercesc_3_2@@SA_K_K@Z@4_KB)
>
> [D:\build\OME-FILES-CPP-DEV-merge-win-superbuild\2a8f6256\build\xalan-source\c\Projects\Win32\VC12\AllInOne\AllInOne.vcxproj]
> 12:29:32 ..\..\..\..\Build\Win64\VC12\Release\Xalan-C_1_11.dll :
> fatal error LNK1120: 1 unresolved externals
> [D:\build\OME-FILES-CPP-DEV-merge-win-superbuild\2a8f6256\build\xalan-source\c\Projects\Win32\VC12\AllInOne\AllInOne.vcxproj]
> {noformat}
> Is there any incompatible change expected here? Could potentially be missing
> symbol exports or anything of that nature?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
