Re: Problems with 2006 rollup QFE for 5.0

Tech-Archive recommends: Fix windows errors by optimizing your registry

1. Why would you ever modify PUBLIC in place? That's known bad practice for
many reasons, not least of which any QFE can overwrite your changes.

2. If you install the private source with PB, when you "build and sysgen" it
attempts to recreate everything. It first does a "clean" which wipes all
your LIBs. You don't have 100% of the CE source, so when it tries to
recreate them it fails. Now you have a useless install of PB and must
reinstall.


--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--



"Arnie" <jefferyronaldarnett@xxxxxxx> wrote in message
news:%23Cor67eWHHA.1120@xxxxxxxxxxxxxxxxxxxxxxx
We modify code in public and it is the only way to get it built; to use
"build & sysgen".

To clone "public" and then try to keep in sync with QFE's etc. seemed
ridiculous to me.


-arnie

"Michel Verhagen (eMVP)" <mverhagen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eiryNCVWHHA.3500@xxxxxxxxxxxxxxxxxxxxxxx
This was actually a response to Arnie's statement

"It usually turns out to be a stale build environment
and usually doing a "clean" and then a build & sysgen fixes things."

and was made to prevent other users reading his statement to not make
that mistake.

No need to feel offended...

Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com

casner wrote:
I have only once done a build & sysgen. That was a couple of years ago,
on another machine. I nave NEVER done that since, and that is not the
issue here, so this response is not helpful for this issue. There IS an
issue with one of the recent QFE's, possibly only in the 2006 rollup,
but possibly with one of the monthlys shortly before that. True, these
are warnings not errors, but why issue a "fix" that breaks what was
working before? Is there someone at Microsoft who can look at this?

"Michel Verhagen (eMVP)" wrote:

Again: Never EVER do a build & sysgen. Remove that option from the
build menu. Search this NG for "build and sysgen" to find out why.

Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com

Arnie wrote:
This may not help much but we do periodically see build issues after
installing a new Qfe. It usually turns out to be a stale build
environment and usually doing a "clean" and then a build & sysgen
fixes things.

We had one particularly nasty build problem after the Nov QFE and we
actually had to build a new build machine from scratch, but even then
it built fine.

I've installed all the latest QFE's and don't see this build problem.
We are targeting x86 and ARMV4I

-jeff

"casner" <casner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5DC1FD72-A16A-4D89-B579-5A1DA2670983@xxxxxxxxxxxxxxxx
After installing the yearly rollup for December 2006, I get a new
warning in
my builds, which has not happened before:

BUILD: [01:0000000426:WARNN ] fulllibc.lib(__div0.obj) : warning
LNK4099:
PDB 'ccrthelp.pdb' was not found with
'C:\WINCE500\PBWorkspaces\MyProject\WINCE500\LoCE_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fulllibc.lib'
or at 'C:\WINCE500\platform\LoCE\target\ARMV4I\retail\ccrthelp.pdb';
linking
object as if no debug info

BUILD: [01:0000000427:WARNN ] fulllibc.lib(xtoa.obj) : warning
LNK4099: PDB
'ccrtconv.pdb' was not found with
'C:\WINCE500\PBWorkspaces\MyProject\WINCE500\LoCE_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fulllibc.lib'
or at 'C:\WINCE500\platform\LoCE\target\ARMV4I\retail\ccrtconv.pdb';
linking
object as if no debug info

BUILD: [01:0000000428:WARNN ] fulllibc.lib(atox.obj) : warning
LNK4099: PDB
'ccrtconv.pdb' was not found with
'C:\WINCE500\PBWorkspaces\MyProject\WINCE500\LoCE_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fulllibc.lib'
or at 'C:\WINCE500\platform\LoCE\target\ARMV4I\retail\ccrtconv.pdb';
linking
object as if no debug info


Looks like something broken in the QFE?

--


--




.

Relevant Pages

  • Re: Problems with 2006 rollup QFE for 5.0
    ... not least of which any QFE can overwrite your changes. ... If you install the private source with PB, ... "It usually turns out to be a stale build environment ... mverhagen at embeddedfusion dot com ...
    (microsoft.public.windowsce.platbuilder)
  • Re: QFE updates
    ... installing a QFE you have an option to save the install log. ... > Took your advice and downloaded the XPe QFE for Dec 2004. ... The info for each hotfix tells you which files and registry entries ...
    (microsoft.public.windowsxp.embedded)
  • Re: Error while compiling WINCE OS 5.0
    ... For every QFE they include a read me which tells you exaclty what ... For installing the QFE there is a very nice tool which install all QFE's ... Any how now i am reinstalling platform builder. ... Can you tell me what for this you have mentioned ->Perhaps NMD feature pack ...
    (microsoft.public.windowsce.app.development)
  • Re: sqlceme30.dll
    ... Paul G. Tobey wrote: ... seems that something was probably screwed up during the QFE install. ... Could it be due to the .net framework 2.0? ...
    (microsoft.public.sqlserver.ce)
  • Re: QFE Installer tool
    ... I am trying to install QFE 842930 which is needed ... before you install the Installer tool. ... Import just that one SLD. ...
    (microsoft.public.windowsxp.embedded)