> I have these entries in my project PCH, do I need to do anything so that these imports are transferred when installing the PCH?

> #import <Foundation/Foundation.h>
> #import <UIKit/UIKit.h>
> #import <CoreText/CoreText.h>

> I have a DTCoreTextFontOverrides.plist that should be transferred as a resource, I add that to resources, right?

> In the above mentioned podspec, I have some provision to add ALLOW_IPHONE_SPECIAL_CASES to the PCH file, but this is no longer necessary. How do I get rid of that without interfering with the imports mentioned in the first question?

>> I have these entries in my project PCH, do I need to do anything so that these imports are transferred when installing the PCH?

>> #import <Foundation/Foundation.h>
>> #import <UIKit/UIKit.h>
>> #import <CoreText/CoreText.h>

> Only the last would have to be added.

> Nowadays you can completely replace https://github.com/Cocoanetics/DTCoreText/blob/master/DTCoreText.pods... by using the `prefix_header_contents` attribute:

>  s.prefix_header_contents = '#import <CoreText/CoreText.h>'

>> I have a DTCoreTextFontOverrides.plist that should be transferred as a resource, I add that to resources, right?

> Yup. If you have just one file you can also use the alias `resource`.

>> In the above mentioned podspec, I have some provision to add ALLOW_IPHONE_SPECIAL_CASES to the PCH file, but this is no longer necessary. How do I get rid of that without interfering with the imports mentioned in the first question?

> With the aforementioned prefix_header_contents example, the ALLOW_IPHONE_SPECIAL_CASES won’t be added.

> Eloy

On Mon, Jan 7, 2013 at 12:40 PM, Oliver Drobnik <oli...@drobnik.com> wrote:
> Hi,

> my DTCoreText project requires two additional libraries which are
> represented by two static library targets in DTFoundation.

> This is where I got to, but now I am stuck:

> https://github.com/Cocoanetics/DTCoreText/commit/100468c67dd8a1ffe6f8...

> how would I represent this dependency? Would I make a pod spec per static
> library target?

> I specifically need DTVersion.m+h and DTHTMLParser.m+h from the project.

> kind regards
> Oliver Drobnik

> Hello Oliver!

> I'm not 100% sure, but as possible solution you can declare DTFoundation as a spec with lots of small subspecs like RestKit do: https://github.com/CocoaPods/Specs/blob/master/RestKit/0.20.0pre6/Res...

> And after that to specify the needed subspecs as dependencies for DTCoreText.

> I will be glad if somebody else will proof my answer because I'm not 100% sure) Thanks.

> On Mon, Jan 7, 2013 at 12:40 PM, Oliver Drobnik <oli...@drobnik.com> wrote:
> Hi,

> my DTCoreText project requires two additional libraries which are represented by two static library targets in DTFoundation.

> This is where I got to, but now I am stuck:
> https://github.com/Cocoanetics/DTCoreText/commit/100468c67dd8a1ffe6f8...

> how would I represent this dependency? Would I make a pod spec per static library target?

> I specifically need DTVersion.m+h and DTHTMLParser.m+h from the project.

> kind regards
> Oliver Drobnik

> --
> Best regards,
> Victor Ilyukevich.
> @yas375

> Could you please have a look and tell me if these pod spec changes are correct?

> https://github.com/Cocoanetics/DTCoreText/commit/260ec697410e6b8797a0...

> - basically it's a new tag
> - The prefix_header_contents should replace the file.puts
> - I am uncertain about the spec.resources, do I need a path there?

> kind regards
> Oliver Drobnik

> Am 21.09.2012 um 18:34 schrieb Eloy Durán <eloy.de.en...@gmail.com>:

>>> I have these entries in my project PCH, do I need to do anything so that these imports are transferred when installing the PCH?

>>> #import <Foundation/Foundation.h>
>>> #import <UIKit/UIKit.h>
>>> #import <CoreText/CoreText.h>

>> Only the last would have to be added.

>> Nowadays you can completely replace https://github.com/Cocoanetics/DTCoreText/blob/master/DTCoreText.pods... by using the `prefix_header_contents` attribute:

>> s.prefix_header_contents = '#import <CoreText/CoreText.h>'

>>> I have a DTCoreTextFontOverrides.plist that should be transferred as a resource, I add that to resources, right?

>> Yup. If you have just one file you can also use the alias `resource`.

>>> In the above mentioned podspec, I have some provision to add ALLOW_IPHONE_SPECIAL_CASES to the PCH file, but this is no longer necessary. How do I get rid of that without interfering with the imports mentioned in the first question?

>> With the aforementioned prefix_header_contents example, the ALLOW_IPHONE_SPECIAL_CASES won’t be added.

>> Eloy

> Looks good to me! Be sure to use the linting features of the `pod` CLI tool and possibly by testing the integration in a dumb app.

> On Jan 7, 2013, at 9:30 AM, Oliver Drobnik <oli...@drobnik.com> wrote:

>> Could you please have a look and tell me if these pod spec changes are correct?

>> https://github.com/Cocoanetics/DTCoreText/commit/260ec697410e6b8797a0...

>> - basically it's a new tag
>> - The prefix_header_contents should replace the file.puts
>> - I am uncertain about the spec.resources, do I need a path there?

>> kind regards
>> Oliver Drobnik

>> Am 21.09.2012 um 18:34 schrieb Eloy Durán <eloy.de.en...@gmail.com>:

>>>> I have these entries in my project PCH, do I need to do anything so that these imports are transferred when installing the PCH?

>>>> #import <Foundation/Foundation.h>
>>>> #import <UIKit/UIKit.h>
>>>> #import <CoreText/CoreText.h>

>>> Only the last would have to be added.

>>> Nowadays you can completely replace https://github.com/Cocoanetics/DTCoreText/blob/master/DTCoreText.pods... by using the `prefix_header_contents` attribute:

>>> s.prefix_header_contents = '#import <CoreText/CoreText.h>'

>>>> I have a DTCoreTextFontOverrides.plist that should be transferred as a resource, I add that to resources, right?

>>> Yup. If you have just one file you can also use the alias `resource`.

>>>> In the above mentioned podspec, I have some provision to add ALLOW_IPHONE_SPECIAL_CASES to the PCH file, but this is no longer necessary. How do I get rid of that without interfering with the imports mentioned in the first question?

>>> With the aforementioned prefix_header_contents example, the ALLOW_IPHONE_SPECIAL_CASES won’t be added.

>>> Eloy

> I have recently added DTFoundation 1.1.0 podspec.

> Is this reference in DTCoreText correct? I only changed the 1.0 to 1.1. Does that automatically catch all point release versions like 1.1.1?

> Pod::Spec.new do |spec|
>   spec.name         = 'DTCoreText'
>   spec.version      = '1.3.2'
>   spec.platform     = :ios, '4.3'
>   spec.license      = 'BSD'
>   spec.source       = { :git => 'https://github.com/Cocoanetics/DTCoreText.git', :tag => spec.version.to_s }
>   spec.source_files = 'Core/Source/*.{h,m,c}'
>   spec.dependency 'DTFoundation/Core', '~>1.1'
>   spec.dependency 'DTFoundation/DTHMLParser', '~>1.0'
>   spec.frameworks   = 'MediaPlayer', 'QuartzCore', 'CoreText', 'CoreGraphics', 'ImageIO'
>  [...]

> It allows any version in the last specified digit. I.e. you’ll have to adjust it to '~> 1.1.0'.

> - Eloy

> On Mar 5, 2013, at 7:43 PM, Oliver Drobnik <oli...@drobnik.com> wrote:

>> I have recently added DTFoundation 1.1.0 podspec.

>> Is this reference in DTCoreText correct? I only changed the 1.0 to 1.1. Does that automatically catch all point release versions like 1.1.1?

>> Pod::Spec.new do |spec|
>>   spec.name         = 'DTCoreText'
>>   spec.version      = '1.3.2'
>>   spec.platform     = :ios, '4.3'
>>   spec.license      = 'BSD'
>>   spec.source       = { :git => 'https://github.com/Cocoanetics/DTCoreText.git', :tag => spec.version.to_s }
>>   spec.source_files = 'Core/Source/*.{h,m,c}'
>>   spec.dependency 'DTFoundation/Core', '~>1.1'
>>   spec.dependency 'DTFoundation/DTHMLParser', '~>1.0'
>>   spec.frameworks   = 'MediaPlayer', 'QuartzCore', 'CoreText', 'CoreGraphics', 'ImageIO'
>>  [...]

> --
> You received this message because you are subscribed to a topic in the Google Groups "CocoaPods" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/cocoapods/8S_39J0soog/unsubscribe?h....
> To unsubscribe from this group and all its topics, send an email to cocoapods+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

> why?

> I don't care about the third digits and any future fixes should be picked up as well as long as it is in the 1.1.x range.

> On 14.03.2013, at 12:14, Eloy Durán <eloy.de.en...@gmail.com> wrote:

>> It allows any version in the last specified digit. I.e. you’ll have to adjust it to '~> 1.1.0'.

>> - Eloy

>> On Mar 5, 2013, at 7:43 PM, Oliver Drobnik <oli...@drobnik.com> wrote:

>>> I have recently added DTFoundation 1.1.0 podspec.

>>> Is this reference in DTCoreText correct? I only changed the 1.0 to 1.1. Does that automatically catch all point release versions like 1.1.1?

>>> Pod::Spec.new do |spec|
>>>   spec.name         = 'DTCoreText'
>>>   spec.version      = '1.3.2'
>>>   spec.platform     = :ios, '4.3'
>>>   spec.license      = 'BSD'
>>>   spec.source       = { :git => 'https://github.com/Cocoanetics/DTCoreText.git', :tag => spec.version.to_s }
>>>   spec.source_files = 'Core/Source/*.{h,m,c}'
>>>   spec.dependency 'DTFoundation/Core', '~>1.1'
>>>   spec.dependency 'DTFoundation/DTHMLParser', '~>1.0'
>>>   spec.frameworks   = 'MediaPlayer', 'QuartzCore', 'CoreText', 'CoreGraphics', 'ImageIO'
>>>  [...]

>> --
>> You received this message because you are subscribed to a topic in the Google Groups "CocoaPods" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/cocoapods/8S_39J0soog/unsubscribe?h....
>> To unsubscribe from this group and all its topics, send an email to cocoapods+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.

> --
> You received this message because you are subscribed to the Google Groups "CocoaPods" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cocoapods+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.