Hi, guys,

I'm new to do-plugins development, and I encountered some problems at
the beginning :(, here's the detail:
I followed the instructions here:
http://do.davebsd.com/wiki/index.php?title=Getting_started_with_writing_plugins
. and my system is ubuntu 9.04 i386

1. I checked out the code using
$ bzr branch lp:do-plugins
this command told me I should login with launchpad id, anyhow it
checkout a bunch of code(Branched 611 revision
(s)).

2. I installed monodevelop using
$ sudo apt-get install monodevelop

3. I opened the solution DoPlugins.mds, and it loads well.

but the problems comes next:
a. every project misses lots of references (Do.Platform, Do.Universe,
System.Core) while some references can be found( System.Web, System,
Mono.Posix).. so I cannot build the project using the monodevelop

b. since this can not work, I turned to terminal, after typing ./
autogen.sh, I got a long output with errors:

I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command
line.
Running aclocal -I . -I m4/shamrock  ...
Running automake --gnu  ...
Running autoconf ...
Running intltoolize --force --copy --automake ...
Running ./configure ...
configure: WARNING: unrecognized options: --enable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking whether NLS is requested... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... none
checking for intltool >= 0.35.0... 0.40.6 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.10.0
checking for XML::Parser... ok
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for pkg-config... /usr/bin/pkg-config
checking for mautil... /usr/bin/mautil
checking for a BSD-compatible install... /usr/bin/install -c
checking for mono... /usr/bin/mono
checking for gmcs... /usr/bin/gmcs
checking pkg-config is at least version 0.9.0... yes
checking for BANSHEE_INDEXER... no
checking for EVOLUTION_SHARP... yes
checking for FLICKRNET... yes
checking for GDATA_SHARP_CALENDAR... no
checking for GDATA_SHARP_CONTACTS... no
checking for GDATA_SHARP_DOCUMENTS... no
checking for GDATA_SHARP_YOUTUBE... no
checking for GCONF_SHARP_20... yes
checking for GLADE_SHARP_20... yes
checking for GLIB_SHARP_20... yes
checking for GNOME_DESKTOP_SHARP_20... yes
checking for GNOME_KEYRING_SHARP... yes
checking for GNOME_SHARP_20... yes
checking for GNOME_VFS_SHARP_20... yes
checking for GTK_SHARP_20... yes
checking for MONO_ADDINS... yes
checking for MONO_ADDINS_GUI... yes
checking for MONO_ADDINS_SETUP... yes
checking for NDESK_DBUS_10... yes
checking for NDESK_DBUS_GLIB_10... yes
checking for NOTIFY_SHARP... yes
checking for WNCK_SHARP_10... yes
checking for DO_PLATFORM... yes
checking for DO_PLATFORM_LINUX... yes
checking for DO_UNIVERSE... yes
checking for DO_INTERFACE_WINK... configure: error: Package
requirements (do.interface.wink >= 0.8) were not met:

No package 'do.interface.wink' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables
DO_INTERFACE_WINK_CFLAGS
and DO_INTERFACE_WINK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.






so... how to install the missing package "do.interface.wink" ?

c. even if the project built well, I still don't know how to start
writing a new plugin ( seems like I need to add a new project to the
solution, but what type of project? what's the structure of project?
how to make sure the plugin can be recognised by the Do after
building? what's the API for Do system?....) I hope anyone can give me
some detailed instructions, a "hello world" will be great!

Thanks in advance!






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"GNOME Do" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/gnome-do?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to