What is proper naming convention for MSVC dlls, static libraries and import libraries

Question

What is standard or \"most-popular\" naming convention for MSVC library builds.

For example, for following platforms library foo has these conventions:<

Answer 1

As far as I know there still aren't any conventions with regards to this. Here's an example of how I do it:

{Project}{SubModule}{Platform}{Architecture}{CompilerRuntime}_{BuildType}.lib/dll

The full filename shall be lowercase only and shall only contain alphanumerics with predesignated underscores. The submodule field, including its leading underscore, is optional.

Project: holds project name/identifier. Preferably as short as possible. ie "dna"

SubModule: optional. holds module name. Preferably as short as possible. ie "dna_audio"

Platform: identifies the platform the binary is compiled for. ie "win32" (Windows), "winrt", "xbox", "android".

Architecture: describes the architecture the binary is compiled for. ie "x86", "x64", "arm". There where architecture names are equal for various bitnesses use its name followed by the bitness. ie. "name16", "name32", "name64"

CompilerRuntime: optional. Not all binaries link to a compiler runtime, but if they do, it's included here. ie "vc90" (Visual Studio 2008), "gcc". Where applicable apartment can be included ie "vc90mt"

BuildType: optional. This can hold letters (in any order desired), each which tell something about the build-specifics. d=debug (omitted if release) t=static (omitted if dynamic) a=ansi (omitted if unicode)

Examples (assuming a project named "DNA"): dna_win32_x86_vc90.lib/dll dna_win32_x64_vc90_d.lib/dll dna_win32_x86_vc90_sd.lib dna_audio_win32_x64_vc90.lib/dll dna_audio_winrt_x64_vc110.lib/dll