How to use static lib(that was built from VS) inside the UMDF ddk build

NTDEV
1

I am having trouble intergrating my static libraries to my UMDF driver…I got warning LNK4229 ‘/FAILIFMISTACH:_MSC_VER=1600’

I already applied the #pragma warning(disable:4229)

and still no luck…

any ideas?

2

The #pragma warning applies to COMPILER warnings, not LINKER warnings. So
it really doesn’t matter what you tell the COMPILER.

If you want to disable linker errors, you add /IGNORE:4229 to the linker
command line. As far as I know, this is still an undocumented option.
See

http://www.flounder.com/msdn_documentation_errors_and_omissions.htm#LNK4089

Of course, there is a question as to whether or not this warning actually
indicates a serious problem. I can’t comment on that, since I haven’t
tried to use static libraries in a driver.
joe

I am having trouble intergrating my static libraries to my UMDF driver…I
got warning LNK4229 ‘/FAILIFMISTACH:_MSC_VER=1600’

I already applied the #pragma warning(disable:4229)

and still no luck…

any ideas?

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

I cannot find any reference on how to add the /IGNORE:XXXX to the “build -xx” command in winDDK

4

Hmm. Try LINKER_FLAGS. Maybe LINK_FLAGS.

Worst case, adding it to TARGET_LIBS would probably work, but I’m sure that
there is a better way.

Good luck,

Mm
On Nov 20, 2011 11:20 PM, wrote:

> I cannot find any reference on how to add the /IGNORE:XXXX to the “build
> -xx” command in winDDK
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

5

Make that LINK_LIBS

MM
On Nov 20, 2011 11:55 PM, “Martin O’Brien” <
xxxxx@gmail.com> wrote:

Hmm. Try LINKER_FLAGS. Maybe LINK_FLAGS.

Worst case, adding it to TARGET_LIBS would probably work, but I’m sure
that there is a better way.

Good luck,

Mm
On Nov 20, 2011 11:20 PM, wrote:
>
>> I cannot find any reference on how to add the /IGNORE:XXXX to the “build
>> -xx” command in winDDK
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>

6

here is the warning, i cannot disable it.

1>warnings in directory c:\serial\lvc2
1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid directive
‘/FAILIFMISMATCH:_MSC_VER=1600’ encountered; ignored
1>errors in directory c:\serial\lvc2
1>link : error LNK1218: warning treated as error; no output file generated

I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no luck…
I already included the library in the target libs and still doesn’t work…

I think nested library doesn’t work, because I created a static library as libx1 from VS which also uses another static library as libx2… so basically I used the libx1 in UMDF module…

7

How about adding /WX? Not a great solution, by any means.

I meant adding ‘/IGNORE:4229’ like this:

TARGETLIBS=$(TARGETLIBS) /IGNORE:4229

Again, ugly, but it’s possible that LINKER_FLAGS gets filtered through the
magic of Makefile.new; or not, I really don’t know, but TARGETLIBS won’t (or
at least I don’t think it will).

Of course, another possibility is that this #pragma use exists for a reason.
I don’t know the answer to that either, alas, but it’s certainly possibly
that some C++ things could take issue with binary compatibility.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 21, 2011 1:44 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to use static lib(that was built from VS) inside the
UMDF ddk build

here is the warning, i cannot disable it.

1>warnings in directory c:\serial\lvc2
1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid directive
‘/FAILIFMISMATCH:_MSC_VER=1600’ encountered;
ignored
1>errors in directory c:\serial\lvc2
1>link : error LNK1218: warning treated as error; no output file generated

I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no luck…
I already included the library in the target libs and still doesn’t work…

I think nested library doesn’t work, because I created a static library as
libx1 from VS which also uses another static library as libx2… so
basically I used the libx1 in UMDF module…

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

8

The #pragma you referenced DOES exist “for a reason”. Its reason is to
tell the COMPILER to establish a property of certain messages. Now, as I
explained, you are getting a LINKER error, and why you would thing a
COMPILER directive would affect the LINKER is quite surprising.

You DO understand the difference between a compiler and the linker? I am
continually surprised by the number of my students who have no idea about
what a linker is or does.

Note that the message you are getting tells you that an illegal option is
supplied on the linker command line, that is, the /FAILIFMISTATCH_MSC_VER
switch is not recognized by the linker you are using. I have found a
number of bugs in build scripts, some of which have seriously broken the
user-level VS2010 builds, and it is always possible you have hit a case
where the script has put something in the linker command line that is not
understood by the linker. In this case, you should report it to
Microsoft. Note that you can enable options to have the linker print out
its command line and other details while it is working.

Note also that you can add #pragma comment(linker, “XXX”)

and the XXX is interpreted as part of the linker command line; for example

#pragma comment(linker, “/Section:whatever,rws”)

which marks the segment (named by #prama data_seg(“whatever”) ) as read,
write and shared. So if you don’t see this on the command line, there
might be a #pragma in your static library build that added that option to
the command line.

joe

How about adding /WX? Not a great solution, by any means.

I meant adding ‘/IGNORE:4229’ like this:

TARGETLIBS=$(TARGETLIBS) /IGNORE:4229

Again, ugly, but it’s possible that LINKER_FLAGS gets filtered through the
magic of Makefile.new; or not, I really don’t know, but TARGETLIBS won’t
(or
at least I don’t think it will).

Of course, another possibility is that this #pragma use exists for a
reason.
I don’t know the answer to that either, alas, but it’s certainly possibly
that some C++ things could take issue with binary compatibility.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 21, 2011 1:44 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to use static lib(that was built from VS) inside
the
UMDF ddk build

here is the warning, i cannot disable it.

1>warnings in directory c:\serial\lvc2
1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid
directive
‘/FAILIFMISMATCH:_MSC_VER=1600’
encountered;
ignored
1>errors in directory c:\serial\lvc2
1>link : error LNK1218: warning treated as error; no output file generated

I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no luck…
I already included the library in the target libs and still doesn’t
work…

I think nested library doesn’t work, because I created a static library as
libx1 from VS which also uses another static library as libx2… so
basically I used the libx1 in UMDF module…

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

9

xxxxx@gmail.com wrote:

here is the warning, i cannot disable it.

1>warnings in directory c:\serial\lvc2
1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid directive
‘/FAILIFMISMATCH:_MSC_VER=1600’ encountered; ignored
1>errors in directory c:\serial\lvc2
1>link : error LNK1218: warning treated as error; no output file generated

This library was built with Visual Studio 2010, and you’re trying to use
it with an older compiler/linker. That directive appears to be an
attempt to ensure that the library does not get linked with stuff from
any older compiler. In that sense, what you’re trying to do is
inherently risky.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

10

>Now, as I explained, you are getting a LINKER error, and why you would
thing a COMPILER directive would affect the LINKER is quite surprising.

Because this is new to him, and you’re helping with the confusion by making
a big deal out of the terminology and then proceeding to use it casually.

Also, I can see why he thinks this is being caused by a compiler directive,
because that is what’s happening. Yes it is a linker error, caused by a bad
command line option, but it’s getting inserted by #pragma, which is a
compiler directive.

This is exactly the case of your example:

#pragma comment(linker, “/Section:whatever,rws”)

COMPILER directive -> affects the LINKER

I assume that you mean ‘switch’ or ‘option,’ but even then, I just don’t see
why it’s that hard to understand why he’s confused.

And then there’s ‘-MT’ which unambiguously does exactly what you find
surprising. And then there’s ‘-link’…

It’s being added by VS2010, I believe. I don’t think that any build script
is required to produce this (nor is he using one).

I believe that this gets added by VS2010 to prevent binary compatibility
issues with earlier versions of the compiler. I’m pretty sure that it has
to do with STL (debug iterators, I think).

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@flounder.com
Sent: Monday, November 21, 2011 9:24 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to use static lib(that was built from VS) inside
the UMDF ddk build

The #pragma you referenced DOES exist “for a reason”. Its reason is to tell
the COMPILER to establish a property of certain messages. Now, as I
explained, you are getting a LINKER error, and why you would thing a
COMPILER directive would affect the LINKER is quite surprising.

You DO understand the difference between a compiler and the linker? I am
continually surprised by the number of my students who have no idea about
what a linker is or does.

Note that the message you are getting tells you that an illegal option is
supplied on the linker command line, that is, the /FAILIFMISTATCH_MSC_VER
switch is not recognized by the linker you are using. I have found a number
of bugs in build scripts, some of which have seriously broken the user-level
VS2010 builds, and it is always possible you have hit a case where the
script has put something in the linker command line that is not understood
by the linker. In this case, you should report it to Microsoft. Note that
you can enable options to have the linker print out its command line and
other details while it is working.

Note also that you can add #pragma comment(linker, “XXX”)

and the XXX is interpreted as part of the linker command line; for example

#pragma comment(linker, “/Section:whatever,rws”)

which marks the segment (named by #prama data_seg(“whatever”) ) as read,
write and shared. So if you don’t see this on the command line, there might
be a #pragma in your static library build that added that option to the
command line.

joe

How about adding /WX? Not a great solution, by any means.

I meant adding ‘/IGNORE:4229’ like this:

TARGETLIBS=$(TARGETLIBS) /IGNORE:4229

Again, ugly, but it’s possible that LINKER_FLAGS gets filtered through
the magic of Makefile.new; or not, I really don’t know, but TARGETLIBS
won’t (or at least I don’t think it will).

Of course, another possibility is that this #pragma use exists for a
reason.
I don’t know the answer to that either, alas, but it’s certainly
possibly that some C++ things could take issue with binary compatibility.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 21, 2011 1:44 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to use static lib(that was built from VS)
inside the UMDF ddk build

here is the warning, i cannot disable it.

1>warnings in directory c:\serial\lvc2
1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid
directive
‘/FAILIFMISMATCH:_MSC_VER=1600’
encountered;
ignored
1>errors in directory c:\serial\lvc2
1>link : error LNK1218: warning treated as error; no output file
1>generated

I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no luck…
I already included the library in the target libs and still doesn’t
work…

I think nested library doesn’t work, because I created a static
library as
libx1 from VS which also uses another static library as libx2… so
basically I used the libx1 in UMDF module…

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

11

Yes, I realized after I went to bed that a compiler directive COULD affect
the linker, which is why I posted an update this morning.

However, #pragam warning is most distinctly a compiler directive.

I was bothered by the fact that someone who is writing a driver and using
a static library does not seem to understand the difference. I would
expect that the role of the linker, and the fact that the message came out
as LNKxxxx instead of Cxxxx might have made this obvious.

I am making a big deal of the terminology because, frankly, the problem
seems to be a failure to understand the terminology.

joe

>Now, as I explained, you are getting a LINKER error, and why you would
thing a COMPILER directive would affect the LINKER is quite surprising.

Because this is new to him, and you’re helping with the confusion by
making
a big deal out of the terminology and then proceeding to use it casually.

Also, I can see why he thinks this is being caused by a compiler
directive,
because that is what’s happening. Yes it is a linker error, caused by a
bad
command line option, but it’s getting inserted by #pragma, which is a
compiler directive.

This is exactly the case of your example:

#pragma comment(linker, “/Section:whatever,rws”)

COMPILER directive -> affects the LINKER

I assume that you mean ‘switch’ or ‘option,’ but even then, I just don’t
see
why it’s that hard to understand why he’s confused.

And then there’s ‘-MT’ which unambiguously does exactly what you find
surprising. And then there’s ‘-link’…

It’s being added by VS2010, I believe. I don’t think that any build
script
is required to produce this (nor is he using one).

I believe that this gets added by VS2010 to prevent binary compatibility
issues with earlier versions of the compiler. I’m pretty sure that it has
to do with STL (debug iterators, I think).

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@flounder.com
Sent: Monday, November 21, 2011 9:24 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to use static lib(that was built from VS) inside
the UMDF ddk build

The #pragma you referenced DOES exist “for a reason”. Its reason is to
tell
the COMPILER to establish a property of certain messages. Now, as I
explained, you are getting a LINKER error, and why you would thing a
COMPILER directive would affect the LINKER is quite surprising.

You DO understand the difference between a compiler and the linker? I am
continually surprised by the number of my students who have no idea about
what a linker is or does.

Note that the message you are getting tells you that an illegal option is
supplied on the linker command line, that is, the /FAILIFMISTATCH_MSC_VER
switch is not recognized by the linker you are using. I have found a
number
of bugs in build scripts, some of which have seriously broken the
user-level
VS2010 builds, and it is always possible you have hit a case where the
script has put something in the linker command line that is not understood
by the linker. In this case, you should report it to Microsoft. Note
that
you can enable options to have the linker print out its command line and
other details while it is working.

Note also that you can add #pragma comment(linker, “XXX”)

and the XXX is interpreted as part of the linker command line; for example

#pragma comment(linker, “/Section:whatever,rws”)

which marks the segment (named by #prama data_seg(“whatever”) ) as read,
write and shared. So if you don’t see this on the command line, there
might
be a #pragma in your static library build that added that option to the
command line.

joe

> How about adding /WX? Not a great solution, by any means.
>
> I meant adding ‘/IGNORE:4229’ like this:
>
> TARGETLIBS=$(TARGETLIBS) /IGNORE:4229
>
> Again, ugly, but it’s possible that LINKER_FLAGS gets filtered through
> the magic of Makefile.new; or not, I really don’t know, but TARGETLIBS
> won’t (or at least I don’t think it will).
>
> Of course, another possibility is that this #pragma use exists for a
> reason.
> I don’t know the answer to that either, alas, but it’s certainly
> possibly that some C++ things could take issue with binary
> compatibility.
>
> mm
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@gmail.com
> Sent: Monday, November 21, 2011 1:44 AM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] How to use static lib(that was built from VS)
> inside the UMDF ddk build
>
> here is the warning, i cannot disable it.
>
> 1>warnings in directory c:\serial\lvc2
> 1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid
> directive
> ‘/FAILIFMISMATCH:_MSC_VER=1600’
> encountered;
> ignored
> 1>errors in directory c:\serial\lvc2
> 1>link : error LNK1218: warning treated as error; no output file
> 1>generated
>
> I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no
> luck…
> I already included the library in the target libs and still doesn’t
> work…
>
> I think nested library doesn’t work, because I created a static
> library as
> libx1 from VS which also uses another static library as libx2… so
> basically I used the libx1 in UMDF module…
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

12

Still not clear on how you helped here.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@flounder.com
Sent: Monday, November 21, 2011 10:13 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to use static lib(that was built from VS) inside
the UMDF ddk build

Yes, I realized after I went to bed that a compiler directive COULD affect
the linker, which is why I posted an update this morning.

However, #pragam warning is most distinctly a compiler directive.

I was bothered by the fact that someone who is writing a driver and using a
static library does not seem to understand the difference. I would expect
that the role of the linker, and the fact that the message came out as
LNKxxxx instead of Cxxxx might have made this obvious.

I am making a big deal of the terminology because, frankly, the problem
seems to be a failure to understand the terminology.

joe

>Now, as I explained, you are getting a LINKER error, and why you would
thing a COMPILER directive would affect the LINKER is quite surprising.

Because this is new to him, and you’re helping with the confusion by
making a big deal out of the terminology and then proceeding to use it
casually.

Also, I can see why he thinks this is being caused by a compiler
directive, because that is what’s happening. Yes it is a linker
error, caused by a bad command line option, but it’s getting inserted
by #pragma, which is a compiler directive.

This is exactly the case of your example:

#pragma comment(linker, “/Section:whatever,rws”)

COMPILER directive -> affects the LINKER

I assume that you mean ‘switch’ or ‘option,’ but even then, I just
don’t see why it’s that hard to understand why he’s confused.

And then there’s ‘-MT’ which unambiguously does exactly what you find
surprising. And then there’s ‘-link’…

It’s being added by VS2010, I believe. I don’t think that any build
script is required to produce this (nor is he using one).

I believe that this gets added by VS2010 to prevent binary
compatibility issues with earlier versions of the compiler. I’m
pretty sure that it has to do with STL (debug iterators, I think).

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@flounder.com
Sent: Monday, November 21, 2011 9:24 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to use static lib(that was built from VS)
inside the UMDF ddk build

The #pragma you referenced DOES exist “for a reason”. Its reason is
to tell the COMPILER to establish a property of certain messages.
Now, as I explained, you are getting a LINKER error, and why you would
thing a COMPILER directive would affect the LINKER is quite
surprising.

You DO understand the difference between a compiler and the linker? I
am continually surprised by the number of my students who have no idea
about what a linker is or does.

Note that the message you are getting tells you that an illegal option
is supplied on the linker command line, that is, the
/FAILIFMISTATCH_MSC_VER switch is not recognized by the linker you are
using. I have found a number of bugs in build scripts, some of which
have seriously broken the user-level
VS2010 builds, and it is always possible you have hit a case where the
script has put something in the linker command line that is not
understood by the linker. In this case, you should report it to
Microsoft. Note that you can enable options to have the linker print
out its command line and other details while it is working.

Note also that you can add #pragma comment(linker, “XXX”)

and the XXX is interpreted as part of the linker command line; for
example

#pragma comment(linker, “/Section:whatever,rws”)

which marks the segment (named by #prama data_seg(“whatever”) ) as
read, write and shared. So if you don’t see this on the command line,
there might be a #pragma in your static library build that added that
option to the command line.

joe

> How about adding /WX? Not a great solution, by any means.
>
> I meant adding ‘/IGNORE:4229’ like this:
>
> TARGETLIBS=$(TARGETLIBS) /IGNORE:4229
>
> Again, ugly, but it’s possible that LINKER_FLAGS gets filtered
> through the magic of Makefile.new; or not, I really don’t know, but
> TARGETLIBS won’t (or at least I don’t think it will).
>
> Of course, another possibility is that this #pragma use exists for a
> reason.
> I don’t know the answer to that either, alas, but it’s certainly
> possibly that some C++ things could take issue with binary
> compatibility.
>
> mm
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@gmail.com
> Sent: Monday, November 21, 2011 1:44 AM
> To: Windows System Software Devs Interest List
> Subject: RE:[ntdev] How to use static lib(that was built from VS)
> inside the UMDF ddk build
>
> here is the warning, i cannot disable it.
>
> 1>warnings in directory c:\serial\lvc2
> 1>c:\xxxx\xx2\mydsp1.lib(mydsp1lib.obj) : warning LNK4229: invalid
> directive
> ‘/FAILIFMISMATCH:_MSC_VER=1600’
> encountered;
> ignored
> 1>errors in directory c:\serial\lvc2
> 1>link : error LNK1218: warning treated as error; no output file
> 1>generated
>
> I applied LINKER_FLAGS = $(LINKER_FLAGS) /IGNORE:4229 and still no
> luck…
> I already included the library in the target libs and still doesn’t
> work…
>
> I think nested library doesn’t work, because I created a static
> library as
> libx1 from VS which also uses another static library as libx2… so
> basically I used the libx1 in UMDF module…
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

13

Yeah, Tim Roberts is right, this is kinda risky… we are using a third party library that was built in VS 2010…and we use it in UMDF DDK building…

This may end up with something like porting or edit the source of the library and compile it again with the older compiler… inorder to make it work I think…

Thanks MM for the support you have the point also…

14

Glad I could help.

Good luck,

Mm
On Nov 21, 2011 8:37 PM, wrote:

> Yeah, Tim Roberts is right, this is kinda risky… we are using a third
> party library that was built in VS 2010…and we use it in UMDF DDK
> building…
>
> This may end up with something like porting or edit the source of the
> library and compile it again with the older compiler… inorder to make it
> work I think…
>
> Thanks MM for the support you have the point also…
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

15

Alternatively, there is way less magic involved with a UMDF driver. It is just a DLL project really that includes the UMDF header. The alternative would be to build the umdf driver in VS2010 as a dll project and then link the lib.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Monday, November 21, 2011 8:42 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to use static lib(that was built from VS) inside the UMDF ddk build

Glad I could help.

Good luck,

Mm
On Nov 21, 2011 8:37 PM, > wrote:
Yeah, Tim Roberts is right, this is kinda risky… we are using a third party library that was built in VS 2010…and we use it in UMDF DDK building…

This may end up with something like porting or edit the source of the library and compile it again with the older compiler… inorder to make it work I think…

Thanks MM for the support you have the point also…

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

16

@ Doron Holan, yeah that is right… I might open up with this rather than porting a huge library…

I used to have CLI as of now than VS for ddk building…
do you have any link or information related to using VS for UMDF building? i might also dig some with goggle…:smiley:

17

There is nothing out there in terms of docs. It is not supported really, but building a dll is less build setting dependent / magical than building a driver, so it is easier to make the leap

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Monday, November 21, 2011 9:34 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to use static lib(that was built from VS) inside the UMDF ddk build

@ Doron Holan, yeah that is right… I might open up with this rather than porting a huge library…

I used to have CLI as of now than VS for ddk building…
do you have any link or information related to using VS for UMDF building? i might also dig some with goggle…:smiley:

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

18

> Yeah, Tim Roberts is right, this is kinda risky… we are using a third party library that was built in VS

2010

I’m just plain amazed that people do ship the .lib files for the newest toolchain only.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

19

On 22-Nov-2011 10:21, Maxim S. Shatskih wrote:

I’m just plain amazed that people do ship the .lib files for the newest toolchain only.

People may have limited resources and ship only configurations that they
can maintain. Which often are for more recent toolchain.
If users need something else, they can just ask the vendor.
– pa