<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <ImportGroup Label="PropertySheets" /> <PropertyGroup Label="UserMacros"> <P4APIDIR>E:\Brian\Downloads\tools\perforce\p4api\r14.2\x86\p4api-2014.2.978861-vs2012_dyn</P4APIDIR> </PropertyGroup> <PropertyGroup /> <ItemDefinitionGroup /> <ItemGroup> <BuildMacro Include="P4APIDIR"> <Value>$(P4APIDIR)</Value> <EnvironmentVariable>true</EnvironmentVariable> </BuildMacro> </ItemGroup> </Project>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 11435 | brkarpala |
Fix p4win project so the project can both build and run in release and Unicode Release - Compiled in VS2012 - Was compiled against api r14.2 - Added PostBuildEvent to P4Win409 and P4Win411 to copy TargetFile to all four configurations. Can be done better, but good enough for now. - Both debug configurations receive a failed assertion starting up. Though fixed, that change will be moved to another changelist for it is adding to the code base (more information is returned from p4 info than expected) - Needed to disable GenerateManifest (seem to conflict even if all but one config was disabled) - Created a second P4EnvVariables (for debug). Not required, and probably can be handled better, but wanted the debug build to point to the debug api. |
||
#1 | 11099 | brkarpala | Integrate p4win from //guest/perforce_software/p4win/...@8562 | ||
//guest/perforce_software/p4win/gui/P4EnvVariables.props | |||||
#1 | 8562 | Matt Attaway |
These feet never stop running. Initial commit of the P4Win source code. To the best of our knowledge this compiles and runs using the 2013.3 P4 API and VS 2010. Expect a few changes as we refine the build process. Please post any build issues to the forums. |