Home Dashboard Directory Help
Search

VS11 build/lib.exe will not allow the creation of c++ static library that calls WinRT apis (with 8175 & BETAREL) by evangineer


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 722313
Opened: 2/1/2012 2:25:25 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

VS11 IDE (build rules) and lib.exe prevent the creation of statically linked libraries that call WinRT apis. This is fundamental to separation of concerns, data hiding, and reuse.
Details
Sign in to post a comment.
Posted by evangineer on 4/6/2012 at 10:08 AM
Below the comment was left by 'Microsoft' that this will be fixed in the next major release. Does this mean VS12 or will a build of VS11 fix this issue?

this defect (decision) to prevent the creation of static libraries is very disruptive to our development for Win8 and Metro.
Posted by OmniGSoft on 3/2/2012 at 9:54 AM
Hi VS 11 Team:
It looks like this bug is still in the VS 11 Beta.
When we build a static library with WinRT calls in the source code, the compiler still gives error message "error LNK1326: archiving OBJ compiled with /ZW into static lib is not supported".

Is there a work around for this?
OmniGSoft
Posted by thefans on 3/2/2012 at 8:30 AM
Is this fix included in Visual Studio 11 Beta? Because the problem still exists.
Posted by Microsoft on 2/9/2012 at 8:36 PM
We have resolved the problem and the fix will be included in our next major release. Thank you very much for the report.
Posted by MS-Moderator07 [Feedback Moderator] on 2/1/2012 at 6:19 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 2/1/2012 at 2:43 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.