[nvmewin] sources miss wmilib.lib and scsiwmi.lib

Alex Chang Alex.Chang at pmcs.com
Wed Oct 15 09:23:19 PDT 2014


Hi Peng,

We had decided to migrate to VS 2013 and driver compiling and linking is done within VS 2013. Are you still using command prompt to build the driver after VS 2013 installed?

Thanks,
Alex

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Thomas Freeman
Sent: Wednesday, October 15, 2014 7:08 AM
To: cheng.peng at memblaze.com; nvmewin
Subject: Re: [nvmewin] sources miss wmilib.lib and scsiwmi.lib

I did not update the sources file for those changes.
My understanding is that with WDK 8.1 "sources" is not used. The project builds fine without these changes.

Alex, do those changes need to be put into sources?
If it is updated, nvmeWmi.c also needs to be added.



Tom Freeman

Software Engineer, Device Manager and Driver Development
HGST, a Western Digital company
Thomas.Freeman at hgst.com<mailto:Thomas.Freeman at hgst.com>
507-322-2311

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of cheng.peng at memblaze.com<mailto:cheng.peng at memblaze.com>
Sent: Wednesday, October 15, 2014 1:22 AM
To: nvmewin
Subject: [nvmewin] sources miss wmilib.lib and scsiwmi.lib

Hi all:

should be wmilib.lib and scsiwmi.lib included in trunk\source\sources file?

________________________________
cheng.peng at memblaze.com<mailto:cheng.peng at memblaze.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20141015/45d01ada/attachment.html>


More information about the nvmewin mailing list