On Thu, Dec 30, 2010 at 13:39, Rich Shepard <[email protected]> wrote: > On Thu, 30 Dec 2010, Rich Shepard wrote: > >> If I can find where to add the library reference, I'll do this. > > Now I know that I begin the line with LDFLAGS="-ldl" ./configure ...
exactly. > Now to get it to find wxWidgets. quite possibly in a similar way. LDFLAGS get passed to the linker (typically gcc invoking ld for you, which wants -llibraryname. you can chain them, "-ldl -lwxwidgets -lbob ...") CFLAGS (set the same way) get passed to the compiler so you might need something like "-i/usr/src/wxwidgets/include" (change to reflect your setup, obviously). the preferred way for this to work is that you inform configure about the install location directly with something like ./configure --enable-wxwidgets=/path/to/location (if --enable-wxwidgets doesn't work by itself). you can find available flags listed via: ./configure --help in theory, when you tell configure where a thing is installed (via --enable-bob=/path/to/bob), it can figure out the rest. in practice, if things aren't installed both somewhere configure can find (perhaps via your gentle nudging) AND installed in the way configure is expecting (ie some packages stick their include files in /usr/include/package, others in /usr/local/package/include, etc), you have to start doing kind of nasty hackery with CFLAGS and LDFLAGS. oh, yeah--and if you for some reason don't store the libs for the package in a place /etc/ld.so.conf knows about, things get even more fun. google 'setting rpath' sometime for a good time. there have been months on the job when 90% of my work was taming ./configure. once i got stuff compiled, it usually just worked. (building KDE against our self-built x11 server on solaris was a multi-month process whose completed results were probably never actually used by anyone. sigh.) _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
