From: <alp...@ea...> - 2007-12-05 17:32:50
|
At 09:53 PM 12/2/07 +0000, you wrote: >On Sunday 02 December 2007 18:44, alp...@ea... wrote: >> >-lanything does not belong in LDFLAGS. =A0It should go in LIBS. =A0This >> >matters for ordering. >> >Brian >> ya but LDFLAGS=3D-lcomctl32 >> got the GUI up and runinng! >> what should I be reading now regarding "It should go in LIBS"? >Brian is 100% correct. Autotooled makefiles pass two macros (in=20 >particular) to ld; one is LDFLAGS, the other is LIBS. Technically,=20 >LDFLAGS should be reserved for library search paths, i.e. the likes of=20 >LDFLAGS=3D'-L /path/to/libs ...', while the libs themselves should be=20 >passed through LIBS=3D'-lsomelib ...'. LDFLAGS are passed early in the=20 >link argument list; LIBS come last, where the libraries must be listed. =20 >That you were successful using LDFLAGS=3D-anything may be fortuitous, but= =20 >LIBS=3D-lsomething is the correct way, and is more robust. > >Regards, >Keith. I left cause it seemed you guys didnt have time to talk to me, thank you for that reply. where's a tutorial on this: here's all I know: (final attempt to resolve this here) LDFLAGS=3D-lcomctl32 Links to F:\mingw\lib\libcomctl32.a GUI links and runs Renaming F:\mingw\lib\libcomctl32.b Error We know that path And that's all we know, How to find a tutorial And learn to link 2 libs? libcomctl32.a libwinmm.a pouring over tons of makefiles yikes this is heinous indeed |