A static library that's used in a Universal Windows Platform app can contain ISO-standard C++ code, including STL types, and also calls to Win32 APIs that are not excluded from the Universal Windows Platform app platform. A static library consumes Windows Runtime components and may create Windows Runtime components with certain restrictions.
Creating static libraries
To create a static library for use in a Universal Windows Platform app
On the menu bar, choose File > New > Project > Blank Static Library for Universal Windows Platform apps.
In Solution Explorer, open the shortcut menu for the project and then choose Properties. In the Properties dialog box, on the Configuration Properties > General page, set Universal Windows Platform app support to Yes.
On the Configuration Properties > C/C++ page, set Consume Windows Runtime Extension to Yes (/ZW).
When you compile a new static library, if you make a call to a Win32 API that's excluded for Universal Windows Platform apps, the compiler will raise error C3861, “Identifier not found.” To look for an alternative method that's supported for the Windows Runtime, see Alternatives to Windows APIs in Windows Store apps.
If you add a C++ static library project to a Universal Windows Platform app solution, you might have to update the library project’s property settings so that the Universal Windows Platform support property is set to Yes. Without this setting, the code builds and links, but an error occurs when you attempt to verify the app for the Windows Store. The static lib should be compiled with the same compiler settings as the project that consumes it.
If you consume a static library that creates public
refclasses, public interface classes, or public value classes, the linker raises this warning:
warning LNK4264: archiving object file compiled with /ZW into a static library; note that when authoring Windows Runtime types it is not recommended to link with a static library that contains Windows Runtime metadata.
You can safely ignore the warning only if the static library is not producing Windows Runtime components that are consumed outside the library itself. If the library doesn’t consume a component that it defines, then the linker can optimize away the implementation even though the public metadata contains the type information. This means that public components in a static library will compile but will not activate at run time. For this reason, any Windows Runtime component that's intended for consumption by other components or apps must be implemented in a dynamic-link library (DLL).