 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Pocket PC Forum / Developers / WinCE Programming / July 2008ATL8 Issues PC based proj --> CE6.0 proj Migration/Port....
I have a perfectly executing project on PC that uses ATL & MFC. I am now in the process of migrating it to CE 6.0. So far, I have successfully created a subproject (not created from scratch, but imported from existing source code using SOUCRES/DIR method) in my OS Design, and trying to build. The very first error is as follows: C:\WINCE600\OTHERS\ATL8\INCLUDE\altcecrt.h(9) : fatal error C1189: #error : This header file is only used internally by ATL under the WinCE OS tree I looked online and few posts lead me to MSDN website that talks about migration from evC to PB/VS2005 project, but they dont seem to be useful to me, becuase thats for folks who take the wizard approach. ex: http://msdn2.microsoft.com/en-us/library/ms228806(VS.80).aspx Question is, how do you resolve this compile time error? Thanks. Do you know if your vendor's SDK supports ATL/MFC and if they do if they support it fully or subsets of it? OR are you using Standard SDK? -compe2001 > I have a perfectly executing project on PC that uses ATL & MFC. I am now in > the process of migrating it to CE 6.0. So far, I have successfully created a [quoted text clipped - 13 lines] > > Thanks. Thanks for reading and reply to my post. I am in complete control of SDK. The project was initially developed for PC enviorn. Now, I am taking charge of migrating to CE 6.0. And I created a SDK for my CE device, which includes support for ATL and MFC. To what extent it supports ATL/MFC - that only Microsoft knows, becuase its the PB that creates the SDK. I hope it answers your question as to who generates the SDK and what its support is. Thanks. The SDK, in CE6, no longer actually includes MFC (not sure about ATL, but I think it's the same). When you build your smart device application in Visual Studio targeting that SDK, you can use the MFC version that shipped with Visual Studio (and that's what the SDK, Microsoft, etc. is expecting). You don't want to create a MFC-based subproject of your OS project. My experience is that MFC, as with managed code (C#/VB.NET), doesn't build well in the Platform Builder build system. I suppose that there's nothing to prevent it from eventually working, but a) you have an SDK, b) you have VS2005. I see no reason not to use a separate workspace for building your MFC or ATL components. Paul T. > Thanks for reading and reply to my post. > I am in complete control of SDK. The project was initially developed for [quoted text clipped - 10 lines] > > Thanks. Hi Paul, C:\WINCE600\OTHERS\ATL8\INCLUDE\altcecrt.h(9) : fatal error C1189: #error : This header file is only used internally by ATL under the WinCE OS tree This is the error I am seeing when I build a subproject in PB for CE 6.0 The subproject (by itself) works fine in VS2005 for PC version. Its only when I move it to CE - and start building I get this. For some reason, I cannot seem to also create a New Project | Smart Dev in my PB. The dialog gets stuck there, and does nothing. So, I have to create a subprpject under OS design, and build against the SDK (that I create). Also, I made sure, the SDK included the ATL (by manually adding ATL directories, found under \OTHERS\ATL8) to SDK creation & building. But even then, I get these errors. Any resolution? Thanks. I have seen some posts on internet (which are too complex and seems to have no clear resolution) and Mike Halls blog [adding XML/Web services for CE stuff] that says use Win32 Smart Device ATL template - but as I said, project creation for Smart Devices is failing in my setup. Yes - I have tried re-installing VS. May be I should try one more try - doing a clean install- for I did the modify/repair current installation option last time. Thanks. Who are you talking to? Check http://guruce.com/blogpost/howtoaskquestionsonnewsgroups. Paul T. > Hi Paul, > [quoted text clipped - 25 lines] > > Thanks. Hello, Sorry about whatever I did wrong.... By posting it twice? I posted it and then saw your answers to another thread, and replied to your posts. Apologies again, Thanks I don't own the group and you don't want me to address any problems with ATL, let me tell you! Don't treat the group like a chat; it's not. By referencing a particular person, you reduce the liklihood of a response by about 50%, and it makes it seem like you're referencing some other problem but posted the message to the wrong thread, all things that make a useful interaction unlikely. Paul T. > Hello, > [quoted text clipped - 5 lines] > > Thanks I see. OK. Understood. Thanks. Paul, Its me again. Now that I am thinking of it...am I building against the SDK I newly created to include ATL ? I guess not... 1 . How do I force my subproject to build against the SDK? All Im doing now, is to right click on the my subprojectAPP that I added and say Build. and thats when I see these rrrors... My SDK structure looks like this: (if you can spot something wrong) C:\WINCE600\OSDesigns\OSDesign_Jul_08_v1\OSDesign_Jul_08_v1\SDKs\SDK2\obj\SDK2 under SDK2\ I have: \ADDATL (this is what I manually added to fetch in the ATL files from C:\WINCE600\OTHERS\ATL8. \INCLUDE \LIB Now, under ADDATL, I have the same structure as \OTHERS\ATL8, i.e: \INCLUDE \LIB and \SRC This \INCLUDE contains ATLCERT.H (I'm sure you know that!!!) Thanks, > Thanks for reading and reply to my post. > I am in complete control of SDK. The project was initially developed for PC > enviorn. Now, I am taking charge of migrating to CE 6.0. And I created a SDK > for my CE device, which includes support for ATL and MFC. To what extent it > supports ATL/MFC - that only Microsoft knows, becuase its the PB that creates > the SDK. There is no MFC in Windows CE 6.0 PB. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.