Changes between Version 2 and Version 3 of CHowTo/DebugAPIHowTo

Timestamp:

Sep 14, 2007, 2:36:21 AM (16 years ago)

Author:

John Bailey

Comment:

s/-/_/ for consistency with what was added for the 2.2.0 release

CHowTo/DebugAPIHowTo

@@ -22 +22 @@
 This plugin will eventually be included as an example plugin in the libpurple source, but it is not part of Pidgin 2.0.2, which the rest of the How-To documents assume you are using.  We are going to continue this assumption here.  In fact, we're going to continue all the assumptions set forth in the [wiki:CHowTo/BasicPluginHowto Basic C Plugin How-To]
 
-Go back to `~/development/pidgin-2.0.2/libpurple/plugins` and fire up your favorite editor on a new file called `debug-example.c`.  The contents of the file will be this:
+Go back to `~/development/pidgin-2.0.2/libpurple/plugins` and fire up your favorite editor on a new file called `debug_example.c`.  The contents of the file will be this:
  {{{
 #!c
@@ -127 +127 @@
 
 == Compiling, Installing, and Testing the Plugin ==
-As before, run `make debug-example.so` (`make -f Makefile.mingw debug-example.dll` for you Windows types) to build the plugin.  Copy the resulting `debug-example.so` to `~/.purple/plugins`, or copy the resulting `debug-example.dll` to `%APPDATA%\.purple\plugins`.
+As before, run `make debug_example.so` (`make -f Makefile.mingw debug_example.dll` for you Windows types) to build the plugin.  Copy the resulting `debug_example.so` to `~/.purple/plugins`, or copy the resulting `debug_example.dll` to `%APPDATA%\.purple\plugins`.
 
 Since we're continuing our assumptions, we're going to still assume that you're using Pidgin.  Open the Debug Window (located on the Help menu).  Resize it so it's rather large so we can easily see all the messages.  Now open the Plugins dialog.  In the Debug Window you'll see a ''lot'' of information about plugins scroll by as libpurple reprobes all the plugins available to it.  Now find the "Debug API Example" entry in the dialog.  Check the box and watch what appears in the Debug Window.  You may need to scroll back just a bit to see the six messages that print.  You should see something like this: