Windows cpp examples: exe files go to different directories based on
configuration and platform
-----------------------------------------------------------------------------------------------
Key: QPID-3146
URL: https://issues.apache.org/jira/browse/QPID-3146
Project: Qpid
Issue Type: Improvement
Reporter: Chuck Rolke
The project files for the cpp examples use inconsistent path specs for the
output.
For instance, messaging client uses:
messaging\messaging_client.vcproj: OutputDirectory="."
messaging\messaging_client.vcproj: OutputDirectory="Release"
messaging\messaging_client.vcproj:
OutputDirectory="$(PlatformName)\$(ConfigurationName)"
messaging\messaging_client.vcproj:
OutputDirectory="$(PlatformName)\$(ConfigurationName)"
where $(PlatformName) is "win32" or "x64", and $(ConfigurationName) is "debug"
or "release".
In practice this translates to the file client.exe landing in
messaging\
messaging\Release\
messaging\x64\debug\
messaging\x64\release\
I propose to modify the vcproj files so that the output directory in all cases
is $(PlatformName)\$(ConfigurationName). In the vcproj file the OutputDirectory
value is always "$(PlatformName)\$(ConfigurationName)".
To find a specific built executable you then need to navigate to
cpp\examples\messaging, then to win32 or x64, and then to debug or release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
