Thanks. Although perhaps not the cleanest way to do it, I switched to just having d.lst deliver it directly from the source dir.
-- Michael Leibowitz Software Engineer, Channel Platform Solutions Group Intel Corporation michael.leibowitz at intel.com +1 503 264 7621 >-----Original Message----- >From: Hans-Joachim Lankenau [mailto:[EMAIL PROTECTED] >Sent: Monday, July 17, 2006 8:29 AM >To: [email protected] >Subject: Re: [dev] "make" a python script in makefile.mk? > >hi! > >UNIXTEXT was introduced to make sure the resulting file gets cleaned >from dos lineends. >there is currently nothing similar available for windows :( > >Leibowitz, Michael wrote: >> I'm having some trouble with "making" scripts in my makefile.mk. In >> UNIX, I use "UNIXTEXT = $(MISC)/dbbe_enable.sh" That seems to work. >> However, on Windows, I don't know of any similar variable. I tried >> putting in my own target: >> >> # --- Targets ---------------------------------- >> >> .INCLUDE : target.mk > ># insert your target in the dependency chain >ALLTAR : $(MISC)$/dbbe_enable.py >> >> $(MISC)$/dbbe_enable.py: dbbe_enable.py >> +cp $? $@ >> >> But, this doesn't seem to have any effect. Any hints?? >> > >better use $(COPY) or $(GNUCOPY) instead of "cp" > >tschau... > >ause > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
