C
chris-s
Hi folks,
We've been developing PPC apps focusing a single manufacturers device, and
intend to remain doing this for the forseeable future. Up until now we have
been deploying on PPC2002 PXA 250 devices and building our apps using the
2002SDK and ARM build.
Recently the manufacturer have released their devices with PPC2003 and
PXA255 cpu's. Can somebody confirm that we should now use an 'ARMV4' build?
Is this dictacted by the OS version or processor type?
Also, should we install and build using the 2003SDK, despite initial testing
shows that a 2002 build works on 2003 ok?
Providing we do not use any specific 2003 p/invokes, will these builds still
be compatible with PPC2002?
Is there a list of what the 2003SDK changes over 2002SDK?
I said the 2002 build works ok on 2003, well, thats not quite true, we get a
couple of odd things when installing the cab...
1 - the start-menu shortcut is no longer created
2 - we get a new program files shortcut each time it is installed
Cheers,
Chris
We've been developing PPC apps focusing a single manufacturers device, and
intend to remain doing this for the forseeable future. Up until now we have
been deploying on PPC2002 PXA 250 devices and building our apps using the
2002SDK and ARM build.
Recently the manufacturer have released their devices with PPC2003 and
PXA255 cpu's. Can somebody confirm that we should now use an 'ARMV4' build?
Is this dictacted by the OS version or processor type?
Also, should we install and build using the 2003SDK, despite initial testing
shows that a 2002 build works on 2003 ok?
Providing we do not use any specific 2003 p/invokes, will these builds still
be compatible with PPC2002?
Is there a list of what the 2003SDK changes over 2002SDK?
I said the 2002 build works ok on 2003, well, thats not quite true, we get a
couple of odd things when installing the cab...
1 - the start-menu shortcut is no longer created
2 - we get a new program files shortcut each time it is installed
Cheers,
Chris