cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Developing Cordova plug-ins
Date Wed, 03 Jul 2013 03:10:47 GMT
For CordovaLib, I think what you'd need to do is:

cd platforms/ios
rm -r CordovaLib
../path/to/cordova-ios/bin/update_cordova_subproject MyProject.xcodeproj

For plugins, I think removing & re-adding is what we've got, but are open
for suggestions for making it better.


On Tue, Jul 2, 2013 at 8:48 PM, Don Coleman <don.coleman@gmail.com> wrote:

> I develop plugins in a sample project, then copy the files into the plugman
> directory structure.
>
> If multiple projects use the plugin, I usually uninstall and re-install the
> plugin after making updates
>   $ cordova plugin remove plugin_name
>   $ cordova plugin add /path/to/plugin
>
> For cordovalib, removing and adding the platform works to upgrade but is a
> pain if you have local modifications
>  $ cordova platform remove ios
>  $ cordova platform add ios
>
>
>
>
> On Tue, Jul 2, 2013 at 7:50 PM, Tyler Wilson <twilson@pulse-robotics.com
> >wrote:
>
> > Good day,
> >
> > So based on earlier emails and more research, I am going to update my
> > project to the more 'modern' cordova-cli way, following the instructions
> > here: https://github.com/apache/cordova-cli
> >
> > Two questions:
> >
> > 1. I am developing a plug-in (Bluetooth Smart) at the same time. I think
> > it is clear how I can create a local plugman-compatible layout for the
> > import. But since I will be importing the plugin into multiple projects,
> > how can I organize it so that the plugin is linked to the original
> > location? Or at least do a kind of 'plugin update' procedure on the
> > projects?
> >
> > 2. Similar question for the CordovaLib. In the 2.x versions I would
> always
> > do a ./create --shared so that I could update the cordova git clone and
> my
> > projects would automatically be up-to-date. Is this possible with the
> > cordova-cli system?
> >
> > Thank you,
> > Tyler
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message