Prev: Manually editing INF file for flakey soundcard
Next: USB networking device slow removal
From: Pavel A. on 27 Oct 2009 23:07
Yes, there are some breaking changes in WDK 7000.
Behaviour of some variables in sources file, like TARGETPATH,
was changed.
Try to clean up your sources file from anything not absolutely nesessary
and see if it helps.

Regards,
--pa

"RamenWarrior" <RamenWarrior(a)nospam.nospam> wrote in message
news:8C5CA070-F3EB-4719-A60F-356972A67F31(a)microsoft.com...
> I appreciate the suggestions. Unfortunately my "sources" file is quite
> large
> and I am not sure it is appropriate to upload it here.
>
> Since everything works fine in the older WDK I assume there must be
> something subtle that needs to be changed.
>
> I think this commend in makefile.new may point us in the right direction:
> This is the standard makefile for the components of the NT project.
> It includes the following files:
>
> .\sources. - developer supplies this file. It defines the
> required TARGETNAME, TARGETTYPE and
> SOURCES as well as optional macros that control
> the behavior of the compiler and linker:
>
> $(OBJ_PATH)\$O\_objects.mac - built by BUILD.EXE from .\sources.
>
>
> It appears that $(OBJ_PATH) is not initialized correctly for my build.
> This
> environment variable seems to be only referenced in makefile.new. I don't
> see
> it anywhere in my sources file.
>
> Does my hypothesis seem to be valid?
>
> "David Craig" wrote:
>
>> Your build environment is wrong. List the complete directory structure
>> and
>> show the presence of dirs, sources, makefile, and makefile.inc in each of
>> those directories from the location where you execute 'build -ceZ'. Also
>> show where any new directories are created during your build attempts.
>> The
>> subdirectories are NOT root relative, but relative to the place where the
>> appropriate sources file is found. You might want to consider using
>> ddkbuild.bat from Hollis technologies (Mark Roddy) as it works very well
>> from almost any decent editor. Follow the tutorial to configure Visual
>> Studio, but I use SlickEdit and have a local batch file as follows:
>> date /t
>> time /t
>> python BuildNbr.py Ver.h
>> if not errorlevel 1 ddkbuild.bat %*
>>
>> The parameters are as specified on Mark's website and passed in for the
>> various builds (32 & 64 & checked & free). On some builds I also may
>> need
>> IA64, but not this project. There was a very good article/document from
>> Microsoft about how build works and the restrictions on directory
>> placement.
>>
>> Cryptic question:
>> Shou or shio? Hokkaido or ...?
>> End cryptic question
>>
>>
>> "RamenWarrior" <RamenWarrior(a)nospam.nospam> wrote in message
>> news:159BA591-399D-4376-A9FA-EFA990D59AA5(a)microsoft.com...
>> >I have been using the 6001.XXXX WDK for several years and my drivers
>> >build
>> > just fine.
>> > When I upgraded to 7600, the build broke.
>> > The error messages seem to indicate that the wrong source directory is
>> > being
>> > used.
>> > For some reason, the build process is all relative to the root
>> > directory
>> > instead of the base directory for my source code.
>> >
>> > BUILD: Saving c:\winddk\7600.16385.0\build.dat...
>> > Total of 40 source files (95,725 lines) to compile in 6 directories
>> >
>> > BUILD: Compiling d:\svn\spctrunk\tisa\drivers\windows\common directory
>> > 1>errors in directory d:\svn\spctrunk\tisa\drivers\windows\common
>> > 1>c:\winddk\7600.16385.0\bin\makefile.new(453) : error U1052: file
>> > '\objchk_wlh_
>> > x86\i386\_objects.mac' not found
>> > 1>nmake.exe /nologo BUILDMSG=Stop. -i BUILD_PASS=PASS1 NOLINK=1
>> > NOPASS0=1
>> > MAKEDI
>> > R_RELATIVE_TO_BASEDIR= failed - rc = 2
>> >
>> > I tried comparing SETENV.BAT and MAKEFILE.NEW between 6001 and 7600 but
>> > I
>> > can't see anything obvious that is wrong.
>> >
>> > thanks,
>> >
>> > RW
>>
>>
>> .
>>
First  |  Prev  | 
Pages: 1 2
Prev: Manually editing INF file for flakey soundcard
Next: USB networking device slow removal