Yes, we could do some streamlining here, as most compilers and hbmk/hbmk2/gnu-make will use slightly different win syslib list.
gnu-make should use the minimum required to build Harbour libs and binaries. This should still be cleaned. hbmk2 could get a wider list, although I'm unsure where to draw the line. Listing all libs is pbly a performance killer. Anyhow there is utils/hbmk2/examples/winapi.hbp which has a quite generic set of common libs. It can be used even now, it include the two you've just said. Brgds, Viktor On Wed, Mar 4, 2009 at 3:37 PM, Lorenzo Fiorini <[email protected]>wrote: > In my local tree, I've always added -lmapi32 and -lmpr: > > ... > HB_SYS_LIBS="${HB_SYS_LIBS} -luser32 -lwinspool -lgdi32 -lcomctl32 > -lcomdlg32 -lole32 -loleaut32 -luuid -lwsock32 -lws2_32 -lmapi32 > -lmpr" > ... > > - mapi32 is used for mapisendmail which is a quite common way to send > emails from Win apps > - mpr is necessary for hbct net* functions. > > Adding them to the list will not hurt anyone and will make life easier > when hbct is used. > > best regards, > Lorenzo > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
