Windows CE

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I'm looking at the feasability of porting our product to create a windows CE version and needed to look into porting requirements for the toolkit. Has anyone tried to do this? Of course I assume that a lot of the toolkit just doesn't even apply at that point, however, It seems to me like most of the controls and some other areas of the program SHOULD be portable.
Is there any chance of prevailing on the powers that be to put in some #ifdefs and create a CE buildable configuration? (of course I'm fairly sure that would require static linkage.)

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
JohnCrenshaw Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 September 2006 Status: Offline Points: 65	Post Options Post Reply Quote JohnCrenshaw Report Post Thanks(0) Quote Reply Topic: Windows CE Posted: 10 January 2007 at 10:45am
	I'm looking at the feasability of porting our product to create a windows CE version and needed to look into porting requirements for the toolkit. Has anyone tried to do this? Of course I assume that a lot of the toolkit just doesn't even apply at that point, however, It seems to me like most of the controls and some other areas of the program SHOULD be portable. Is there any chance of prevailing on the powers that be to put in some #ifdefs and create a CE buildable configuration? (of course I'm fairly sure that would require static linkage.)