<br><br><div class="gmail_quote">On Wed, Mar 10, 2010 at 7:52 PM, Lex Trotman <span dir="ltr"><<a href="mailto:elextr@gmail.com">elextr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div><div></div><div class="h5">On 11 March 2010 11:40, Chuck Tilbury <span dir="ltr"><<a href="mailto:chucktilbury@gmail.com" target="_blank">chucktilbury@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">
<br><br><div class="gmail_quote">On Wed, Mar 10, 2010 at 6:16 PM, Lex Trotman <span dir="ltr"><<a href="mailto:elextr@gmail.com" target="_blank">elextr@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">
<snip><div><br><br><div class="gmail_quote"><div>Aha,<br><br>I assume this means that you have more than one Geany at different prefixes? <br><br>There is a problem with plugins in that situation, the autoconf/make builder gets the wrong prefix and so makes the plugins with the wrong version. <br>
But since you made the demoplugin separately it works ok. <br><br>This bug has been raised to the autoconf maintainer but I've not seen it fixed. AFAIK the WAF builder works ok so you might want to use that.<br><br>
Cheers<br><font color="#888888">
Lex<br></font></div></div><br>PS ignore my comment about .lo and .la files, I wasn't paying attention, they are of course libtool files. But they "shouldn't" be needed to run just to link.<br>
</div></blockquote></div><br><div>So I will clean out the previous install and reinstall. That should fix the issue, correct?</div><div><br></div><div>The only files that I know of are in these areas:</div><div>/usr/bin/geany</div>
<div>/usr/lib/geany/</div><div>/usr/lib/geany-plugins/</div><div>/home/me/.config/geany/</div><div><br></div><div>Is there anything else?</div><div><br></div><font color="#888888"><div>-=c=-</div></font></blockquote></div>
</div><div>
<br>You could try make uninstall :-)<br><br>Well a nice clean install allways helps :-), but it HAS to be the same version as you are building the plugin for since the autotools is hard coded to use the standard Geany prefix for plugins.<br>
<br>As I said above I am told by "Prolific Plugin Programmers" that the waf version will handle plugins properly to any prefix, but I havn't used it yet.<br><br>Cheers<br><font color="#888888">Lex<br></font><br>
PS please reply to the list, not to me, so other people can see and interrupt any time either of us is talking garbage :-) ((sorry, I thought I was.))<br>
</div></div><br></blockquote><div> </div><div>My problem was that I first installed the Ubuntu package from the package repository. It worked fine, but there was the build confusion. I removed the package and then did a "make uninstall" to get it right. I built it from the source available in the web page and the demo plugin now loads and seems fine.</div>
<div><br></div><div>I had another problem with building the add-ons, though. After taking care of the dependencies given by ./configure, I tried to get and build the geany-plugins-0.18 files and many of the plugins refused to build because of inaccessible header files. I created a directory of /usr/include/geany and copied the files from .../geany_svn/src/*.h there, but there are still others that appear to be missing and that I don't have installed anywhere. The plugins that failed are:</div>
<div><div>#<span class="Apple-tab-span" style="white-space:pre"> </span>addons \</div><div>#<span class="Apple-tab-span" style="white-space:pre"> </span>geanydoc \</div><div>#<span class="Apple-tab-span" style="white-space:pre"> </span>geanylipsum \</div>
<div>#<span class="Apple-tab-span" style="white-space:pre"> </span>geanylua \</div><div>The others seem OK. Sorry, I don't have time to give more information. :( I gotta think that this is probably a issue that has already been looked at.</div>
<div><br></div><div>It looks like I have enough to get started on a macro recorder. Am I correct in thinking that the demo plugin has the correct message loop that I want to tap into?</div><div><br></div><div>Thanks,</div>
<div>-=chuck=-</div><div><br></div><div><br></div></div></div><br>