Problem linking .0 file to nullclient
florin.diaconeasa at gmail.com
Wed Jul 30 15:56:48 EDT 2008
Thank you very much for the help.
Indeed your answer solved my problem.
Thank you again,
On Wed, Jul 30, 2008 at 8:21 PM, Sadrul Habib Chowdhury <imadil at gmail.com>wrote:
> * Florin Diaconeasa had this to say on [30 Jul 2008, 00:57:30 +0300]:
> > Hi!
> > I'm currently trying to extend the nullclient that comes with the sources
> > pidgin(in libpurple).
> > I have created a directory inside the example directory, which is called
> > Managers. Inside this directory i have 2 files:
> > Test.h
> > Test.c
> > written in C ofcourse.
> > Here i have 2 functions testOne() and testTwo()
> > The problem that i'm facing right now is that i can't seem to be able to
> > link the Test.o file to the compilation of nullclient
> > I've modified the LINK var(in the Makefile.in) so to contain
> > Managers/Test.o, but it doesn't do the trick, as i get undefined
> > to testOne() and testTwo()
> You should not manually modify Makefile.in files in pidgin, rather you
> need to change Makefile.am files appropriately.
> I am really bad at this kind of stuff, but a quick test seems to work
> with the following patch:
> --- libpurple/example/Makefile.am
> +++ libpurple/example/Makefile.am
> @@ -1,6 +1,6 @@ noinst_PROGRAMS = nullclient
> noinst_PROGRAMS = nullclient
> -nullclient_SOURCES = defines.h nullclient.c
> +nullclient_SOURCES = defines.h nullclient.c managers/test.h
> nullclient_DEPENDENCIES =
> nullclient_LDFLAGS = -export-dynamic
> nullclient_LDADD = \
> @@ -20,6 +20,7 @@ AM_CPPFLAGS = \
> -I$(top_builddir)/libpurple \
> -I$(top_srcdir)/libpurple \
> -I$(top_srcdir) \
> + -I$(top_srcdir)/libpurple/example/managers/ \
> $(DEBUG_CFLAGS) \
> $(GLIB_CFLAGS) \
> $(DBUS_CFLAGS) \
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel