<br><br><div class="gmail_quote">On Mon, Oct 19, 2009 at 10:11 AM, Ben Browitt <span dir="ltr"><<a href="mailto:ben.browitt@gmail.com">ben.browitt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="gmail_quote"><br><div>I've removed the umbrella folder and repeated all the steps. The jsonrpc plugin is running now so I don't know<br>
what happened before. If it'll crash again I'll use the toolbar and report my findings as you explained above.<br><br></div></div></div></blockquote><div><br>I'm glad to hear it went away. As you say though - if it does happen again, the findings would be very interesting.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br>Another option when developing plugins is to do a "make run" from the plugin directory. As long as you've declared the dependencies in the Makefile (and are using our standard <a href="http://include.mk" target="_blank">include.mk</a>), then you should find that it will auto-wire the dependencies automatically, and prevent you needing to do symlinks.<br>
</div></div></blockquote></div><div><br>Very useful, thanks.<br></div></div></div></blockquote><div><br>No worries. I might try to find a way to make this explicit in the documentation too, since it (hopefully) makes the turnaround time on the development process shorter.<br>
<br>By the way, if you're able to share, I'd be very interested to hear at some point what your plugin is going to do.<br></div></div>