Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
CocoaPods
Home
+ new post
About this group
Join this group
Message from discussion Subspecs with multiple targets
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
ap4y  
View profile  
 More options Sep 20 2012, 2:22 pm
From: ap4y <3aka...@gmail.com>
Date: Thu, 20 Sep 2012 11:22:25 -0700 (PDT)
Local: Thurs, Sep 20 2012 2:22 pm
Subject: Re: Subspecs with multiple targets
Print | View thread | Show original | Report this message | Find messages by this author

Thanks for the answer. I have created new issue(*#535*). With "groups" I
meant that change from 0.12.0 changelog:
Make the Pods Xcode project prettier by namespacing subspecs in nested
groups. #466 <https://github.com/CocoaPods/CocoaPods/pull/466>

It have been working for me with 0.12.0. It's not a big deal, but was
really helpful sometimes. Thanks.

On Thursday, September 20, 2012 7:54:18 PM UTC+4, Eloy Durán wrote:

> This first issue definitely sounds like a bug (please file a ticket for
> that) the second issue I don’t really follow; what kind of ‘groups’ are you
> referring to? In the Xcode project?

> On Sep 20, 2012, at 11:00 AM, ap4y <3ak...@gmail.com <javascript:>>
> wrote:

> > Hi all,

> > I'm using latest cocoapods (0.14.0) and experiencing strange issue with
> subspecs and multiple targets(additional target for the unit test) in
> podfile. For example, such podfile:

> > pod 'RestKit'
> > target 'test123Tests', :exclusive => true do
> >   pod 'RestKit/Testing'
> > end

> > includes files from Testing subspec into the main target library. Also
> JSON subspec included into the tests target. Even more, subspec
> dependencies resolved correctly and only included into the desired target
> library, but other targets have sources from all subspecs, so they can't
> compile. Does anyone have the same issue? Or maybe I'm doing something
> wrong? Also in version 0.12.0 nested groups for subspecs was introduced, it
> was decent feature, but with 0.14.0 I don't have such groups. I can't find
> any mention in changelog also, so I wonder is it bug or not. Thanks!


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google