[wdmaudiodev] Re: BUILD.EXE from WDK 5365 now build using 2 makefiles.

  • From: Kenny Ong <fluffy_ko@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Thu, 25 May 2006 19:54:56 -0700 (PDT)

Thanks Tim, you are right, it certainly screwed up my case where my "makefile" 
is meant for Linux used...
   
  I guess the only confusion which Microsoft will have to address is when /f 
parameter is being passed twice to nmake, which is the precedence makefile?
   
  And also how can i suppress the default makefile?
   
   
  Thanks!
  Kenny.

timr@xxxxxxxxx wrote:
  On Wed, May 24, 2006 at 02:30:30AM -0700, Kenny Ong wrote:
> > That's not true. It would use "makefile" automatically, if present, as
> it was supposed be in every leaf directory, and it would happily do 
> nothing if there was no makefile present:
> 
> I believe you are running the BUILD.EXE in an empty folder (i.e. with
> no sources file), and that explaint why the BUILD.EXE doesn't complaint
> about missing makefile... Try running in a valid source folder (fresh)
> with no makefile present, and you will see what i mean.

You are correct.

> > The WDK is apparently encoding this knowledge into the "build" command
> > itself, instead of relying on the user to copy that file everywhere.
>
> Agreed, but the problem with the WDK's BUILD.EXE is that it will include 
> both the makefiles if i choose to use a custom makefile (i.e. "-nmake /f 
> makefile.nt").
> Ultimately what i'm expecting is that the BUILD.EXE should not
> include the default makefile (either the makefile that reside in the
> source folder, or the makefile from the WDK's Bin folder) when i specify
> the "/f" parameter.

Well, as I said before, I think you were "slipping by" before with 
behavior that was never intended to be supported by "build". Build
expects to be used with the stock makefile.def. Prior to the WDK, that
was accomplished by an !INCLUDE in the local makefile. Now it's being
accomplished by a direct parameter to nmake.

It's not terribly surprising that it doesn't parse your "-nmake"
parameter; it's just passing that through to nmake along with whatever
parameters it decides to add.

Without addressing the issue of "good vs bad", I don't think you'll be
able to convince anyone that the new behavior is a bug. I think you got 
burned by relying on undocumented behavior. The new behavior is better 
for 99.99% of the cases (because we no longer need the silly one-line 
makefile), but it does screw up your case.
-- 
- Tim Roberts, timr@xxxxxxxxx
Providenza & Boeklheide, Inc.
******************

WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx

URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/



                
---------------------------------
Be a chatter box. Enjoy free PC-to-PC calls  with Yahoo! Messenger with Voice.

Other related posts: