lib/cocoapods/installer/user_project_integrator.rb
def warn_about_empty_podfile
        if podfile.target_definitions.values.all?{ |td| td.empty? }
          UI.warn "[!] The Podfile does not contain any dependency."
        end
      end
# Warns the user if the podfile is empty.
#
# @note   The workspace is created in any case and all the user projects
#         are added to it, however the projects are not integrated as
#         there is no way to discern between target definitions which are
#         empty and target definitions which just serve the purpose to
#         wrap other ones. This is not an issue because empty target
#         definitions generate empty libraries.
#
# @return [void]
#
Warns the user if the podfile is empty.
Warns the user if the podfile is empty .
def warn_about_empty_podfile
        if podfile.target_definitions.values.all?{ |td| td.empty? }
          UI.warn "[!] The Podfile does not contain any dependency."
        end
      end
def warn_about_empty_podfile if podfile . target_definitions . values . all? { | td | td . empty? } UI . warn "[!] The Podfile does not contain any dependency." end end
Warns the user if the podfile is empty.
Warns the user if the podfile is empty .
None
void
note
The workspace is created in any case and all the user projects are added to it, however the projects are not integrated as there is no way to discern between target definitions which are empty and target definitions which just serve the purpose to wrap other ones. This is not an issue because empty target definitions generate empty libraries.
The workspace is created in any case and all the user projects are added to it however the projects are not integrated as there is no way to discern between target definitions which are empty and target definitions which just serve the purpose to wrap other ones . This is not an issue because empty target definitions generate empty libraries .