将DLL与C ++项目中的其他输出文件分开

Question

I have a few dll projects in a solution (some depending on each other)

Project1 -> Properties -> Linker -> Input -> Additional Dependencies -> Project2.lib
Project1 -> Properties -> Linker -> General -> Additional Library Directories -> $(OutDir)

All is working fine.

Projects are Win7Debug Win32, Win7Debug x64..... and a Win32 project with only Debug and Release configurations.

I would like to have all dll's for Win32 placed in one folder and the x64 ones in another folder. So I added the x64 configuration for the Win32 project, and changed

Project1 -> Properties -> Linker -> General -> Output File -> $(SolutionDir)/i386/$(TargetName)/$(TargetExt)

(for Win32 - similar change for x64)

all seemed fine - and I only received dlls in the i386 folder... until I had to rebuild and got

Warning 23  warning MSB8012: 
TargetPath(C:\Path\Win7Debug\Project1.dll) does not match the Linker's OutputFile 
property value (C:\Path\i386\Project1.dll). This may cause your project to build 
incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and 
$(TargetExt) property values match the value specified in %(Link.OutputFile).   

This seems serious... and I don't want to have problems with missing dependencies (though everything seems to be working fine - and not just on my machine)

I changed

 Project1 -> Properties -> Configuration Properties -> General -> OutputDirectory -> $(SolutionDir)/i386

(to match the linker output) but now of course I get lib and exp files in the same folder as the dll's.

Other than using post build script, is there a way to separate the output files ?

Should I just leave the settings how I had them and disregard the warning above ?

Note : I am not trying to separate the Platform/configuration output files... That is done automagically using the default output directory.

What I need is, for each platform, to place only DLL files in one folder away from anything else. Redirecting Linker output (and leaving project output to standard) accomplishes that - I just am not sure if it is correct. Logically I should not have any build problems since I am giving linker all the info it needs...

Answer 1

The standard approach is to leave all these properties unchanged (inherit from parent). In this case linker will create DLL and LIB in $(Output) directory, which by default is $(SolutionDir)$(Configuration) . You just specify the name for x64 configuration, and all output files will be separated automatically.

The standard (and the easest) way to link import library is to add reference to corresponding project in Common Properties / References page. Nothing else is required.

If, for any reason, it is impossible, add $(SolutionDir)$(Configuration) to Configuration Properties / VC++ Directories / Library Directories and add library to be linked to Linker / Additional Dependencies . If there are many projects in your solution, you may create Property Sheet for the solution and specify Library Directories only once.