Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 39329 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Tried out your 'sharpie' command line tool and am interested in using it to pull in and expose a CocoaPod based iOS library.
I have a custom pod that is currently deployed via a private cocoapods specs repo. Can you please enhance the 'sharpie' command line tool to allow me to point to my specs repo rather than use the normal master specs repo?
Good idea. I will implement this when time permits.
+1 this would be very handy
I'm not exactly sure what this would look like from an Objective Sharpie perspective.
I may not be fully understanding how the "pod" tool works, but I do not see any way to explicitly specify a different repo.
Objective Sharpie invokes the following Cocoapods commands under the hood:
I do not see any options to those commands for specifying a repo. It's my understanding that if you use the `pod repo` command to manage repos as usual, list and install should implicitly handle the non-master repo?
"pod install" requires a podfile
* use the source directive.
* specify per pod the folder or git repo directly using the :git or :path options
Both options will prompt you for credentials when required.
Ah, okay, so the repo is specified via the Podfile, which sharpie generates.
Does this mean that the `pod list/search` tools searches the repos implicitly?
I could probably generate the source into the Podfile that way.
yes. this is how I bypassed the initial step.
* ran 'sharpie pod init XYZ' for a public pod
* fix the Podfile by adding 'source' and changed the reference to our spec
you probably will also have to include the public source as well so it kind find referenced public pods.
Next problem I'm running into is that sharpie pod bind does not like the Amazon AWS pods (https://github.com/aws/aws-sdk-ios). And will fail due to missing header files (which are there).