Re: GTK+ externals are unresolved

2008-12-22 Thread M . O . D .
> gcc -o murg murg.c `pkg-config --cflags --libs gtk+-2.0` This worked, and it sounded so similar to what Greg Chicares recommended earlier that I went back to his message and rearranged the command again as he described, and that also worked this time. I don't know how I dorked that up the fir

Re: GTK+ externals are unresolved

2008-12-21 Thread Yaakov (Cygwin/X)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 M.O.D. wrote: > Thanks for your comments, Yaakov. As you suspected, the order of the link > libraries made no difference. > > I downloaded all of Cygwin at one time, in about an hour. I have not done > anything I know of that would mix versions.

Re: GTK+ externals are unresolved

2008-12-21 Thread M . O . D .
Thanks for your comments, Yaakov. As you suspected, the order of the link libraries made no difference. I downloaded all of Cygwin at one time, in about an hour. I have not done anything I know of that would mix versions. If there is some kind of library mismatch, I have no idea what to do abou

Re: GTK+ externals are unresolved

2008-12-20 Thread Yaakov (Cygwin/X)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Reini Urban wrote: > Anyway, it compiles with my fixed order and gives the unresolved symbols > with the original $(pkg-config --libs gtk+-2.0) order of libs. > Please try it our yourself. Listen, I've been building GNOME for years now. pkg-config'

Re: GTK+ externals are unresolved

2008-12-20 Thread Reini Urban
Yaakov (Cygwin/X) schrieb: René Berber wrote: You're wrong, libraries shared or static are dealt the same way by the compiler which looks for its list of unresolved symbols and doesn't re-scan libraries when another symbol appears. Since I apparently didn't make myself clear the last two times

Re: GTK+ externals are unresolved

2008-12-17 Thread Yaakov (Cygwin/X)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 René Berber wrote: > You're wrong, libraries shared or static are dealt the same way by the > compiler which looks for its list of unresolved symbols and doesn't > re-scan libraries when another symbol appears. Since I apparently didn't make myself

Re: GTK+ externals are unresolved

2008-12-17 Thread René Berber
Yaakov (Cygwin/X) wrote: > Once again, these are all shared libraries, in which case the order > among them does NOT matter. But if any of them were static, then this > top-down order is correct. [snip] You're wrong, libraries shared or static are dealt the same way by the compiler which looks f

Re: GTK+ externals are unresolved

2008-12-17 Thread Yaakov (Cygwin/X)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Reini Urban wrote: > I tend to disagree. > With the original order: > -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 > -lpangoxft-1.0 -lXft -lfreetype -lz -lXrender -lXext -lfontconfig > -lpangox-1.0 -lX11 -lpango-1.0 -lm -lg

Re: GTK+ externals are unresolved

2008-12-17 Thread Reini Urban
Yaakov (Cygwin/X) schrieb: Reini Urban wrote: The order of libs is wrong for $(pkg-config --libs gtk+-2.0) -lgtk-x11-2.0 -lgdk-x11-2.0 should be at the end. $ pkg-config --libs gtk+-2.0 -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lXft -lfreetype -lz

Re: GTK+ externals are unresolved

2008-12-16 Thread Yaakov (Cygwin/X)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Reini Urban wrote: > > The order of libs is wrong for $(pkg-config --libs gtk+-2.0) > > -lgtk-x11-2.0 -lgdk-x11-2.0 should be at the end. > > $ pkg-config --libs gtk+-2.0 > -L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 >

Re: GTK+ externals are unresolved

2008-12-16 Thread Reini Urban
M.O.D. schrieb: John Emmas tiscali.co.uk> writes: Perhaps you're missing the file 'libgtk-x11-2.0.la' I included a directory listing in my message, showing that this file is there. Perhaps you and John Emmas should read the messages before you reply to them. The order of libs is wrong for

Re: GTK+ externals are unresolved

2008-12-16 Thread M . O . D .
John Emmas tiscali.co.uk> writes: > Perhaps you're missing the file 'libgtk-x11-2.0.la' I included a directory listing in my message, showing that this file is there. Perhaps you and John Emmas should read the messages before you reply to them. -- Unsubscribe info: http://cygwin.com/ml/#

Re: GTK+ externals are unresolved

2008-12-15 Thread Andreas Eibach
- Original Message - From: "John Emmas" To: Sent: Monday, December 15, 2008 11:45 PM Subject: Re: GTK+ externals are unresolved > Perhaps you're missing the file 'libgtk-x11-2.0.la' (it should be in /lib/). > Try linking to 'libgtk-x11-2.0.dll.a

Re: GTK+ externals are unresolved

2008-12-15 Thread M . O . D .
> Does it work if you move the libraries after the source files? No, that doesn't make any difference. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: GTK+ externals are unresolved

2008-12-15 Thread John Emmas
- Original Message - From: "M.O.D." Subject: GTK+ externals are unresolved Why are the GTK externals going unresolved on Cygwin? Thanks, Ollie $ cc `pkg-config --cflags --libs gtk+-2.0` murg.c -o murg /cyg

Re: GTK+ externals are unresolved

2008-12-15 Thread Greg Chicares
On 2008-12-15 21:19Z, M.O.D. wrote: > When I compile a GTK+ application in Cygwin, all the GTK externals are > unresolved. > > $ cc `pkg-config --cflags --libs gtk+-2.0` murg.c -o murg Does it work if you move the libraries after the source files? Something like this: $ cc `pkg-config --cflag