<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:00:42 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CXX-892] Segregate Release vs. Debug build outputs</title>
                <link>https://jira.mongodb.org/browse/CXX-892</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;It appears that builds do not segregate outputs based on configuration (Release, Debug, ...). It would be nice if outputs were automatically segregated by configuration (either by directory name or some file naming scheme that distinguishes configurations) so that users (like me) don&apos;t accidentally overwrite build results when switching to a different configuration.&lt;/p&gt;

&lt;p&gt;I understand that the way cmake works the onus is on the developer to target different install directories based on  compiler version (VS2012, VS2013, VS2015, ...) and platform (Win32, Win64, ...) when configuring CMake.&lt;/p&gt;</description>
                <environment>Win 7, VS2015, CMake 3.5</environment>
        <key id="278852">CXX-892</key>
            <summary>Segregate Release vs. Debug build outputs</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="5" iconUrl="https://jira.mongodb.org/images/icons/priorities/trivial.svg">Trivial - P5</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="andrew.morrow@mongodb.com">Andrew Morrow</assignee>
                                    <reporter username="sxhickman">Steve Hickman</reporter>
                        <labels>
                    </labels>
                <created>Mon, 11 Apr 2016 16:20:19 +0000</created>
                <updated>Tue, 26 Apr 2016 12:51:57 +0000</updated>
                            <resolved>Tue, 26 Apr 2016 12:51:57 +0000</resolved>
                                    <version>3.0.1</version>
                                                    <component>Build</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="1246571" author="acm" created="Tue, 26 Apr 2016 12:51:57 +0000"  >&lt;p&gt;OK, thanks. I&apos;m going to close this out i favor of the other tickets. Please feel free to watch them for updates. The 3.1.0 release should be coming out sometime this summer with many small build improvements.&lt;/p&gt;</comment>
                            <comment id="1245749" author="sxhickman" created="Mon, 25 Apr 2016 18:05:19 +0000"  >&lt;p&gt;That&apos;s actually better.  Thx&lt;/p&gt;</comment>
                            <comment id="1245451" author="acm" created="Mon, 25 Apr 2016 15:24:26 +0000"  >&lt;p&gt;Thanks for clarifying. I actually want to take this a different direction, where we adorn the libraries with ABI tags, like boost does. I also want to add autolink (autolib?) support, so that the headers #pragma in an appropriately adorned name. Please see &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-521&quot; title=&quot;Support windows autolib and ABI tagged libraries&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-521&quot;&gt;&lt;del&gt;CXX-521&lt;/del&gt;&lt;/a&gt; (and, to a lesser extent, &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-816&quot; title=&quot;Different polyfill or library selections result in different ABIs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-816&quot;&gt;CXX-816&lt;/a&gt;). Under this scheme, the library names will vary with the build type automatically, and you will be able to install them all to the same installation prefix without conflict.&lt;/p&gt;

&lt;p&gt;Those tickets are currently slated for the 3.1.0 release.&lt;/p&gt;
</comment>
                            <comment id="1245415" author="sxhickman" created="Mon, 25 Apr 2016 15:02:24 +0000"  >&lt;p&gt;The installation directory.  &lt;/p&gt;

&lt;p&gt;Reasoning: The intermediate files (the build directory) can be overwritten because it will only be used to build the libraries. The installation directory/ies will be used when linking to the libraries. Users will sometimes want to link to different builds of the library (release vs. debug, 32 vs. 64 bit).&lt;/p&gt;</comment>
                            <comment id="1244932" author="acm" created="Sun, 24 Apr 2016 21:56:32 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=sxhickman&quot; class=&quot;user-hover&quot; rel=&quot;sxhickman&quot;&gt;sxhickman&lt;/a&gt; -&lt;/p&gt;

&lt;p&gt;Would you please clarify something for me: Is it the installation directory that you want to automatically disambiguate? Or the CMake build time directory (like where CMakeCache.txt is emitted)?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="1239200" author="sxhickman" created="Mon, 18 Apr 2016 19:37:49 +0000"  >&lt;p&gt;Not that was generated by CMake. However, I do this all the time in VS. My Output directory is typically defined as:&lt;br/&gt;
...&amp;lt;some root&amp;gt;....\$(PlatformToolset)\$(Platform)\$(Configuration)\&lt;br/&gt;
Note that&lt;br/&gt;
$(PlatformToolset) is defined in VS as the compiler version (e.g., v110 for VS2012, v140 for VS2015)&lt;br/&gt;
$(Platform) is defined in VS as either &apos;Win32&apos; or &apos;x64&apos;&lt;br/&gt;
$(Configuration) is defined in VS as either &apos;Debug&apos; or &apos;Release&apos;&lt;/p&gt;

&lt;p&gt;All you need to do is to use these macros in the string used to construct the output directory and VS will translate them when building.&lt;/p&gt;</comment>
                            <comment id="1238085" author="acm" created="Sun, 17 Apr 2016 15:45:42 +0000"  >&lt;p&gt;I&apos;m not entirely sure that this is possible. CMake generally treats the cwd as the output directory. Do you have a link to another project that exhibits the behavior that you want? Or let me know if I&apos;m misunderstanding what you are after here.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrd5db:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="978">Platforms 13 (04/22/16)</customfieldvalue>
    <customfieldvalue id="1055">Platforms 14 (05/13/16)</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>