(crossposting this to microsoft.public.windows.embedded.vc since this is
really more of an eVC question than PB.)
I asked the eVC team about this and here is their reply:
"This can occur when the new platform doesn't support the entire set of CPU
configurations that the project targets. For example, a vanilla project that
only targets MIPS and SHx will not display "Pocket PC 2003" as a valid
platform to build against (because PPC only supports ARM and X86). The
resolution may be to rebuild his new SDK with additional CPU support."
"As for porting project settings: We have no option/tool to do this AFAIK. A
touch of notepad.exe on the .vcp file is a possible remedy."
This posting is provided "AS IS" with no warranties, and confers no rights.
> uses ARMV4, my new one associated with the new SDK uses ARMV4I.
> > use build | configurations | add
> > >-----Original Message-----
> > >If any of you answered this post previously, my
> > apologies, but for some
> > >reason, the message disappeared from the server. So, I'm
> > reposting...
> > >Hi,
> > >I'm working with a board for which I've created an SDK in
> > PB 4.2. What I'm
> > >finding is that I have to recreate my eVC project to have
> > the new SDK appear
> > >as an option under eVC (4.0 sp2). Is there an easy way
> > to have the new SDK
> > >appear as an option within eVC?
> > >If not, is there an easy way to port the eVC project
> > settings from one
> > >project to another?
> > >Thanks,
> > >Bruce
> > >.