[ 
https://issues.apache.org/jira/browse/QPID-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763652#action_12763652
 ] 

Steve Huston commented on QPID-2134:
------------------------------------

Note that this does not affect the wcf component - its solution/project files 
must remain since CMake currently doesn't have the support required to generate 
the C#, .NET things needed there, as I understand it.

> Remove Windows Visual Studio .sln/.vcproj files from svn; generate them 
> during release process
> ----------------------------------------------------------------------------------------------
>
>                 Key: QPID-2134
>                 URL: https://issues.apache.org/jira/browse/QPID-2134
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Build Tools, C++ Broker, C++ Client
>    Affects Versions: 0.6
>            Reporter: Steve Huston
>            Assignee: Steve Huston
>             Fix For: 0.6
>
>
> In 0.5 the qpid C++ release contains Visual Studio project (.vcproj) and 
> solution (.sln) files for building Qpid C++ on Windows. Subsequent to 0.5, 
> CMake was introduced. This obviates the need for maintaining 
> source-controlled vcproj/sln files. Those files are now generated during the 
> cmake configuration phase (as are Linux Makefiles, on that platform).
> Before 0.6 is released, the source-controlled vcproj/sln files should be 
> removed from the repository and the release process adjusted to incorporate 
> the cmake-generated files instead.
> Is there a script or defined procedure documented somewhere? On the wiki I 
> could find only a mention that one needs to be developed, and notes from how 
> previous RMs did it (apparantly by hand).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to