On Fri, Sep 10, 2010 at 4:18 PM, Kai Tietz <[email protected]> wrote: >>> Hrmph, I guess the only way here is to bite the bullet and >>> really add a -lmingwex after all other libs. However it would >>> have been really nice if we provided them as always_inlines >> >> Yes changing the Makefile to link to libmingwex will make >> the driver building through. >> >> DRIVER_LDFLAGS = -s -shared -Wl,--entry,DriverEntry \ >> -nostartfiles -nostdlib -L. -lusbd -lntoskrnl -lhal -lmingwex >> >> Thanks for all the helps. The support here is really superior! >> >> One more question, what will be the potential issues of linking >> to libmingwex for the libusb0.sys kernel driver? >> > > Well, libmingwex code is written for user-mode applications. This > means that there is some API used, which is in kernel-mode not > necessarily present. (See as example those VirtualAlloc routines). > Also math can be an issue, as kernel doesn't setup x87 stack AFAIK. > But in special case of intrinsics there shouldn't be any side-effects AFAICS. >
Thanks for the explanations. Now I need to test this MinGW-w64 build driver. I will come back if I encounter problems. -- Xiaofan ------------------------------------------------------------------------------ Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
