Module: Pod::Specification::DSL

Extended by:
AttributeSupport
Included in:
Pod::Specification
Defined in:
lib/cocoapods-core/specification/dsl.rb,
lib/cocoapods-core/specification/dsl/attribute.rb,
lib/cocoapods-core/specification/dsl/deprecations.rb,
lib/cocoapods-core/specification/dsl/platform_proxy.rb,
lib/cocoapods-core/specification/dsl/attribute_support.rb,
lib/cocoapods-core/specification/root_attribute_accessors.rb

Overview

A specification describes a version of Pod library. It includes details about where the source should be fetched from, what files to use, the build settings to apply, and other general metadata such as its name, version, and description.

A stub specification file can be generated by the [pod spec create](commands.html#tab_spec-create) command.

The specification DSL provides great flexibility and dynamism. Moreover, the DSL adopts the [convention over configuration](en.wikipedia.org/wiki/Convention_over_configuration) and thus it can be very simple:

Pod::Spec.new do |s|
  s.name         = 'Reachability'
  s.version      = '3.1.0'
  s.license      = { :type => 'BSD' }
  s.homepage     = 'https://github.com/tonymillion/Reachability'
  s.authors      = { 'Tony Million' => '[email protected]' }
  s.summary      = 'ARC and GCD Compatible Reachability Class for iOS and OS X. Drop in replacement for Apple Reachability.'
  s.source       = { :git => 'https://github.com/tonymillion/Reachability.git', :tag => 'v3.1.0' }
  s.source_files = 'Reachability.{h,m}'
  s.framework    = 'SystemConfiguration'
  s.requires_arc = true
end

Defined Under Namespace

Modules: AttributeSupport, Deprecations, RootAttributesAccessors Classes: Attribute, PlatformProxy

Root specification A ‘root’ specification stores the information about the specific version of a library. The attributes in this group can only be written to on the ‘root’ specification, **not** on the ‘sub-specifications’. --- The attributes listed in this group are the only one which are required by a podspec. The attributes of the other groups are offered to refine the podspec and follow a convention over configuration approach. A root specification can describe these attributes either directly of through ‘[sub-specifications](#subspec)’. collapse

LICENSE_KEYS =

The keys accepted by the license attribute.

[:type, :file, :text].freeze
SOURCE_KEYS =

The keys accepted by the hash of the source attribute.

{
  :git => [:tag, :branch, :commit, :submodules],
  :svn => [:folder, :tag, :revision],
  :hg => [:revision],
  :http => nil,
  :path => nil
}.freeze

Platform A specification should indicate the platforms and the correspondent deployment targets on which the library is supported. If not defined in a subspec the attributes of this group inherit the value of the parent. collapse

PLATFORMS =

The names of the platforms supported by the specification class.

[:osx, :ios].freeze

Root specification A ‘root’ specification stores the information about the specific version of a library. The attributes in this group can only be written to on the ‘root’ specification, **not** on the ‘sub-specifications’. --- The attributes listed in this group are the only one which are required by a podspec. The attributes of the other groups are offered to refine the podspec and follow a convention over configuration approach. A root specification can describe these attributes either directly of through ‘[sub-specifications](#subspec)’. collapse

Platform A specification should indicate the platforms and the correspondent deployment targets on which the library is supported. If not defined in a subspec the attributes of this group inherit the value of the parent. collapse

Build settings In this group are listed the attributes related to the configuration of the build environment that should be used to build the library. If not defined in a subspec the attributes of this group inherit the value of the parent. collapse

File patterns Podspecs should be located at the **root** of the repository, and paths to files should be specified **relative** to the root of the repository as well. File patterns do not support traversing the parent directory ( `..` ). File patterns may contain the following wildcard patterns: --- ### Pattern: * Matches any file. Can be restricted by other values in the glob. * `*` will match all files * `c*` will match all files beginning with `c` * `*c` will match all files ending with `c` * `*c*` will match all files that have `c` in them (including at the beginning or end) Equivalent to `/.*/x` in regexp. **Note** this will not match Unix-like hidden files (dotfiles). In order to include those in the match results, you must use something like `{*,.*}`. --- ### Pattern: ** Matches directories recursively. --- ### Pattern: ? Matches any one character. Equivalent to `/.{1}/` in regexp. --- ### Pattern: [set] Matches any one character in set. Behaves exactly like character sets in Regexp, including set negation (`[^a-z]`). --- ### Pattern: {p,q} Matches either literal `p` or literal `q`. Matching literals may be more than one character in length. More than two literals may be specified. Equivalent to pattern alternation in regexp. --- ### Pattern: \ Escapes the next meta-character. --- ### Examples Consider these to be evaluated in the source root of [JSONKit](https://github.com/johnezang/JSONKit). "JSONKit.?" #=> ["JSONKit.h", "JSONKit.m"] "*.[a-z][a-z]" #=> ["CHANGELOG.md", "README.md"] "*.[^m]*" #=> ["JSONKit.h"] "*.{h,m}" #=> ["JSONKit.h", "JSONKit.m"] "*" #=> ["CHANGELOG.md", "JSONKit.h", "JSONKit.m", "README.md"] collapse

Subspecs A library can specify a dependency on either another library, a subspec of another library, or a subspec of itself. collapse

Multi-Platform support A specification can store values which are specific to only one platform. --- For example one might want to store resources which are specific to only iOS projects. spec.resources = "Resources/**/*.png" spec.ios.resources = "Resources_ios/**/*.png" collapse

Class Method Summary collapse

Methods included from AttributeSupport

attribute, root_attribute

Class Method Details

.attributes ⇒ Array<Attribute>

Returns The attributes of the class.

Returns:

  • (Array<Attribute>) —

    The attributes of the class.



7
8
9
 
# File 'lib/cocoapods-core/specification/dsl/attribute_support.rb', line 7

def self.attributes
  @attributes
end

Instance Method Details

#authors=(authors) ⇒ Object

The name and email addresses of the library maintainers, not the Podspec maintainer.

Examples:


spec.author = 'Darth Vader'


spec.authors = 'Darth Vader', 'Wookiee'


spec.authors = { 'Darth Vader' => '[email protected]',
                 'Wookiee'     => '[email protected]' }

Parameters:

  • authors (String, Hash{String=>String}) —

    the list of the authors of the library and their emails.



127
128
129
130
131
132
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 127

root_attribute :authors, {
  :types       => [String, Array, Hash],
  :container   => Hash,
  :required    => true,
  :singularize => true,
}

#compiler_flags=(flags) ⇒ Object

A list of flags which should be passed to the compiler.

Examples:


spec.compiler_flags = '-DOS_OBJECT_USE_OBJC=0', '-Wno-format'

Parameters:

  • flags (String, Array<String>) —

    A list of flags.



672
673
674
675
676
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 672

attribute :compiler_flags, {
  :container   => Array,
  :singularize => true,
  :inherited => true,
}

#default_subspec=(subspec_name) ⇒ Object

The name of the subspec that should be used as preferred dependency. If not specified a specifications requires all its subspecs as dependencies.

A Pod should make available the full library by default. Users can fine tune their dependencies, and exclude unneeded subspecs, once their requirements are known. Therefore, this attribute is rarely needed. It is intended to be used to select a default if there are ‘sub-specifications’ which provide alternative incompatible implementations, or to exclude modules rarely needed (especially if they trigger dependencies on other libraries).

Examples:

spec.default_subspec = 'Pod/Core'

Parameters:

  • subspec_name (String) —

    the name of the subspec that should be inherited as dependency.



1202
1203
1204
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1202

attribute :default_subspec, {
  :multi_platform => false,
}

#dependency(*args) ⇒ Object

Any dependency on other Pods or to a ‘sub-specification’.

Dependencies can specify versions requirements. The use of the approximate version indicator ‘~>` is recommended because it provides good control over the version without being too restrictive. For example, `~> 1.0.1` is equivalent to `>= 1.0.1` combined with `< 1.1`. Similarly, `~> 1.0` will match `1.0`, `1.0.1`, `1.1`, but will not upgrade to `2.0`.

Pods with overly restrictive dependencies limit their compatibility with other Pods.

Examples:

spec.dependency 'AFNetworking', '~> 1.0'

spec.dependency 'RestKit/CoreData', '~> 0.20.0'

spec.ios.dependency 'MBProgressHUD', '~> 0.5'



541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 541

def dependency(*args)
  name, *version_requirements = args
  if name == self.name
    raise Informative, "A specification can't require itself as a " \
      "subspec"
  end
  if @parent
    composed_name = ""
    @parent.name.split("/").each do |component|
      composed_name << component
      if name == composed_name
        raise Informative, "A subspec can't require one of its " \
          "parents specifications"
      else
        composed_name << "/"
      end
    end
  end
  unless version_requirements.all? { |req| req.is_a?(String) }
    raise Informative, "Unsupported version requirements"
  end
  attributes_hash["dependencies"] ||= {}
  attributes_hash["dependencies"][name] = version_requirements
end

#deployment_target=(*args) ⇒ Object

The minimum deployment targets of the supported platforms.

The following behavior is regarding the use of GCD and the ‘OS_OBJECT_USE_OBJC` flag. When set to `0`, it will allow code to use `dispatch_release()` on >= iOS 6.0 and OS X >= 10.8.

  • New libraries that do not require ARC don’t need to care about this issue at all.

  • New libraries that do require ARC and have a deployment target of >= iOS 6.0 or OS X >= 10.8:

    These *no longer* use ‘dispatch_release()` and should have the `OS_OBJECT_USE_OBJC` flag set to `1`.

    Note: this means that these libraries have to specify the

    deployment target in their specifications in order to have
CocoaPods set the flag to `1` and ensure proper behavior.

  • New libraries that do require ARC, but have a deployment target of < iOS 6.0 or OS X < 10.8:

    These contain ‘dispatch_release()` calls and as such need the `OS_OBJECT_USE_OBJC` flag set to `0`.

    Note: libraries that do not specify a platform version are

    assumed to have a deployment target of < iOS 6.0 or OS X < 10.8.

For more information, see: http://opensource.apple.com/source/libdispatch/libdispatch-228.18/os/object.h

Examples:


spec.ios.deployment_target = "6.0"


spec.osx.deployment_target = "10.8"

Parameters:

  • args (String) —

    The deployment target of the platform.

Raises:



495
496
497
498
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 495

def deployment_target=(*args)
  raise Informative, "The deployment target can be declared only per " \
    "platform."
end

#description=(description) ⇒ Object

A description of the Pod more detailed than the summary.

Examples:


spec.description = "                     Computes the meaning of life.\n                     Features:\n                     1. Is self aware\n                     ...\n                     42. Likes candies.\n                   DESC\n"

Parameters:

  • description (String) —

    A longer description of the Pod.



320
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 320

root_attribute :description

#documentation_url=(documentation_url) ⇒ Object

An optional URL for the documentation of the Pod which will be honored by CocoaPods web properties. Leaving it blank will default to a CocoaDocs generated URL for your library.

Examples:


spec.documentation_url = 'www.example.com/docs.html'

Parameters:

  • documentation_url (String) —

    The link of the web documentation of the Pod.



361
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 361

root_attribute :documentation_url

#exclude_files=(exclude_files) ⇒ Object

A list of file patterns that should be excluded from the other file patterns.

Examples:


spec.ios.exclude_files = "Classes/osx"


spec.exclude_files = "Classes/**/unused.{h,m}"

Parameters:

  • exclude_files (String, Array<String>) —

    the file patterns that the Pod should ignore.



1062
1063
1064
1065
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1062

attribute :exclude_files, {
  :container     => Array,
  :file_patterns => true,
}

#frameworks=(*frameworks) ⇒ Object

A list of system frameworks that the user’s target needs to link against.

Examples:


spec.ios.framework = 'CFNetwork'


spec.frameworks = 'QuartzCore', 'CoreData'

Parameters:

  • frameworks (String, Array<String>) —

    A list of framework names.



609
610
611
612
613
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 609

attribute :frameworks, {
  :container   => Array,
  :singularize => true,
  :inherited => true,
}

#header_dir=(dir) ⇒ Object

The directory where to store the headers files so they don’t break includes.

Examples:


spec.header_dir = 'Three20Core'

Parameters:

  • dir (String) —

    the headers directory.



760
761
762
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 760

attribute :header_dir, {
  :inherited => true
}

#header_mappings_dir=(dir) ⇒ Object

A directory from where to preserve the folder structure for the headers files. If not provided the headers files are flattened.

Examples:


spec.header_mappings_dir = 'src/include'

Parameters:

  • dir (String) —

    the directory from where to preserve the headers namespacing.



778
779
780
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 778

attribute :header_mappings_dir, {
  :inherited => true
}

#homepage=(homepage) ⇒ Object

The URL of the homepage of the Pod.

Examples:


spec.homepage = 'www.example.com'

Parameters:

  • homepage (String) —

    the URL of the homepage of the Pod.



219
220
221
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 219

root_attribute :homepage, {
  :required => true,
}

#ios ⇒ PlatformProxy

Provides support for specifying iOS attributes.

Examples:

spec.ios.source_files = "Classes/ios/**/*.{h,m}"

Returns:



1230
1231
1232
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1230

def ios
  PlatformProxy.new(self, :ios)
end

#libraries=(*libraries) ⇒ Object

A list of libraries that the user’s target (application) needs to link against.

Examples:


spec.ios.library = 'xml2'


spec.libraries = 'xml2', 'z'

Parameters:

  • libraries (String, Array<String>) —

    A list of library names.



653
654
655
656
657
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 653

attribute :libraries, {
  :container   => Array,
  :singularize => true,
  :inherited => true,
}

#license=(license) ⇒ Object

The license of the Pod.

Unless the source contains a file named ‘LICENSE.*` or `LICENCE.*`, the path of the license file or the integral text of the notice commonly used for the license type must be specified.

This information is used by CocoaPods to generate acknowledgement files (markdown and plist) which can be used in the acknowledgements section of the final application.

Examples:


spec.license = 'MIT'


spec.license = { :type => 'MIT', :file => 'MIT-LICENSE.txt' }


spec.license = { :type => 'MIT', :text => "                   Copyright 2012\n                   Permission is granted to...\n                 LICENSE\n               }\n"

Parameters:

  • license (String, Hash{Symbol=>String}) —

    The type of the license and the text of the grant that allows to use the library (or the relative path to the file that contains it).



200
201
202
203
204
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 200

root_attribute :license, {
  :container => Hash,
  :keys      => LICENSE_KEYS,
  :required  => true,
}

#name=(name) ⇒ Object

The name of the Pod.

Examples:


spec.name = 'AFNetworking'

Parameters:

  • name (String) —

    the name of the pod.



82
83
84
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 82

root_attribute :name, {
  :required => true,
}

#osx ⇒ PlatformProxy

Provides support for specifying OS X attributes.

Examples:

spec.osx.source_files = "Classes/osx/**/*.{h,m}"

Returns:



1241
1242
1243
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1241

def osx
  PlatformProxy.new(self, :osx)
end

#platform=(args) ⇒ Object

The platform on which this Pod is supported. Leaving this blank means the Pod is supported on all platforms.

Examples:


spec.platform = :osx, "10.8"


spec.platform = :ios


spec.platform = :osx

Parameters:

  • args (Array<Symbol, String>) —

    A tuple where the first value is the name of the platform, (either ‘:ios` or `:osx`) and the second is the deployment target.



440
441
442
443
444
445
446
447
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 440

def platform=(args)
  name, deployment_target = args
  if name
    attributes_hash["platforms"] = { name.to_s => deployment_target }
  else
    attributes_hash["platforms"] = {}
  end
end

#prefix_header_contents=(content) ⇒ Object

Any content to inject in the prefix header of the pod project.

This attribute is __not recommended__ as Pods should not pollute the prefix header of other libraries or of the user project.

Examples:


spec.prefix_header_contents = '#import <UIKit/UIKit.h>'


spec.prefix_header_contents = '#import <UIKit/UIKit.h>', '#import <Foundation/Foundation.h>'

Parameters:

  • content (String) —

    The contents of the prefix header.



718
719
720
721
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 718

attribute :prefix_header_contents, {
  :types => [Array, String],
  :inherited => true,
}

#prefix_header_file=(path) ⇒ Object

A path to a prefix header file to inject in the prefix header of the pod project.

This attribute is __not recommended__ as Pods should not pollute the prefix header of other libraries or of the user project.

Examples:


spec.prefix_header_file = 'iphone/include/prefix.pch'

Parameters:

  • path (String) —

    The path to the prefix header file.



742
743
744
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 742

attribute :prefix_header_file, {
  :inherited => true
}

#prepare_command=(command) ⇒ Object

A bash script that will be executed after the Pod is downloaded. This command can be used to create, delete and modify any file downloaded and will be ran before any paths for other file attributes of the specification are collected.

This command is executed before the Pod is cleaned and before the Pods project is created. The working directory is the root of the Pod.

If the pod is installed with the ‘:path` option this command will not be executed.

Examples:


spec.prepare_command = 'ruby build_files.rb'


spec.prepare_command = "                        sed -i 's/MyNameSpacedHeader/Header/g' ./**/*.h\n                        sed -i 's/MyNameOtherSpacedHeader/OtherHeader/g' ./**/*.h\n                   CMD\n"

Parameters:

  • command (String) —

    the prepare command of the pod.



393
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 393

root_attribute :prepare_command

#preserve_paths=(preserve_paths) ⇒ Object

Any file that should not be removed after being downloaded.

By default, CocoaPods removes all files that are not matched by any of the other file pattern.

Examples:


spec.preserve_path = "IMPORTANT.txt"


spec.preserve_paths = "Frameworks/*.framework"

Parameters:

  • preserve_paths (String, Array<String>) —

    the paths that should be not cleaned.



1089
1090
1091
1092
1093
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1089

attribute :preserve_paths, {
  :container     => Array,
  :file_patterns => true,
  :singularize   => true
}

#private_header_files=(private_header_files) ⇒ Object

A list of file patterns that should be used to mark private headers.

These patterns are matched against the public headers (or all the headers if no public headers have been specified) to exclude those headers which should not be exposed to the user project and which should not be used to generate the documentation.

Examples:


spec.private_header_files = "Headers/Private/*.h"

Parameters:

  • private_header_files (String, Array<String>) —

    the private headers of the Pod.



926
927
928
929
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 926

attribute :private_header_files, {
  :container => Array,
  :file_patterns => true,
}

#public_header_files=(public_header_files) ⇒ Object

A list of file patterns that should be used as public headers.

These are the headers that will be exposed to the user’s project and from which documentation will be generated. If no public headers are specified then all the headers are considered public.

Examples:


spec.public_header_files = "Headers/Public/*.h"

Parameters:

  • public_header_files (String, Array<String>) —

    the public headers of the Pod.



901
902
903
904
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 901

attribute :public_header_files, {
  :container => Array,
  :file_patterns => true,
}

#requires_arc=(flag) ⇒ Object

Wether the library requires ARC to be compiled. If true the ‘-fobjc-arc` flag will be added to the compiler flags.

The default value of this attribute is __transitioning__ from ‘false` to `true`, and in the meanwhile this attribute is always required.

Examples:


spec.requires_arc = true

Parameters:

  • flag (Bool) —

    whether the source files require ARC.



585
586
587
588
589
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 585

attribute :requires_arc, {
  :types => [TrueClass, FalseClass],
  :default_value => false,
  :inherited => true,
}

#resource_bundles=(*frameworks) ⇒ Object

This attribute allows to define the name and the file of the resource bundles which should be built for the Pod. They are specified as a hash where the keys represent the name of the bundles and the values the file patterns that they should include.

We strongly recommend library developers to adopt resource bundles as there can be name collisions using the resources attribute.

The names of the bundles should at least include the name of the Pod to minimize the change of name collisions.

To provide different resources per platform namespaced bundles must be used.

Examples:


spec.ios.resource_bundle = { 'MapBox' => 'MapView/Map/Resources/*.png' }


spec.resource_bundles = { 'MapBox' => ['MapView/Map/Resources/*.png'], 'OtherResources' => ['MapView/Map/OtherResources/*.png'] }

Parameters:

  • resource_bundles (Hash{String=>String}) —

    A hash where the keys are the names of the resource bundles and the values are their relative file patterns.



1008
1009
1010
1011
1012
1013
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1008

attribute :resource_bundles, {
  :types => [String, Array],
  :container => Hash,
  :file_patterns => true,
  :singularize => true,
}

#resources=(resources) ⇒ Object

A list of resources that should be copied into the target bundle.

We strongly recommend library developers to adopt [resource bundles](docs.cocoapods.org/specification.html#resources) as there can be name collisions using the resources attribute. Moreover resources specified with this attribute are copied directly to the client target and therefore they are not optimized by Xcode.

Examples:


spec.resource = "Resources/HockeySDK.bundle"


spec.resources = ["Images/*.png", "Sounds/*"]

Parameters:

  • resources (String, Array<String>) —

    The resources shipped with the Pod.



1038
1039
1040
1041
1042
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1038

attribute :resources, {
  :container     => Array,
  :file_patterns => true,
  :singularize   => true,
}

#screenshots=(screenshots) ⇒ Object

A list of URLs to images showcasing the Pod. Intended for UI oriented libraries.

Examples:


spec.screenshot  = "http://dl.dropbox.com/u/378729/MBProgressHUD/1.png"


spec.screenshots = [ "http://dl.dropbox.com/u/378729/MBProgressHUD/1.png",
                     "http://dl.dropbox.com/u/378729/MBProgressHUD/2.png" ]

Parameters:

  • screenshots (String) —

    An URL for the screenshot of the Pod.



341
342
343
344
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 341

root_attribute :screenshots, {
  :singularize    => true,
  :container      => Array,
}

#social_media_url=(social_media_url) ⇒ Object

The URL for the social media contact of the Pod, CocoaPods web services can use this.

For example, the @CocoaPodsFeed notifications will include the Twitter handle (shortening the description) if the URL is relative to Twitter. This does not necessarily have to be a Twitter URL, but only those are included in the Twitter @CocoaPodsFeed notifications.

Examples:


spec.social_media_url = 'https://twitter.com/cocoapods'


spec.social_media_url = 'https://groups.google.com/forum/#!forum/cocoapods'

Parameters:

  • social_media_url (String) —

    the social media URL.



157
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 157

root_attribute :social_media_url

#source=(source) ⇒ Object

The location from where the library should be retrieved.

Examples:

Specifying a Git source with a tag. This is how most OSS Podspecs work.


spec.source = { :git => 'https://github.com/AFNetworking/AFNetworking.git',
                :tag => 'v0.0.1' }

Using the version of the Pod to identify the Git commit and using submodules.


spec.source = { :git => 'https://github.com/AFNetworking/AFNetworking.git',
                :commit => "v#{spec.version}", :submodules => true }

Using the version of the Pod to identify the Git branch.


spec.source = { :git => 'https://github.com/AFNetworking/AFNetworking.git',
                :branch => "orta_fixes"}

Using Subversion with a tag.


spec.source = { :svn => "http://svn.code.sf.net/p/polyclipping/code", :tag => '4.8.8' }

Using Mercurial with the same revision as the spec’s semantic version string.


spec.source = { :hg => "https://bitbucket.org/dcutting/hyperbek", :revision => "#{s.version}" }

Using HTTP to download a compressed file of the code. It supports zip, tgz, bz2 and tar.


spec.source = { :http => "http://dev.wechatapp.com/download/sdk/WeChat_SDK_iOS_en.zip" }

Parameters:

  • source (Hash{Symbol=>String}) —

    The location from where the library should be retrieved.



269
270
271
272
273
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 269

root_attribute :source, {
  :container => Hash,
  :keys      => SOURCE_KEYS,
  :required  => true,
}

#source_files=(source_files) ⇒ Object

The source files of the Pod.

Examples:


spec.source_files = "Classes/**/*.{h,m}"


spec.source_files = "Classes/**/*.{h,m}", "More_Classes/**/*.{h,m}"

Parameters:

  • source_files (String, Array<String>) —

    the source files of the Pod.



877
878
879
880
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 877

attribute :source_files, {
  :container     => Array,
  :file_patterns => true,
}

#subspec(name, &block) ⇒ Object

Represents specification for a module of the library.

Subspecs participate on a dual hierarchy.

On one side, a specification automatically inherits as a dependency all it children ‘sub-specifications’ (unless a default subspec is specified).

On the other side, a ‘sub-specification’ inherits the value of the attributes of the parents so common values for attributes can be specified in the ancestors.

Although it sounds complicated in practice it means that subspecs in general do what you would expect:

pod 'ShareKit', '2.0'

Installs ShareKit with all the sharers like ‘ShareKit/Evernote`, `ShareKit/Facebook`, etc, as they are defined a subspecs.

pod 'ShareKit/Twitter',  '2.0'
pod 'ShareKit/Pinboard', '2.0'

Installs ShareKit with only the source files for ‘ShareKit/Twitter`, `ShareKit/Pinboard`. Note that, in this case, the ‘sub-specifications’to compile need the source files, the dependencies, and the other attributes defined by the root specification. CocoaPods is smart enough to handle any issues arising from duplicate attributes.

Examples:

Subspecs with different source files.


subspec "Twitter" do |sp|
  sp.source_files = "Classes/Twitter"
end

subspec "Pinboard" do |sp|
  sp.source_files = "Classes/Pinboard"
end

Subspecs referencing dependencies to other subspecs.


Pod::Spec.new do |s|
  s.name = 'RestKit'

  s.subspec 'Core' do |cs|
    cs.dependency 'RestKit/ObjectMapping'
    cs.dependency 'RestKit/Network'
    cs.dependency 'RestKit/CoreData'
  end

  s.subspec 'ObjectMapping' do |os|
  end
end

Nested subspecs.


Pod::Spec.new do |s|
  s.name = 'Root'

  s.subspec 'Level_1' do |sp|
    sp.subspec 'Level_2' do |ssp|
    end
  end
end



1171
1172
1173
1174
1175
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 1171

def subspec(name, &block)
  subspec = Specification.new(self, name, &block)
  @subspecs << subspec
  subspec
end

#summary=(summary) ⇒ Object

A short (maximum 140 characters) description of the Pod.

The description should be short, yet informative. It represents the tag line of the Pod and there is no need to specify that a Pod is a library (they always are).

The summary is expected to be properly capitalized and containing the correct punctuation.

Examples:


spec.summary = 'Computes the meaning of life.'

Parameters:

  • summary (String) —

    A short description of the Pod.



297
298
299
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 297

root_attribute :summary, {
  :required => true,
}

#vendored_frameworks=(*frameworks) ⇒ Object

The paths of the framework bundles that come shipped with the Pod.

Examples:


spec.ios.vendored_frameworks = 'Frameworks/MyFramework.framework'


spec.vendored_frameworks = 'MyFramework.framework', 'TheirFramework.framework'

Parameters:

  • vendored_frameworks (String, Array<String>) —

    A list of framework bundles paths.



948
949
950
951
952
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 948

attribute :vendored_frameworks, {
  :container => Array,
  :file_patterns => true,
  :singularize => true,
}

#vendored_libraries=(*frameworks) ⇒ Object

The paths of the libraries that come shipped with the Pod.

Examples:


spec.ios.vendored_library = 'Libraries/libProj4.a'


spec.vendored_libraries = 'libProj4.a', 'libJavaScriptCore.a'

Parameters:

  • vendored_libraries (String, Array<String>) —

    A list of library paths.



971
972
973
974
975
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 971

attribute :vendored_libraries, {
  :container => Array,
  :file_patterns => true,
  :singularize => true,
}

#version=(version) ⇒ Object

The version of the Pod. CocoaPods follows [semantic versioning](semver.org).

Examples:


spec.version = '0.0.1'

Parameters:

  • version (String) —

    the version of the Pod.



100
101
102
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 100

root_attribute :version, {
  :required => true,
}

#weak_frameworks=(*frameworks) ⇒ Object

A list of frameworks that the user’s target needs to weakly link against.

Examples:


spec.weak_framework = 'Twitter'

Parameters:

  • weak_frameworks (String, Array<String>) —

    A list of frameworks names.



629
630
631
632
633
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 629

attribute :weak_frameworks, {
  :container   => Array,
  :singularize => true,
  :inherited => true,
}

#xcconfig=(value) ⇒ Object

Any flag to add to the final xcconfig file.

Examples:


spec.xcconfig = { 'OTHER_LDFLAGS' => '-lObjC' }

Parameters:

  • value (Hash{String => String}) —

    A representing an xcconfig.



691
692
693
694
 
# File 'lib/cocoapods-core/specification/dsl.rb', line 691

attribute :xcconfig, {
  :container => Hash,
  :inherited => true,
}