How to build platform quickly when I modified file?

Hi all,
I modified some file under HAL directory,then use build -c,but it's no
effect when I use "make image" or "build platform",so I only can use
"rebuild platform" ,it's too slowly.Anybody can tell how to build it
quickly? thanks in advance.

regards

Todd
Tue Dec 14 08:25:49 CST 2004

If you can "build" from the command line then go ahead and run "makeimg"
from there also. The "make image" in the user interface probably didn't
work if you hadn't run "buildrel". So from the command line:

> build
> buildrel
> makeimg

or you can eliminate the "buildrel" step by having WINCERL=1 defined in your
environment which will cause the files generated by "build" to be copied
(during the build) to the flatreleasedir for you. Thus all you need is:

> set WINCEREL=1
> build
> makeimg

Todd Krochta
Applied Data Systems


"Chanter" <blueenc@hotmail.com> wrote in message
news:%23DUcAIe4EHA.1400@TK2MSFTNGP11.phx.gbl...
> Hi all,
> I modified some file under HAL directory,then use build -c,but it's no
> effect when I use "make image" or "build platform",so I only can use
> "rebuild platform" ,it's too slowly.Anybody can tell how to build it
> quickly? thanks in advance.
>
> regards
>
>

Todd
Tue Dec 14 12:25:28 CST 2004

In addition, if you really want recompile and test quickly the same .lib
over and over and you are using KITL, you can do the following. Build a
KITL enabled image with your .lib "excluded" from the image and keep that
image on the device to boot from. That way, when the image boots up and
doesn't find your .lib on the device, it will look over KITL to get it from
the host build computer (your PC). So then all you have to do is make s/w
changes to your source file, rebuild the .lib(with WINCEREL=1) and reboot
the target device.

Todd Krochta
Applied Data Systems

"Todd Krochta" <tkrochta_nospam@applieddata_nospam.net> wrote in message
news:ug%23YQje4EHA.824@TK2MSFTNGP11.phx.gbl...
> If you can "build" from the command line then go ahead and run "makeimg"
> from there also. The "make image" in the user interface probably didn't
> work if you hadn't run "buildrel". So from the command line:
>
>> build
>> buildrel
>> makeimg
>
> or you can eliminate the "buildrel" step by having WINCERL=1 defined in
> your environment which will cause the files generated by "build" to be
> copied (during the build) to the flatreleasedir for you. Thus all you
> need is:
>
>> set WINCEREL=1
>> build
>> makeimg
>
> Todd Krochta
> Applied Data Systems
>
>
> "Chanter" <blueenc@hotmail.com> wrote in message
> news:%23DUcAIe4EHA.1400@TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I modified some file under HAL directory,then use build -c,but it's no
>> effect when I use "make image" or "build platform",so I only can use
>> "rebuild platform" ,it's too slowly.Anybody can tell how to build it
>> quickly? thanks in advance.
>>
>> regards
>>
>>
>
>

Todd
Tue Dec 14 12:42:07 CST 2004

I did not mean to imply that you could do the excluded library techniqure
with your hal.lib. But, this is very useful when working on a driver.

Todd Krochta
Applied Data Systems


"Todd Krochta" <tkrochta_nospam@applieddata_nospam.net> wrote in message
news:%23F7sKpg4EHA.924@TK2MSFTNGP14.phx.gbl...
> In addition, if you really want recompile and test quickly the same .lib
> over and over and you are using KITL, you can do the following. Build a
> KITL enabled image with your .lib "excluded" from the image and keep that
> image on the device to boot from. That way, when the image boots up and
> doesn't find your .lib on the device, it will look over KITL to get it
> from the host build computer (your PC). So then all you have to do is
> make s/w changes to your source file, rebuild the .lib(with WINCEREL=1)
> and reboot the target device.
>
> Todd Krochta
> Applied Data Systems
>
> "Todd Krochta" <tkrochta_nospam@applieddata_nospam.net> wrote in message
> news:ug%23YQje4EHA.824@TK2MSFTNGP11.phx.gbl...
>> If you can "build" from the command line then go ahead and run "makeimg"
>> from there also. The "make image" in the user interface probably didn't
>> work if you hadn't run "buildrel". So from the command line:
>>
>>> build
>>> buildrel
>>> makeimg
>>
>> or you can eliminate the "buildrel" step by having WINCERL=1 defined in
>> your environment which will cause the files generated by "build" to be
>> copied (during the build) to the flatreleasedir for you. Thus all you
>> need is:
>>
>>> set WINCEREL=1
>>> build
>>> makeimg
>>
>> Todd Krochta
>> Applied Data Systems
>>
>>
>> "Chanter" <blueenc@hotmail.com> wrote in message
>> news:%23DUcAIe4EHA.1400@TK2MSFTNGP11.phx.gbl...
>>> Hi all,
>>> I modified some file under HAL directory,then use build -c,but it's no
>>> effect when I use "make image" or "build platform",so I only can use
>>> "rebuild platform" ,it's too slowly.Anybody can tell how to build it
>>> quickly? thanks in advance.
>>>
>>> regards
>>>
>>>
>>
>>
>
>

Steve
Tue Dec 14 12:55:17 CST 2004

What Todd said applies to EXEs and DLLs but not .lib files as they are not
executable modules. You must at least link the library to get the DLL or EXE
when you change it's contents.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

chanter
Tue Dec 14 20:31:49 CST 2004

Thank you for your help,I have some problem by using "set WINCEREL=1 build
makeimg".
I modified the print message of OEMGetRealTime function and I set WINCEREL=1
,build and makeimg under hal dir,then i download to the target and found the
print message not change.i have checked the variable of WINCEREL and found
it is defined as 1,and it's successful compling the file which involved
OEMGetRealTime.

"Todd Krochta" <tkrochta_nospam@applieddata_nospam.net> wrote in message
news:ug#YQje4EHA.824@TK2MSFTNGP11.phx.gbl...
> If you can "build" from the command line then go ahead and run "makeimg"
> from there also. The "make image" in the user interface probably didn't
> work if you hadn't run "buildrel". So from the command line:
>
> > build
> > buildrel
> > makeimg
>
> or you can eliminate the "buildrel" step by having WINCERL=1 defined in
your
> environment which will cause the files generated by "build" to be copied
> (during the build) to the flatreleasedir for you. Thus all you need is:
>
> > set WINCEREL=1
> > build
> > makeimg
>
> Todd Krochta
> Applied Data Systems
>
>
> "Chanter" <blueenc@hotmail.com> wrote in message
> news:%23DUcAIe4EHA.1400@TK2MSFTNGP11.phx.gbl...
> > Hi all,
> > I modified some file under HAL directory,then use build -c,but it's no
> > effect when I use "make image" or "build platform",so I only can use
> > "rebuild platform" ,it's too slowly.Anybody can tell how to build it
> > quickly? thanks in advance.
> >
> > regards
> >
> >
>
>

Dean
Wed Dec 15 17:02:40 CST 2004

The hal directory just builds a lib. The lib must then linked into the
kernel, which ends up being nk.exe in the image. So, you need to build the
kernel after building the hal (typically under the BUILDEXE subdirectories).
So, you need to do your building from the kernel directory, not the HAL
directory.

--
Dean Ramsier - eMVP


"chanter" <blueenc@hotmail.com> wrote in message
news:esWVC5k4EHA.604@TK2MSFTNGP10.phx.gbl...
> Thank you for your help,I have some problem by using "set WINCEREL=1 build
> makeimg".
> I modified the print message of OEMGetRealTime function and I set
WINCEREL=1
> ,build and makeimg under hal dir,then i download to the target and found
the
> print message not change.i have checked the variable of WINCEREL and found
> it is defined as 1,and it's successful compling the file which involved
> OEMGetRealTime.
>
> "Todd Krochta" <tkrochta_nospam@applieddata_nospam.net> wrote in message
> news:ug#YQje4EHA.824@TK2MSFTNGP11.phx.gbl...
> > If you can "build" from the command line then go ahead and run "makeimg"
> > from there also. The "make image" in the user interface probably didn't
> > work if you hadn't run "buildrel". So from the command line:
> >
> > > build
> > > buildrel
> > > makeimg
> >
> > or you can eliminate the "buildrel" step by having WINCERL=1 defined in
> your
> > environment which will cause the files generated by "build" to be copied
> > (during the build) to the flatreleasedir for you. Thus all you need is:
> >
> > > set WINCEREL=1
> > > build
> > > makeimg
> >
> > Todd Krochta
> > Applied Data Systems
> >
> >
> > "Chanter" <blueenc@hotmail.com> wrote in message
> > news:%23DUcAIe4EHA.1400@TK2MSFTNGP11.phx.gbl...
> > > Hi all,
> > > I modified some file under HAL directory,then use build -c,but it's no
> > > effect when I use "make image" or "build platform",so I only can use
> > > "rebuild platform" ,it's too slowly.Anybody can tell how to build it
> > > quickly? thanks in advance.
> > >
> > > regards
> > >
> > >
> >
> >
>
>
>
>