<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:14:09 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>[CDRIVER-2092] Updated packaging for CocoaPods</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-2092</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;This was discussed a while ago in &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-691&quot; title=&quot;Update Podspec to 1.1.6 and enable SSL&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-691&quot;&gt;&lt;del&gt;CDRIVER-691&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I&apos;ve finally had a chance to try to integrate libbson into a Swift project. Using a fork of libbson@1.6.1 with the module map checked in, I was able to publish a prerelease pod and integrate it into an Objective-C project.&lt;/p&gt;

&lt;p&gt;In CocoaPods, all Swift builds, as well as framework-based Objective-C builds, use a module map to collect the interface exposed by a package. This was discussed in &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-691&quot; title=&quot;Update Podspec to 1.1.6 and enable SSL&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-691&quot;&gt;&lt;del&gt;CDRIVER-691&lt;/del&gt;&lt;/a&gt;. Here are a couple links with more information:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;a href=&quot;http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;&lt;a href=&quot;https://clang.llvm.org/docs/Modules.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://clang.llvm.org/docs/Modules.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;By default CocoaPods generates an umbrella header with all of the package&apos;s public header files and a module map around that. That doesn&apos;t work for libbson, since directly including e.g. bson-compat.h will result in a preprocessor error, &quot;Only &amp;lt;bson.h&amp;gt; can be included directly.&quot;&lt;/p&gt;

&lt;p&gt;The solution is to ship our own module map, referencing the library&apos;s umbrella header, and point CocoaPods to that.&lt;/p&gt;

&lt;p&gt;It needs to be checked in. Though it doesn&apos;t matter where it is in the repo. I opened this PR: &lt;a href=&quot;https://github.com/mongodb/libbson/pull/185&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/libbson/pull/185&lt;/a&gt;&lt;/p&gt;</description>
                <environment>OS X, iOS</environment>
        <key id="365836">CDRIVER-2092</key>
            <summary>Updated packaging for CocoaPods</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="jesse@mongodb.com">A. Jesse Jiryu Davis</assignee>
                                    <reporter username="paulmelnikow">Paul Melnikow</reporter>
                        <labels>
                    </labels>
                <created>Fri, 17 Mar 2017 20:38:43 +0000</created>
                <updated>Thu, 17 Aug 2017 18:38:34 +0000</updated>
                            <resolved>Mon, 20 Mar 2017 12:22:45 +0000</resolved>
                                                                    <component>libbson</component>
                    <component>packaging</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="1527997" author="jesse" created="Mon, 20 Mar 2017 12:22:45 +0000"  >&lt;p&gt;I&apos;m closing this issue - if there&apos;s anything we can do to help that does &lt;b&gt;not&lt;/b&gt; require us to maintain CocoaPods files in our repository, please let us know.&lt;/p&gt;</comment>
                            <comment id="1527283" author="jesse" created="Fri, 17 Mar 2017 23:59:11 +0000"  >&lt;p&gt;Hi Paul. Sorry, I really don&apos;t think it&apos;s a good idea to add something to the libbson repository that none of us understands or is committed to maintaining. Isn&apos;t it possible to maintain a CocoaPod for libbson and libmongoc without adding something to our repo? I think it&apos;s better if &lt;b&gt;you&lt;/b&gt; maintain the files you need to maintain to make a CocoaPod for libbson and libmongoc work correctly, in &lt;b&gt;your&lt;/b&gt; repository where you can change it whenever it&apos;s necessary to change.&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|hswvz3:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>