Is Postlink.bat functional in CE 6.0?

I'm trying to convert a BSP from 5.0 to 6.0. This looks to be a manual task
as the command line based, CEC import tool does not produce anything but
errors.

I have added one precompiled driver from my 5.0 BSP to my 6.0 tree as a test
case. There is no source for this driver, just the .dll file and associated
.reg and .bib files. I modified the Catalog file (.pbcxml) to include the
driver. It is visible in the Catalog and selected to be part of the build.


V5.0 required the precompiled .dll and the associated .reg file to be copied
to the _FLATRELEASEDIR using POSTLINK.BAT. This methodology does not appear
to work in 6.0 but there is no documentation that I can find regarding a
change in this regard. Am I missing something? If the methodology has
changed (again), where is it documented?

Dean
Wed Apr 11 11:11:41 CDT 2007

Yes, converting a BSP is a manual task. The only thing cecimport.exe does
is convert a cec file to the new pbcxml file format. Everything else is up
to you to do by hand. I can't say for sure about your specific postlink.bat
question because I've never used it. But it seems to me that it would still
be there...

--
Dean Ramsier - eMVP
BSQUARE Corporation


"KW" <KW@discussions.microsoft.com> wrote in message
news:42043758-7D4E-426A-961A-796150C32D8B@microsoft.com...
> I'm trying to convert a BSP from 5.0 to 6.0. This looks to be a manual
> task
> as the command line based, CEC import tool does not produce anything but
> errors.
>
> I have added one precompiled driver from my 5.0 BSP to my 6.0 tree as a
> test
> case. There is no source for this driver, just the .dll file and
> associated
> .reg and .bib files. I modified the Catalog file (.pbcxml) to include the
> driver. It is visible in the Catalog and selected to be part of the
> build.
>
>
> V5.0 required the precompiled .dll and the associated .reg file to be
> copied
> to the _FLATRELEASEDIR using POSTLINK.BAT. This methodology does not
> appear
> to work in 6.0 but there is no documentation that I can find regarding a
> change in this regard. Am I missing something? If the methodology has
> changed (again), where is it documented?
>
>

Valter
Thu Apr 12 07:01:45 CDT 2007

=?Utf-8?B?S1c=?= <KW@discussions.microsoft.com> wrote in
news:42043758-7D4E-426A-961A-796150C32D8B@microsoft.com:

[...]
> V5.0 required the precompiled .dll and the associated .reg file to
> be copied to the _FLATRELEASEDIR using POSTLINK.BAT. This
> methodology does not appear to work in 6.0 but there is no
> documentation that I can find regarding a change in this regard.
> Am I missing something? If the methodology has changed (again),
> where is it documented?

There is a difference between CE 5 and 6 and in CE 6 the %
FLATRELEASEDIR% seems to be cleaned after postlink is executed and this
will make your copy operation useless.
You should keep the copy to %FLATRELEASEDIR% for localized builds (when
you rebuild only your project) and add a copy to "%_PROJECTROOT%
\cesysgen\oak\target\%_TGTCPU%\%WINCEDEBUG%? to copy the file to a dir
tat will be merged with %FLATRELEASEDIR% before the makeimg step during
a full build.

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)

KW
Wed Apr 18 12:06:02 CDT 2007

Thank you! That did the trick. I was able to figure out that postlink.bat
was (or appeared to be) executing but the files that were copied simply were
not anywhere to be found in the %_FLATRELEASEDIR% after the build completed.
Changing the destination of the copied files per your suggestion solved the
problem.

Now I can move on the next undocumented "feature"...

Thanks again.

"Valter Minute" wrote:

> =?Utf-8?B?S1c=?= <KW@discussions.microsoft.com> wrote in
> news:42043758-7D4E-426A-961A-796150C32D8B@microsoft.com:
>
> [...]
> > V5.0 required the precompiled .dll and the associated .reg file to
> > be copied to the _FLATRELEASEDIR using POSTLINK.BAT. This
> > methodology does not appear to work in 6.0 but there is no
> > documentation that I can find regarding a change in this regard.
> > Am I missing something? If the methodology has changed (again),
> > where is it documented?
>
> There is a difference between CE 5 and 6 and in CE 6 the %
> FLATRELEASEDIR% seems to be cleaned after postlink is executed and this
> will make your copy operation useless.
> You should keep the copy to %FLATRELEASEDIR% for localized builds (when
> you rebuild only your project) and add a copy to "%_PROJECTROOT%
> \cesysgen\oak\target\%_TGTCPU%\%WINCEDEBUG%â?? to copy the file to a dir
> tat will be merged with %FLATRELEASEDIR% before the makeimg step during
> a full build.
>
> --
> Valter Minute
> (the reply address of this message is invalid)
> (l'indirizzo di reply di questo messaggio non è valido)
>