![]() ![]() The answer is a property sheet file for you library: $(MSBuildThisFileDirectory) $(::IsMatch($(Configuration), 'ebug')) 圆4 U D $(CodejockDir)\Bin\vc$(PlatformToolsetVersion)$(CodejockArchSuffix) ToolkitPro1531vc$(PlatformToolsetVersion)$(CodejockArchSuffix)$(UnicodeSuffix)$(DebugSuffix) $(CodejockDir)\Source $(IncludePath) $(CodejockDir)\Lib\vc$(PlatformToolsetVersion)$(CodejockArchSuffix) $(LibraryPath) $(CodejockDir)\Source $(SourcePath) $(CodejockBinDir) %(LocalDebuggerEnvironment) Libraries\Codejock xcopy /Y "%(FullPath)" "$(OutDir)" $(OutDir)\$(CodejockItemName).dll Libraries\Codejock xcopy /Y "%(FullPath)" "$(OutDir)" $(OutDir)\$(CodejockItemName).pdb $(CodejockDir)\Source %(AdditionalIncludeDirectories) $(CodejockDir) Toolkit Pro is a good example of such a library. ![]() Let's say you have reusable library in your (D)VCS repository. Sure you google the solution and end up having Custom Build Tools or The application and realize you must copy dll/pdb/whatever files to your outputĭirectory. You need to specify include paths, library ![]() Adding libraries to your Visual Studio C projects might be cumbersome if youĪint doing "Hello World" applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |