Bot releases are hidden (Show)
Published by segiddins almost 10 years ago
prefix_header
andprepare_command
to aide their declaration as a here document (similarly toPublished by segiddins almost 10 years ago
--no-shallow
option to perform a fullpod init
to save Xcode project file in Podfile when one was supplied.pod lib create
command.pod repo remove
silently handling permission errors.pod push
now properly checks that the repo has changed before attempting+
) inPublished by segiddins almost 10 years ago
CocoaPods
• CocoaPods-core
• cocoapods-downloader
podfile_info
is now a plugin offered by CocoaPods.pod ipc spec
command returns a JSON representation and the YAML.podspec.json
extension.pod try
the easiest way to test the example project of a pod.pod search <query>
command now supports regular expressions--full
.pod push
command will now silently test the upcoming CocoaPods trunkpod search <query>
command now supports searching on cocoapods.org--web
. Options --ios
and --osx
arepod search <query>
command now supports multiword queries when using--web
option.pod lib lint
not being able to find the$(SDKROOT)/Developer/Library/Frameworks
is used for iOS and$(DEVELOPER_LIBRARY_DIR)/Frameworks
is used for OS X.pod search
. In addition, the flag --silent
is no longer supported.framework
QuartzCore.framework
)..a
or .dylib
z.dylib
). It will also display an error if it begins with lib
libxml
)./tmp
being a symlink to /private/tmp
.pod lib lint
, causing it to fail when theprefix_header_*
or when the pod headers imported headers#import <MyPod/Header.h>
).pod lib create
.Published by segiddins almost 10 years ago
CocoaPods
• CocoaPods-core
• CLAide
CLAide now supports gem plugins. An example CocoaPods plugin can be found at
open_pod_bay.
As of yet there are no promises made yet on the APIs, so try to fail as
gracefully as possible in case a CocoaPods update breaks your usage. In these
cases, also please let us know what you would need, so we can take this into
account when we do finalize APIs.
xcassets
with actool
now uses UNLOCALIZED_RESOURCES_FOLDER_PATH
PRODUCT_NAME.WRAPPER_EXTENSION
as output directory as it is moreWRAPPER_NAME
.WRAPPER_EXTENSION
actool
is available when compilingxcassets
. This prevents build failures of Xcode 5 projects on Travis CI (orpod push
command is now more specific about the branch it pushes to.Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
pod lib create
if the name ofPublished by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
link_with
method of the Podfile DSL no longer needlink_with ['target1', 'target2']
canlink_with 'target1', 'target2'
.pod repo
now support a remove ['repo_name']
command.Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
CocoaPods now creates and hides the schemes of its targets after every
installation. The schemes are not shared because the flag which keeps track
whether they should be visible is a user only flag. The schemes are still
present and to debug a single Pod it is possible to make its scheme visible
in the Schemes manager of Xcode. This is rarely needed though because the
user targets trigger the compilation of the Pod targets.
Fabio Pelosin
#1185
Installations which don't integrate a user target (lint subcommands and
--no-integrate
option) now set the architecture of OS X Pod targets to
$(ARCHS_STANDARD_64_BIT)
(Xcode 4 default value for new targets). This
fixes lint issues with Xcode 4.
Fabio Pelosin
#1185
Further improvements to the organization of the Pods project
Subspec
group anymore and the products of the Pods all areAdded the documentation_url
DSL attribute to the specifications.
Fabio Pelosin
#1273
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
Added support for Xcode 5.
The generated Pods Xcode project is now compatible with arm64
projects and
is updated to use Xcode 5’s default settings removing all warnings.
NOTE to users migrating projects from Xcode 4, or are still using Xcode 4:
ONLY_ACTIVE_ARCH
build setting toYES
in the Debug
configuration. You will have to set the same on yourARCHS
value set, otherwise the buildxcodebuild
ONLY_ACTIVE_ARCH=NO
.Speed up project generation in pod install
and pod update
.
The pre and post install hooks that have been deprecated now include the name
and version of the spec that’s using them.
Only create a single resource bundle for all targets. Prior to this change a
resource bundle included into multiple targets within the project would create
duplicately named targets in the Pods Xcode project, causing duplicately named
Schemes to be created on each invocation of pod install
. All targets that
reference a given resource bundle now have dependencies on a single common
target.
Solved outstanding issues with CocoaPods resource bundles and Archive builds:
--copy-links
to the rsync invocation to ensure theTARGET_BUILD_DIR
which points to the AppBUILT_PRODUCTS_DIR
instead ensures that the path is correct for allEnsure resource bundles are copied to installation location on install actions
Chris Gummer
#1364
Various bugfixes in Xcodeproj, refer to its CHANGELOG
for details.
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
• cocoapods-downloader
pod init
command which generates a Podfile according to the~/.cocoapods/templates
folder. Two templates are supported:
Podfile.default
template for regular targets.Podfile.test
template for test targets.xcodeproj 'MyApp', 'App Store' => :release, 'Debug' => :debug, 'Release' => :release
libPods.a
static library is not stripped for all configurations, as explained in #1217.pod spec cat
.TARGET_BUILD_DIR
environment variable for installing resource bundles..xccurrentversion
file.Published by segiddins almost 10 years ago
USE_HEADERMAP
from the user’s project.pod lib create
command.pod push
failing when the podspec is unchanged. It will now[No change] ExamplePod (0.1.0)
and continue to push other podspecs ifPublished by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
• cocoapods-downloader
Added prepare_command
attribute to Specification DSL. The prepare command
will replace the pre_install
hook. The post_install
hook has also been
deprecated.
#1247
The reason we provided Ruby hooks at first, was because we wanted to offer
the option to make any required configuration possible. By now, however, we
have a pretty good idea of the use-cases and are therefore locking down the
freedom that was once available. In turn, we’re adding attributes that can
replace the most common use-cases. (See the enhancements directly following
this entry for more info).
The second reason we need to lock this down is because this is the last
remaining obstacle to fully serialize specifications, which we need in order
to move to a ‘spec push’ web-service in the future.
Added resource_bundles
attribute to the Specification DSL.
#743
#1186
Added vendored_frameworks
attribute to the Specification DSL.
#809
#1075
Added vendored_libraries
attribute to the Specification DSL.
#809
#1075
Restructured .cocoapods
folder to contain repos in a subdirectory.
Ian Ynda-Hummel
#1150
Improved pod spec create
template.
#1223
Added copy&paste-friendly dependency to pod search
.
#1073
Improved performance of the installation of Pods with git
sources which specify a tag.
#1077
Core Data xcdatamodeld
files are now properly referenced from the Pods
project.
#1155
Removed punctuation check from the specification validations.
#1242
Deprecated the documentation
attribute of the Specification DSL.
Core#20
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
• cocoapods-downloader
Added prepare_command
attribute to Specification DSL. The prepare command
will replace the pre_install
hook. The post_install
hook has also been
deprecated.
#1247
The reason we provided Ruby hooks at first, was because we wanted to offer
the option to make any required configuration possible. By now, however, we
have a pretty good idea of the use-cases and are therefore locking down the
freedom that was once available. In turn, we’re adding attributes that can
replace the most common use-cases. (See the enhancements directly following
this entry for more info).
The second reason we need to lock this down is because this is the last
remaining obstacle to fully serialize specifications, which we need in order
to move to a ‘spec push’ web-service in the future.
Added resource_bundles
attribute to the Specification DSL.
#743
#1186
Added vendored_frameworks
attribute to the Specification DSL.
#809
#1075
Added vendored_libraries
attribute to the Specification DSL.
#809
#1075
Restructured .cocoapods
folder to contain repos in a subdirectory.
Ian Ynda-Hummel
#1150
Improved pod spec create
template.
#1223
Added copy&paste-friendly dependency to pod search
.
#1073
Improved performance of the installation of Pods with git
sources which specify a tag.
#1077
Core Data xcdatamodeld
files are now properly referenced from the Pods
project.
#1155
Removed punctuation check from the specification validations.
#1242
Deprecated the documentation
attribute of the Specification DSL.
Core#20
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
[*]
syntax are now properlyxcconfig
attribute of a podspec
are nowPublished by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
CocoaPods
• cocoapods-core
• Xcodeproj
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• Xcodeproj
Published by segiddins almost 10 years ago
CocoaPods
• cocoapods-core
• cocoapods-downloader
• Xcodeproj
• CLAide
Introduces an experimental sandbox feature.
#939
Let’s face it, even though we have a great community that spends an amazing
amount of time on curating the specifications, the internet can be a hostile
place and the community is growing too large to take a naive approach any
longer.
As such, we have started leveraging OS X’s sandbox facilities to disallow
unsanctioned operations. This is still very experimental and therefore has to
be used explicitely, for now, but that does not mean we don’t want you to
start using it and report issues.
To use the sandbox, simply use the sandbox-pod
command instead. E.g.:
$ sandbox-pod install
In case of issues, be sure to check /var/log/system.log
for ‘deny’ messages.
For instance, here’s an example where the sandbox denies read access to /
:
May 16 00:23:35 Khaos kernel[0]: Sandbox: ruby(98430) deny file-read-data /
NOTE: The above example is actually one that we know of. We’re not sure
yet which process causes this, but there shouldn’t be a need for any process
to read data from the root path anyways.
NOTE 2: At the moment the sandbox is not compatible with the :path
option
when referencing Pods that are not stored within the directory of the Podfile.
The naked pod
command now defaults to pod install
.
#958
CocoaPods will look for the Podfile in the ancestors paths if one is
not available in the working directory.
#940
Documentation generation has been removed from CocoaPods as it graduated
to CocoaDocs. This decision was taken because CocoaDocs is a much better
solution which doesn't clutter Xcode's docsets while still allowing
access to the docsets with Xcode and with Dash. Removing this feature
keeps the installer leaner and easier to develop and paves the way for the
upcoming sandbox. Private pods can use pre install hook to generate the
documentation. If there will be enough demand this feature might be
reintegrated as plugin (see
#1037).
Improved performance of the copy resources script and thus build time of
the integrated targets. Contribution by @onato
#1050.
The changelog for the current version is printed after CocoaPods is
installed/updated.
#853.
Published by segiddins almost 10 years ago
Published by segiddins almost 10 years ago
Published by segiddins almost 10 years ago
COCOAPODS=1
macro in the Pod and the Clientprivate_header_files
attribute of the Specificationpod podfile-info
command. Shows list of used Pods and their info--all
- with dependencies. --md
- in Markdown.pod help
command. You can still use the old formatCocoaPods.podfile
. Moreover, theCocoaPods.podfile.yaml
.:local
flag in Podfile has been renamed to :path
and the old syntax