Hi all,
I currently have setup our build environment to disable the NO_BINPLACE
flag and setup a proper command-line and BINPLACE_FLAGS so that binplace
can do its magic. It’s all working perfectly and after a full build, we
have our release drivers, the full symbols and the stripped symbols all
in their proper directories.
However, we also have some “support” files which aren’t being “built”,
but still need to be binplaced. Right now, what we do is that we’ve
created a batch file called “release”, which calls the DDK build then
does a manual binplace on the files that remain. I would like to know if
it’s possible to somehow trick the DDK Build to do this for us, by
somehow putting our support files in an existing or new makefile, and
having Build parse it, but not attempt building it (Since they will be
text or image files).
Does anyone know if this is possible?
Best regards,
Alex Ionescu
Try using MISCFILES=myFileToCopy …
-p
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Ionescu
[397670]
Sent: Tuesday, February 28, 2006 1:12 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Binplace & D(W)DK Question
Hi all,
I currently have setup our build environment to disable the NO_BINPLACE
flag and setup a proper command-line and BINPLACE_FLAGS so that binplace
can do its magic. It’s all working perfectly and after a full build, we
have our release drivers, the full symbols and the stripped symbols all
in their proper directories.
However, we also have some “support” files which aren’t being “built”,
but still need to be binplaced. Right now, what we do is that we’ve
created a batch file called “release”, which calls the DDK build then
does a manual binplace on the files that remain. I would like to know if
it’s possible to somehow trick the DDK Build to do this for us, by
somehow putting our support files in an existing or new makefile, and
having Build parse it, but not attempt building it (Since they will be
text or image files).
Does anyone know if this is possible?
Best regards,
Alex Ionescu
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Thanks Peter, that worked great.
Best regards,
Alex Ionescu
Peter Wieland wrote:
Try using MISCFILES=myFileToCopy …
-p
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Ionescu
[397670]
Sent: Tuesday, February 28, 2006 1:12 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Binplace & D(W)DK Question
Hi all,
I currently have setup our build environment to disable the NO_BINPLACE
flag and setup a proper command-line and BINPLACE_FLAGS so that binplace
can do its magic. It’s all working perfectly and after a full build, we
have our release drivers, the full symbols and the stripped symbols all
in their proper directories.
However, we also have some “support” files which aren’t being “built”,
but still need to be binplaced. Right now, what we do is that we’ve
created a batch file called “release”, which calls the DDK build then
does a manual binplace on the files that remain. I would like to know if
it’s possible to somehow trick the DDK Build to do this for us, by
somehow putting our support files in an existing or new makefile, and
having Build parse it, but not attempt building it (Since they will be
text or image files).
Does anyone know if this is possible?
Best regards,
Alex Ionescu
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer