Make.mingw for nullclient?

Joanna Chopard (jchopard) jchopard at cisco.com
Mon Sep 3 11:18:27 EDT 2007


Hi everyone,

I've tried to create the Make.mingw for nullclient myself, but I'm
battling it!
I must be doing something stupid, as it's been a while since I've
written a makefile myself.

Basically, I think it has problem linking, even though I specify the
LIB_PATHS.  I've tried to include and give lib_paths to everything
possible!!!  And it's driving me mad.
I get undefined errors like the following:

========================================================================
========
gcc.exe -o nullclient.exe -I../../libpurple -I../../libpurple/win32
-I../.. -I..
/../../win32-dev/gtk_2_0/include
-I../../../win32-dev/gtk_2_0/include/glib-2.0 -
I../../../win32-dev/gtk_2_0/lib/glib-2.0/include -I/usr/include
-I../../pidgin/w
in32/IdleTracker -I../../pidgin -I../../pidgin/win32
-I../../../win32-dev/gtk_2_
0/include/gtk-2.0 -I../../../win32-dev/gtk_2_0/include/pango-1.0
-I../../../win3
2-dev/gtk_2_0/include/atk-1.0 -I../../../win32-dev/gtk_2_0/include/cairo
-I../..
/../win32-dev/gtk_2_0/lib/gtk-2.0/include
-I../../../win32-dev/gtkspell-2.0.6 -I
../../../win32-dev/aspell-dev-0-50-3-3/include
-L../../../win32-dev/gtk_2_0/lib
-L../../libpurple -L../../pidgin -L../../pidgin/win32/IdleTracker
-L../../../win
32-dev/aspell-dev-0-50-3-3/lib -L -L  -lintl -lglib-2.0 -lgthread-2.0
-lgobject-
2.0 -lgmodule-2.0 -lws2_32 -lpurple -lz -lidletrack -lgtk-win32-2.0
-latk-1.0 -l
pango-1.0 -lgdk-win32-2.0 -lgdk_pixbuf-2.0 -lgdi32 -lwinmm nullclient.o
nullclient.o:nullclient.c:(.text+0x3b): undefined reference to
`g_io_channel_uni
x_get_fd'
nullclient.o:nullclient.c:(.text+0x7c): undefined reference to
`g_malloc0'
nullclient.o:nullclient.c:(.text+0xa6): undefined reference to
`g_io_channel_uni
x_new'
nullclient.o:nullclient.c:(.text+0xd0): undefined reference to
`g_io_add_watch_f
ull'
nullclient.o:nullclient.c:(.text+0xdb): undefined reference to
`g_io_channel_unr
ef'
nullclient.o:nullclient.c:(.text+0x12d): undefined reference to
`purple_utf8_str
ftime'
nullclient.o:nullclient.c:(.text+0x13a): undefined reference to
`purple_conversa
tion_get_name'
nullclient.o:nullclient.c:(.text+0x17e): undefined reference to
`purple_conversa
tions_set_ui_ops'
nullclient.o:nullclient.c:(.text+0x19d): undefined reference to
`purple_connecti
on_get_account'
nullclient.o:nullclient.c:(.text+0x1f4): undefined reference to
`g_main_loop_new
'
nullclient.o:nullclient.c:(.text+0x206): undefined reference to
`purple_util_set
_user_dir'
nullclient.o:nullclient.c:(.text+0x212): undefined reference to
`purple_debug_se
t_enabled'
nullclient.o:nullclient.c:(.text+0x21e): undefined reference to
`purple_core_set
_ui_ops'
========================================================================
========

I've attached a copy of Makefile.mingw...
If you could take a quick look, I would really appreciate it!!!

Thanks,
Joanna 
  

-----Original Message-----
From: devel-bounces at pidgin.im [mailto:devel-bounces at pidgin.im] On Behalf
Of Joanna Chopard (jchopard)
Sent: Monday, September 03, 2007 2:09 PM
To: Etan Reisner
Cc: devel at pidgin.im
Subject: RE: Make.mingw for nullclient?

Thanks Etan, for the feedback. 

Does anyone have the Makefile.mingw for nullclient example that they'd
like to share?
I'd really appreciate it if someone could...

Thanks,
Joanna
 

-----Original Message-----
From: Etan Reisner [mailto:pidgin at unreliablesource.net]
Sent: Saturday, September 01, 2007 7:38 PM
To: Joanna Chopard (jchopard)
Cc: devel at pidgin.im
Subject: Re: Make.mingw for nullclient?

On Sat, Sep 01, 2007 at 11:48:23AM +0200, Joanna Chopard (jchopard)
wrote:
> Hello,
>
> I've just managed to build pidgin and now want to understand
libpurple.
> I looked under libpurple/example which has the nullclient.c, but 
> didn't see Make.mingw for it.
>
> I'm still not clear what all the different makefile types are for:
> Makefile.in, Makefile.am, Makefile.mingw, and why the latter is 
> missing in the example folder...

The Makefile.am:s are what we write to control the build process, the
Makefile.in:s are generated (from the Makefile.am:s) by the autogen.sh
script at distribution time, the Makefile.mingw:s are hand-written files
for use when building pidgin on Windows.

On non-Windows systems the configure script would generate the final
Makefile:s from the Makefile.in:s when run.

> Do I need to run the configure script at the top level to have it 
> generated?

When building pidgin for Windows you don't use the configure script.

> I'd appreciate if you could just take a few seconds and clue me in so 
> I can get started:)

You will need to write an appropriate Makefile.mingw in order to build
the nullclient (which may or may not work on Windows I'm not sure) or
hope that the right pidgin people write one for you. =)

> Thanks,
> Joanna

	-Etan

_______________________________________________
Devel mailing list
Devel at pidgin.im
http://pidgin.im/cgi-bin/mailman/listinfo/devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile.mingw
Type: application/octet-stream
Size: 1553 bytes
Desc: Makefile.mingw
URL: <http://pidgin.im/pipermail/devel/attachments/20070903/7ede1331/attachment-0002.obj>


More information about the Devel mailing list