-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cocoapod integration #1148
Comments
That would be great, but I'd rather have a name like |
and published https://cocoapods.org/pods/nlohmann_json It's easy to add additional authors, for now I just put you. I didn't put your email. If you want me to update the list in anyway let me know. It's also very easy to do so yourself in the podspec file. The programming language of the podspec is ruby. |
Thanks for taking care of this! Is PR #1150 needed after all if the library is already published? |
your welcome. Theoretically PR is not needed. But it's good to keep all integration files in the main repo. |
I'd rather have the file in a repo controlled by the package maintainer (which I do not want to be). I cannot provide support for tools I do not use. |
I understand no worries. It will probably be good to add to your readme something like If you are using cocoapods, you can use the unofficial pod by adding |
Alright. Do you have a repository where you keep the pod? Then I can link it if someone has issues. Furthermore, I would need such an issue tracker to notify you about new releases. |
Happy Canada day. I'll set something up next week. In the mean time I will enjoy long weekend :) |
I would also need a small running example (something demonstrating how to compile a small program using the library) for the pod. |
Ok I added a sample project too. I have set it up on my bitbucket, as nlohmann_json-cocoapod. People can submit issues there in the issue tracker |
Thanks a lot! |
Is this ok? If I do it can I push to this repo? I want to be able to more easily use this library on ios. Perhaps under the pod
njson
.The text was updated successfully, but these errors were encountered: