Git Product home page Git Product logo

cocoapods-generate's Introduction

cocoapods-generate

A CocoaPods plugin that allows you to easily generate a workspace from a podspec.

Whether you want to completely remove all Xcode projects from your library's repository or you want to be able to focus on a small piece of a monorepo, a single pod gen command will build up a workspace suitable for writing, running, testing, and debugging in Xcode.

When you're done working, you don't have to do anything -- and that means no merge conflicts, no managing Xcode projects, and no tearing down a sample app setup. pod gen manages all that for you.

Installation

Add this line to your application's Gemfile:

gem 'cocoapods-generate'

And then execute:

$ bundle

Or install it yourself as:

$ gem install cocoapods-generate

CLI

The main point of interaction with the plugin is via the pod gen command. It takes in a list of podspecs (or directories) as arguments, as well as many options that modify how gen will create your workspace.

Usage:

    $ pod gen [PODSPEC|DIR ...]

      Generates Xcode workspaces from a podspec.

      pod gen allows you to keep your Podfile and podspecs as the single source of
      truth for pods under development. By generating throw-away workspaces capable of
      building, running, and testing a pod, you can focus on library development
      without worrying about other code or managing an Xcode project.

      pod gen works particularly well for monorepo projects, since it is capable of
      using your existing settings when generating the workspace, making each gen'ed
      project truly a small slice of the larger application.

Options:

    --allow-root                           Allows CocoaPods to run as root
    --silent                               Show nothing
    --verbose                              Show more debugging information
    --no-ansi                              Show output without ANSI codes
    --help                                 Show help banner of specified command
    --podfile-path=PATH                    Path to podfile to use
    --use-podfile                          Whether restrictions should be copied from
                                           the podfile
    --use-podfile-plugins                  Whether plugins should be copied from the
                                           podfile
    --use-lockfile                         Whether the lockfile should be used to
                                           discover transitive dependencies
    --use-lockfile-versions                Whether versions from the lockfile should
                                           be used
    --use-libraries                        Whether to use libraries instead of
                                           frameworks
    --generate-multiple-pod-projects       Whether to generate multiple Xcode projects
    --incremental-installation             Whether to use incremental installation
    --gen-directory=PATH                   Path to generate workspaces in
    --auto-open                            Whether to automatically open the generated
                                           workspaces
    --clean                                Whether to clean the generated directories
                                           before generating
    --app-host-source-dir=DIR              A directory containing sources to use for
                                           the app host
    --sources=SOURCE1,SOURCE2              The sources from which to pull dependent
                                           pods (defaults to all repos in the podfile
                                           if using the podfile, else all available
                                           repos). Can be a repo name or URL. Multiple
                                           sources must be comma-delimited.
    --local-sources=SOURCE1,SOURCE2        Paths from which to find local podspecs for
                                           transitive dependencies. Multiple
                                           local-sources must be comma-delimited.
    --platforms=ios,macos                  Limit to specific platforms. Default is all
                                           platforms supported by the podspec.
                                           Multiple platforms must be comma-delimited.
    --repo-update                          Force running `pod repo update` before
                                           install
    --use-default-plugins                  Whether installation should activate
                                           default plugins
    --deterministic-uuids                  Whether installation should use
                                           deterministic UUIDs for pods projects
    --disable-input-output-paths           Whether to disable the input & output paths
                                           of the CocoaPods script phases (Copy
                                           Frameworks & Copy Resources)
    --share-schemes-for-development-pods   Whether installation should share schemes
                                           for development pods
    --warn-for-multiple-pod-sources        Whether installation should warn when a pod
                                           is found in multiple sources
    --use-modular-headers                  Whether the target should be generated as a
                                           clang module, treating dependencies as
                                           modules, as if `use_modular_headers!` were
                                           specified. Will error if both this option
                                           and a podfile are specified
    --single-workspace                     Whether to produce a single workspace for
                                           all podspecs specified.
    --xcode-version=xcode_version          The Xcode version to use for producing the
                                           consumer sample project

.gen_config.yml

All of the command line options above can also be specified in a .gen_config.yml file.

For example, the equivalent of running pod gen --no-deterministic-uuids --sources=a,b --gen-directory=/tmp/gen --use-libraries would be

deterministic_uuids: false
sources:
- a
- b
gen_directory: /tmp/gen
use_libraries: true

Development

After checking out the repo, run bin/setup to install dependencies. Then, run bin/rake spec to run the tests.

You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install.

To release a new version, update the version number in VERSION, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/square/cocoapods-generate. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

Code of Conduct

Everyone interacting in the cocoapods-generate project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

cocoapods-generate's People

Contributors

amorde avatar congt avatar dependabot-preview[bot] avatar dependabot[bot] avatar dnkoutso avatar dostrander avatar jszumski avatar justinseanmartin avatar kwigginton avatar paulb777 avatar samedson avatar segiddins avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cocoapods-generate's Issues

Install cocoapods-generate do not add gen command to pod.

Cocoapods 1.7.5

  1. gem install cocoapods-generate

Successfully installed cocoapods-generate-1.6.0
Parsing documentation for cocoapods-generate-1.6.0
Done installing documentation for cocoapods-generate after 0 seconds
1 gem installed

  1. pod gen

[!] Unknown command: gen
Did you mean: env?

  1. gem list

*** LOCAL GEMS ***

bigdecimal (default: 1.4.1)
bundler (default: 1.17.3)
cmath (default: 1.0.0)
cocoapods-disable-podfile-validations (0.1.1)
cocoapods-generate (1.6.0)
cocoapods-plugins (1.0.0)
csv (default: 3.0.9)
...

Generated project behaves differently from embedding the Pod in an App.

As mentioned in CocoaPods/CocoaPods#9686 I'm seeing different behaviour from embedding a pod into my app and using the sample project generated by pod gen.

  • running xcodebuild on the generated project builds for maccatalyst instead of ios
  • Swift-Version specification for included pods does not seem to be passed along correctly.

To reproduce, clone https://github.com/gereons/CocoapodsGenTest and run the included gen-build.sh script.

This will produce an error

Compiling UIViewController+UIEmptyState.swift
/.../TestLib/gen/TestLib/UIEmptyState/src/UIEmptyState/UIViewController+UIEmptyState.swift:228:18: 'bringSubviewToFront' has been renamed to 'bringSubview(toFront:)'

        view.bringSubviewToFront(newView)
             ^~~~~~~~~~~~~~~~~~~

while the same call in TestLib/Classes/ReplaceMe.swift compiles without problems.

This build finishes with the output

The following build commands failed:
CompileSwift normal x86_64 /.../TestLib/gen/TestLib/UIEmptyState/src/UIEmptyState/UIViewController+UIEmptyState.swift
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
Ld /Users/gereon/Library/Developer/Xcode/DerivedData/TestLib-abhbyfdhfvwgoxeuoxkqludfutcv/Build/Products/Debug-maccatalyst/TestLib/TestLib.framework/Versions/A/TestLib normal x86_64

(emphasis mine)

Including this test pod into an app shows none of these errors.

v2.0.0 adds CWD as an absolute path which can conflict with local sources

In 1.6.0, the cwd wasn't added to the list of local sources (AFAICT), but in v2.0.0, the cwd is added as an absolute path, so if you specify local sources, they can be at odds with each other.

In v2.0.0, I cannot generate my project and the following error is printed:

Generating GoogleDataTransportCCTSupport in `gen/GoogleDataTransportCCTSupport`
[!] There are multiple dependencies with different sources for `GoogleDataTransportCCTSupport` in `CocoaPods.podfile.yaml`:

- GoogleDataTransportCCTSupport/Tests-Integration (from `../../GoogleDataTransportCCTSupport.podspec`)
- GoogleDataTransportCCTSupport/Tests-Monkey (from `../../GoogleDataTransportCCTSupport.podspec`)
- GoogleDataTransportCCTSupport/Tests-Unit (from `../../GoogleDataTransportCCTSupport.podspec`)
- GoogleDataTransportCCTSupport/TestApp (from `../../GoogleDataTransportCCTSupport.podspec`)
- GoogleDataTransportCCTSupport (from `../../GoogleDataTransportCCTSupport.podspec`)
- GoogleDataTransportCCTSupport/TestApp (from `/Users/haneym/coding/firebase-ios-sdk/GoogleDataTransportCCTSupport.podspec`)

Steps to reproduce: (assuming cocoapods and cocoapods-generate is installed):

brew install protobuf nanopb-generator
easy_install --user protobuf
git clone [email protected]:firebase/firebase-ios-sdk.git
cd firebase-ios-sdk
GDT_DEV=1 pod gen GoogleDataTransportCCTSupport.podspec --auto-open --gen-directory=firebase-ios-sdk/gen --local-sources=firebase-ios-sdk --clean --verbose --platforms=ios,macos,tvos

--use-podfile: In podfile post_install set buildsetting, after gen workspace, buildsetting not working

My Pod requires special settings to compile and I set it in the Podfile::

post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES' config.build_settings['CLANG_WARN_DOCUMENTATION_COMMENTS'] = 'NO' end if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle" target.build_configurations.each do |config| config.build_settings['CODE_SIGN_IDENTITY[sdk=macosx*]'] = '-' end end end end

pod gen xx.podspec --gen-directory=xx --platforms=ios --use-podfile --clean --auto-open

However, the generated Xcode project use own defalult setting. In Podfile Set BUILD_LIBRARY_FOR_DISTRIBUTION & CLANG_WARN_DOCUMENTATION_COMMENTS &CODE_SIGN_IDENTITY[sdk=macosx*] not working:
image

image

can someone tell me how to solve this problem?

编码错误

在Jenkins 中使用 ruby脚本 执行 pod gen 命令(%x(pod gen ))
报错 ArgumentError - invalid byte sequence in US-ASCII
/Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/cdn_source.rb:287:in split' /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/cdn_source.rb:287:in block in ensure_versions_file_loaded'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/cdn_source.rb:286:in `each'

Any way to generate tests for development pods?

I'm working on a module that includes another local module as dependency (podspecs are in the same directory, I use pod gen --local_sources=. for generation).

I would like to have pod gen generate test targets not only for the main pod spec but for the another module as well, similar to effect that can be achieved via Podfile by something like:

pod 'CoconutLib', '~> 1.0', :testspecs => ['Tests']

Is there a way to accomplish this?

Support `:podspec` as alternative to `:path` option

Currently local a podspec can only be included using the --local-sources option which is a directory that may contain multiple podspec files for multiple pod dependencies. This option is used for local dependencies where the source is also local. However to include a library which itself does not have a podspec, a podspec can be created outside a spec repository and refrerenced in the podfile according to https://guides.cocoapods.org/syntax/podfile.html#pod.

If a podspec is available from another source outside of the library’s repository. Consider, for instance, a podspec available via HTTP:

pod 'JSONKit', :podspec => 'https://example.com/JSONKit.podspec'

The :podspec option can also be a local path, however currently pod gen has no option to specify the :podspec for a pod dependency.

Often it is not required to use the :podspec, because the :path option works for local podspecs as well. However, the installation process of :podspec and :path are different, which results in failures. For example the third party podspecs of react-native can not be included with the :path option.

Support generating an xcworkspace instead of separate xcodeprojs

If pod gen is given a list of podspecs, can an xcworkspace containing all the generated projects be generated? Perhaps an additional --gen-workspace argument can be added to implement this functionality. In this case, --auto-open would open the workspace, as opposed to opening all generated projects individually.

Question: Repo layout for monorepo

Hi,

Looking at using this plugin to support multiple modules developed in a single repo.

I got a basic setup working with a single module, when adding more modules, the root of the repo started to feel cluttered with the podspecfiles in the root of the repo.

Any guidance on a clean way of supporting podspec files as a single source of truth while keeping the root of the repo clean?

I tried out sub specs as an approach but didn't get any job with test specs being associated with a subspec.

If the answer is it's a necessary evil with Cocoapods, that totally fine.

Thanks for the awesome work!

New release is required to resolve incompatibility with current iOS toolchain

As of October 2020, the currently released cocoapods-generate gem is incompatible with the latest Cocoapods 1.10.0.
This has been raised and resolved in master branch as a separate issue (#68), but the lack of a release has become all the more pressing now, because Cocoapods 1.9.3 exhibits other incompatibilities with newest Xcode 12, which are resolved in Cocoapods 1.10.0.
Last release of cocoapods-generate was April 2020 - can we have some idea when a new release is likely/planned? Current workaround for working with latest Xcode is to build/install master gem.

pod gen not working with cocoapods 1.10.0

update cocoapods to the latest version ie 1.10.0
gem install cocoapods
gem install cocoapods-generate
pod gen will fail
[!] cocoapods-generate requires CocoaPods >= 1.5.0
cocoapods-generate version check logic is wrong
actual result 1.10.0 < 1.5.0
expected result 1.10.0 > 1.5.0

update: it seems like issue is fixed in master branch when this will be available as release

"Unknown command: `gen`" even if latest cocoapods-generate gem is installed.

I have the following list of cocoapods related gems installed:

cocoapods (1.11.2)
cocoapods-core (1.11.2)
cocoapods-deintegrate (1.0.5)
cocoapods-disable-podfile-validations (0.1.1)
cocoapods-downloader (1.5.1)
cocoapods-generate (2.2.2)
cocoapods-plugins (1.0.0)
cocoapods-search (1.0.1)
cocoapods-trunk (1.6.0)
cocoapods-try (1.2.0)

My ruby version - ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-darwin20]
As you can see in the above list cocoapods-generate (2.2.2) is installed. But, when I run pod gen I get


    WARNING: CocoaPods requires your terminal to be using UTF-8 encoding.
    Consider adding the following to ~/.profile:

    export LANG=en_US.UTF-8
    
[!] Unknown command: `gen`
Did you mean: env?

I couldn't understand how to apply the solution from Issue 95

Though I tried sudo 'xcode-select --switch /Applications/Xcode.app' as suggested in Issue 95 the issue still persist.

refer: Issue 95 and Issue 84

app_host_source_dir wrong path

podspec path : /Users/aaa/bbb/xxx/xxx.podspec
yml path : /Users/aaa/bbb/xxx/.gen_config.yml
xcodeproj path : /Users/aaa/bbb/xxx/gen/xxx/xxx.xcodeproj

after set app_host_source_dir: app in .gen_config.yml

and 'pod gen'

I got an error.

Build input file cannot be found: '/Users/aaa/bbb/app/main.m'

'/Users/aaa/bbb/xxx/app/main.m' expected

Is there a way to ignore existing Podfile?

I'm currently in progress of working on a module inside a big project. The module is kept in a subfolder of the root where the project Podfile is located. I'm not interested at the moment in integration with the project. However when I do pod gen in the subfolder, it detects the Podfile at the upper level and tries to interpret it, producing some warnings (irrelevant to the module I work on/potentially triggered due to loading Podfile multiple times) and actually misbehaving e.g. by outputting Open subfolder/gen/Module/Module.xcworkspace to work on Module (i.e. path is relative to Podfile not to the current directory).

The workaround for me is to rename Podfile to e.g. Podfile.ignored. But it would be great to have a way to ignore the Podfile by specifying e.g. --no-use-podfile or something like that. Probably I miss something (I'm not experienced with Ruby gems/command line option parsers).

`podspec_paths` config option cannot be set in `.gen_config.yml`

When parsing arguments from the command line, podspec_paths will be initialized to an empty array if no positional arguments were provided.

if option.name == :podspec_paths
argv.arguments!

This hash is then passed to merge_configuration, which will cause any existing array which was loaded from .gen_config.yml to be swallowed by the empty array during merge! here:

configuration = config_hashes.compact.each_with_object({}) { |e, h| h.merge!(e) }

I'll have a PR up soon but let me know if I missed something

`swift_version` in the Podspec isn't reflected in the generated Xcode project(s)

My Pod requires Swift 5 to compile and I set it in the Podspec:

  s.swift_version = '5.0'

However, the generated Xcode project still sets the version to 4.0:

smuthu in ~/Sandbox/ios-video-player on branch master >grep 'SWIFT_VERSION = 4.0' ./ -r --color=auto -n
...
.//GeneratedWorkspace/Workspace/Pods/Pods.xcodeproj/project.pbxproj:9874:				SWIFT_VERSION = 4.0;
.//GeneratedWorkspace/Workspace/Pods/Pods.xcodeproj/project.pbxproj:9916:				SWIFT_VERSION = 4.0;
...
.//GeneratedWorkspace/Workspace/Workspace.xcodeproj/project.pbxproj:287:				SWIFT_VERSION = 4.0;
.//GeneratedWorkspace/Workspace/Workspace.xcodeproj/project.pbxproj:374:				SWIFT_VERSION = 4.0;

I was able to run

find . -name '*.pbxproj' -print0 | xargs -0 sed -i "" "s/SWIFT_VERSION\ =\ 4.0/SWIFT_VERSION\ =\ 5.0/g"

and confirmed that my targets build correctly.

cocoapods-generate should respect the swift_version flag and reflect it in the generated Xcode projects.

ERROR: While executing gem ... (NoMethodError) undefined method `request' for nil:NilClass on every version after 1.4.1

When I run gem install cocoapods-generate, it installs version 1.4.1 instead of the most recent (right now is 2.2.2).

My stack is currently incompatible with this version of cocoapods-generate. I get this error which was fixed in later releases:

[!] cocoapods-generate requires CocoaPods >= 1.5.0

When I run gem install cocoapods-generate -v 2.2.2, or any version after 1.4.1, I get:

ERROR: While executing gem ... (NoMethodError)
undefined method `request' for nil:NilClass

My stack:

M1 chip (arm64)
ruby 3.0.2p107
cocoapods (1.10.1)

watchOS support for Pod gen

Hi! I'm trying to add unit tests for a watchOS host app. I'm not able to import a watchOS app's resource files using 'Pod gen', so I wonder if there is such a support that I'm not aware of.

cocoapods-generate won't include sources shared across test_specs

Using cocoapods version 1.6.0.rc.2 and cocoapods-generate, I have two test_specs like below:

  s.test_spec 'UnitTests' do |test_spec|
    test_spec.requires_app_host = false
    test_spec.source_files = 'MyThing/Tests/Common/**/*.{h,m}'
    test_spec.source_files = 'MyThing/Tests/Unit/**/*.{h,m}'
  end

  s.test_spec 'EndToEndUnitTest' do |test_spec|
    test_spec.requires_app_host = true
    test_spec.source_files = 'MyThing/Tests/Common/**/*.{h,m}'
    test_spec.source_files = 'MyThing/Tests/EndToEnd/**/*.{h,m}'
  end

both test_specs have the line
test_spec.source_files = 'MyThing/Tests/Common/**/*.{h,m}'

but cocoapods-generate can't figure out which target the common sources belong to, so they are omitted from the project.

There's no obvious way to solve this problem. Creating an additional test_spec for the purposes of being a dependency of the other two test_specs doesn't work because the dependency isn't being compiled. So if you have something like a category used only for testing, its methods are missing.

Support forcing directory structure as project structure

The generated workspace uses test_spec names as logical folders in Xcode. This makes it difficult to pull out the sources that are common across test targets.

I have this directory structure, and would like the workspace to have this structure, too:

Tests/
- Common/
- Integration/
- Unit/

and these test specs:

  • Unit
  • Integration

The generated workspace builds this structure:

Integration/
- Common/
- Integration/

Unit/
- Unit/

AFAICT, Common/ shows up in Integration because it's earlier in the alphabet. An additional flag, maybe --ignore-spec-names would be useful here.

Side note: I'm really loving cocoapods-generate, thanks for making the plugin!

To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries)

Hi,There is a question, if :modular_headers => true is used, does gen support it?

Here is an example Demo

We have this error here.

Podfile

source 'https://cdn.cocoapods.org/'
platform :ios, '9.0'

target 'Swift-OC' do

#Swift
    pod 'Alamofire'
    pod 'Moya'
    pod 'SnapKit'
    pod 'Kingfisher'
    pod 'HandyJSON'
    pod 'lottie-ios'
    pod 'Toast',:modular_headers => true
    
#OC
    pod 'MYLCommonUI', '~> 0.0.11',:modular_headers => true
    pod 'Masonry',:modular_headers => true
 
end

error

The Swift pod Swift-OC depends upon Toast, MYLCommonUI, and Masonry, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

thank

Getting Unknown command: `gen`

CocoaPods version : 1.10.0

steps to reproduce

  1. $ sudo gem install cocoa-pods-generate
Successfully installed cocoapods-generate-2.0.1
Parsing documentation for cocoapods-generate-2.0.1
Done installing documentation for cocoapods-generate after 0 seconds
1 gem installed
  1. $ pod gen
[!] Unknown command: `gen`
Did you mean: env?
  1. $ gem list
activesupport (5.2.4.4)
algoliasearch (1.27.5)
bigdecimal (1.2.8)
bundler (2.1.4)
CFPropertyList (2.2.8)
cocoapods-disable-podfile-validations (0.1.1)
cocoapods-generate (2.0.1)
concurrent-ruby (1.1.7)
did_you_mean (1.0.0)
fuzzy_match (2.0.4)
httpclient (2.8.3)
i18n (1.8.5)
io-console (0.4.5)
json (1.8.3.1)
libxml-ruby (2.9.0)
minitest (5.8.5)
nap (1.1.0)
net-telnet (0.1.1)
nokogiri (1.5.6)
power_assert (0.2.6)
psych (2.1.0.1)
rake (10.4.2)
rdoc (4.2.1)
sqlite3 (1.3.11)
test-unit (3.1.5)
thread_safe (0.3.6)
tzinfo (1.2.7)

pod gen doesn't respect --local_sources for test_specs

My podspec has these deps

  s.dependency 'FirebaseCoreDiagnosticsInterop', '~> 0.1'
  s.dependency 'GoogleDataTransportCCTSupport', '~> 0.1'
  s.dependency 'GoogleUtilities/Environment', '~> 6.0'
  s.dependency 'GoogleUtilities/Logger', '~> 6.0'

and this test spec

  s.test_spec 'unit' do |unit_tests|
    unit_tests.dependency 'FirebaseCore', '~> 6.0'
    unit_tests.requires_app_host = false
  end

but the local version of FirebaseCore isn't used--it's downloaded instead.

pod gen doesn't respect platform specific dependencies

Given a podspec supporting multiple platforms but also with a platform-specific depa like s.ios.dependency 'SomeiOSSpecificDep', pod gen won't generate a podfile that has that platform information in it. Running pod gen will produce an error similar to

Generating MyLib in `gen/`
[!] The platform of the target `App-macOS` (macOS 10.11) is not compatible with `SomeiOSSpecificDep (1.0)`, which does not support `osx`.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.