Hi all,
I have custom build steps in my makefile.inc: I.e. signing with signtool.
I haven’t found a way yet of propagating any error happening to
ddkbuild and VS2010. In case of an error (i.e. with signing) the build
step just silently fails and the build process continues.
How can I make sure that an error (or a progress indication) is
displayed in the build window of the VS2010 and the build itself is
stopped?
Is ddkbuild really the way to go when building with VS2010?
Thanks,
Hagen.
Well I use it all the time, but I’m biased. Note that the problem is
that the “build process continues” - that isn’t a ddkbuild problem so
much as it is a build.exe (WDK tool) problem. Try the same thing from
the WDK command shell.
Mark Roddy
On Mon, Jun 27, 2011 at 5:34 AM, hagen wrote:
> Hi all,
> I have custom build steps in my makefile.inc: I.e. signing with signtool.
> I haven’t found a way yet of propagating any error happening to
> ddkbuild and VS2010. In case of an error (i.e. with signing) the build
> step just silently fails and the build process continues.
> How can I make sure that an error (or a progress indication) is
> displayed in the build window of the VS2010 and the build itself is
> stopped?
> Is ddkbuild really the way to go when building with VS2010?
>
> Thanks,
> Hagen.
>
> —
> 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
>
Oh and the format for text that is an error is approximately
“error.*[CDLU][0-9]*” using the findstr regex syntax.
So your makefile.inc could test for signing errors and emit something
that matched the error string syntax and then VS might pick it up. or
not.
Mark Roddy
On Mon, Jun 27, 2011 at 5:03 PM, Mark Roddy wrote:
> Well I use it all the time, but I’m biased. Note that the problem is
> that the “build process continues” - that isn’t a ddkbuild problem so
> much as it is a build.exe (WDK tool) problem. Try the same thing from
> the WDK command shell.
>
> Mark Roddy
>
>
>
> On Mon, Jun 27, 2011 at 5:34 AM, hagen wrote:
>> Hi all,
>> I have custom build steps in my makefile.inc: I.e. signing with signtool.
>> I haven’t found a way yet of propagating any error happening to
>> ddkbuild and VS2010. In case of an error (i.e. with signing) the build
>> step just silently fails and the build process continues.
>> How can I make sure that an error (or a progress indication) is
>> displayed in the build window of the VS2010 and the build itself is
>> stopped?
>> Is ddkbuild really the way to go when building with VS2010?
>>
>> Thanks,
>> Hagen.
>>
>> —
>> 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
>>
>
>So your makefile.inc could test for signing errors and emit something that
matched the error string syntax and then VS might pick it up. Or not.
I’m not a big VS user, but when I have to use it and BUILD together, I tend
to do things this. I find it works better than other options, not any of
them work all that well due to what Mark already said - the problem is
basically BUILD.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Monday, June 27, 2011 5:51 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] makefile.inc ddkbuild+VS2010
Oh and the format for text that is an error is approximately
“error.*[CDLU][0-9]*” using the findstr regex syntax.
So your makefile.inc could test for signing errors and emit something
that matched the error string syntax and then VS might pick it up. or
not.
Mark Roddy
On Mon, Jun 27, 2011 at 5:03 PM, Mark Roddy wrote:
> Well I use it all the time, but I’m biased. Note that the problem is
> that the “build process continues” - that isn’t a ddkbuild problem so
> much as it is a build.exe (WDK tool) problem. Try the same thing from
> the WDK command shell.
>
> Mark Roddy
>
>
>
> On Mon, Jun 27, 2011 at 5:34 AM, hagen wrote:
>> Hi all,
>> I have custom build steps in my makefile.inc: I.e. signing with signtool.
>> I haven’t found a way yet of propagating any error happening to
>> ddkbuild and VS2010. In case of an error (i.e. with signing) the build
>> step just silently fails and the build process continues.
>> How can I make sure that an error (or a progress indication) is
>> displayed in the build window of the VS2010 and the build itself is
>> stopped?
>> Is ddkbuild really the way to go when building with VS2010?
>>
>> Thanks,
>> Hagen.
>>
>> —
>> 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
Hi Mark & Martin,
thanks for the info!
Hagen.
On Mon, Jun 27, 2011 at 11:55 PM, Martin O’Brien
wrote:
>>So your makefile.inc could test for signing errors and emit something that
> matched the error string syntax and then VS might pick it up. Or not.
>
> I’m not a big VS user, but when I have to use it and BUILD together, I tend
> to do things this. ?I find it works better than other options, not any of
> them work all that well due to what Mark already said - the problem is
> basically BUILD.
>
>
>
> Good luck,
>
> mm
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
> Sent: Monday, June 27, 2011 5:51 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] makefile.inc ddkbuild+VS2010
>
> Oh and the format for text that is an error is approximately
> “error.[CDLU][0-9]” using the findstr regex syntax.
>
> So your makefile.inc could test for signing errors and emit something
> that matched the error string syntax and then VS might pick it up. or
> not.
>
> Mark Roddy
>
>
>
> On Mon, Jun 27, 2011 at 5:03 PM, Mark Roddy wrote:
>> Well I use it all the time, but I’m biased. Note that the problem is
>> that the “build process continues” - that isn’t a ddkbuild problem so
>> much as it is a build.exe (WDK tool) problem. Try the same thing from
>> the WDK command shell.
>>
>> Mark Roddy
>>
>>
>>
>> On Mon, Jun 27, 2011 at 5:34 AM, hagen wrote:
>>> Hi all,
>>> I have custom build steps in my makefile.inc: I.e. signing with signtool.
>>> I haven’t found a way yet of propagating any error happening to
>>> ddkbuild and VS2010. In case of an error (i.e. with signing) the build
>>> step just silently fails and the build process continues.
>>> How can I make sure that an error (or a progress indication) is
>>> displayed in the build window of the VS2010 and the build itself is
>>> stopped?
>>> Is ddkbuild really the way to go when building with VS2010?
>>>
>>> Thanks,
>>> Hagen.
>>>
>>> —
>>> 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
>
Not a problem.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of hagen
Sent: Friday, July 01, 2011 4:42 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] makefile.inc ddkbuild+VS2010
Hi Mark & Martin,
thanks for the info!
Hagen.
On Mon, Jun 27, 2011 at 11:55 PM, Martin O’Brien
wrote:
>>So your makefile.inc could test for signing errors and emit something
>>that
> matched the error string syntax and then VS might pick it up. Or not.
>
> I’m not a big VS user, but when I have to use it and BUILD together, I
> tend to do things this. ?I find it works better than other options,
> not any of them work all that well due to what Mark already said - the
> problem is basically BUILD.
>
>
>
> Good luck,
>
> mm
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
> Sent: Monday, June 27, 2011 5:51 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] makefile.inc ddkbuild+VS2010
>
> Oh and the format for text that is an error is approximately
> “error.[CDLU][0-9]” using the findstr regex syntax.
>
> So your makefile.inc could test for signing errors and emit something
> that matched the error string syntax and then VS might pick it up. or
> not.
>
> Mark Roddy
>
>
>
> On Mon, Jun 27, 2011 at 5:03 PM, Mark Roddy wrote:
>> Well I use it all the time, but I’m biased. Note that the problem is
>> that the “build process continues” - that isn’t a ddkbuild problem so
>> much as it is a build.exe (WDK tool) problem. Try the same thing from
>> the WDK command shell.
>>
>> Mark Roddy
>>
>>
>>
>> On Mon, Jun 27, 2011 at 5:34 AM, hagen wrote:
>>> Hi all,
>>> I have custom build steps in my makefile.inc: I.e. signing with
signtool.
>>> I haven’t found a way yet of propagating any error happening to
>>> ddkbuild and VS2010. In case of an error (i.e. with signing) the
>>> build step just silently fails and the build process continues.
>>> How can I make sure that an error (or a progress indication) is
>>> displayed in the build window of the VS2010 and the build itself is
>>> stopped?
>>> Is ddkbuild really the way to go when building with VS2010?
>>>
>>> Thanks,
>>> Hagen.
>>>
>>> —
>>> 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