Re: Using NTTARGETFILE1 macro in driver build process

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

There is no need to express Inter-Pass dependencies.
Same pass dependencies are expressed in the usual makefile form:

<target> : <predecessor target>
<build command>

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"MK" <MK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:920E3DF0-18DC-40DF-92E1-9C8E76AC279D@xxxxxxxxxxxxxxxx
Thanks for the reply.
I have few queries...
How to express this dependency?
Do we have any macro to express the dependency?

Thanks
--
MK


"Ivan Brugiolo [MSFT]" wrote:

Can you express a dependency on the target that you have in the
makefile.inc
?
This way it will be build only after the dependency has been built as
well.

--

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"MK" <MK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BFF926D4-0063-4862-84E0-8F9DDF6CCDED@xxxxxxxxxxxxxxxx
Hi,
I am using NTTARGETFILE1 macro in the sources file, to create a
specific
file during driver build (through build utility). It creates the file,
as
expected. But it creates the files twice. DDK says "NTTARGETFILE1 is
invoked
on pass one or later passes". I think the command specified in the
makefile.inc to create the file is invoked twice ( pass 1 and at the
time
of
linking). Because of this unwanted second time execution of the
command,
compilation takes more time. Is there anything to avoid this unwanted
stuff.
Something which gets executed only once, either at the time of
compilation
or
at the time of linking.
I have used the macro like...
In sources file...
.
.
NTTARGETFILE1=CreateMyFile

In makefile.inc ...
.
.
CreateMyFile:
CommandToCreateTheFile


Thanks,
--
MK





.

Relevant Pages

  • Re: Using NTTARGETFILE1 macro in driver build process
    ... Do we have any macro to express the dependency? ... I am using NTTARGETFILE1 macro in the sources file, ... Because of this unwanted second time execution of the command, ... Something which gets executed only once, either at the time of compilation ...
    (microsoft.public.development.device.drivers)
  • GNU make : Generating Prerequisites Automatically
    ... I've read the manual's documentation on Generating Prerequisites Automatically. ... The documentation suggests using the following rule to generate a dependency ... "The -e flag to the shell causes it to exit immediately if any command fails" ... As far as I understand, we want to generate a file "foo.d" which contains two targets foo.o and foo.d before the colon, and gcc produces only foo.o ...
    (comp.unix.programmer)
  • Re: Using NTTARGETFILE1 macro in driver build process
    ... This way it will be build only after the dependency has been built as well. ... Because of this unwanted second time execution of the command, ... Something which gets executed only once, either at the time of compilation ...
    (microsoft.public.development.device.drivers)
  • Re: GNOME wont boot
    ... uninstall some files from glade interface. ... dependency files, I knew that I couldn't remove them and so I ... I'm not sure how that command would work. ... you could install libglade2 using this command (as ...
    (Fedora)
  • requirements (glib >= 1.2.4 gtk+ >= 1.2.4) not met
    ... I'm trying to install the latest version of kino from source ... which of course is lots of fun and giving me dependency troubles... ... sh: glib-config: command not found ... Reading package lists... ...
    (Ubuntu)