Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
C
cocoapods
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
gengmeiios
cocoapods
Commits
ff3a38be
Commit
ff3a38be
authored
Jan 28, 2016
by
Marius Rackwitz
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[Doc] Scoping is not limited to frameworks
parent
b00eac3c
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
pod_target.rb
lib/cocoapods/target/pod_target.rb
+5
-5
No files found.
lib/cocoapods/target/pod_target.rb
View file @
ff3a38be
...
...
@@ -19,11 +19,11 @@ module Pod
# @return [Bool] whether the target needs to be scoped by target definition,
# because the spec is used with different subspec sets across them.
#
# @note
For frameworks the target products of {PodTarget}s are named
#
after their specs. The namespacing cannot directly happen in
#
the product name itself, because this must be equal to the modul
e
#
name and this will be used in source code, which should stay
#
agnostic over the
dependency manager.
# @note
The target products of {PodTarget}s are named after their specs.
#
The namespacing cannot directly happen in the product name itself,
#
because this must be equal to the module name and this will b
e
#
used in source code, which should stay agnostic over the
# dependency manager.
# We need namespacing because multiple targets can exist for the
# same podspec and their products should not collide. This
# duplication is needed when multiple user targets have the same
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment