Re: Error building project for CEPC X86 target.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

When you build your platform, the headers and libraries are there. If the
only question is "how do I access functions declared in libraries that
aren't installed with a SDK", you can just add the actual locations of the
headers and libraries to your eVC project, or you can manually add the
header and library files to the SDK that you produce from platform builder
and there you are.

Just as with SDKs, there is no "the DDK" for Windows CE. Every device
would have a different one. It's up to the device vendor to put the pieces
that they think you'll need into their SDK.

Paul T.

"Mike M." <nospam@xxxxxxxxxxxxx> wrote in message
news:%23WUIsr1PFHA.3668@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks Yannick. That's what I originally built my program in built I
> needed
> to have the READ_PORT_UCHAR and WRITE_PORT_UCHAR macros and I couldn't
> find
> the method to download and install the ceddk. I need to read/write single
> chars to a port address (0x443). Can you suggest how I can get the ceddk
> into my eVC 4.0 environment?
>
> Thanks.
>
> "Yannick Chamming's [eMVP]" <ychammings_nospam@xxxxxxxxxx> wrote in
> message
> news:Owx3LZyPFHA.648@xxxxxxxxxxxxxxxxxxxxxxx
>> Platform Builder does not include a wizard that allows MFC based
> application
>> creation.
>>
>> You should use eVC++ to create these kind of applications, and to have
>> settings that allow you selecting MFC as shared or statically linked.
>>
>>
>> --
>> ----------------------------------------------------------------
>> Yannick Chamming's (eMVP)
>> ADENEO (ADESET)
>> Windows Embedded Manager
>> ychammings AT adeset DOT com>
>> http://www.adeset.com
>> Tél : +33 (0)4.72.18.57.77
>> Fax : +33 (0)4.72.18.57.78
>> ----------------------------------------------------------------
>>
>> "Mike M." <nospam@xxxxxxxxxxxxx> wrote in message
>> news:uSXROltPFHA.1564@xxxxxxxxxxxxxxxxxxxxxxx
>> > I am using Platform builder for Wince 5.0. I am trying to build an
>> > application (WCE application) for a CEPC x86 target platform. I needed
> to
>> > add MFC support to use some of the code in the project. I added the
>> > MFC
>> > catlog to my platform and rebuilt the OS. Then when I build my project
> I
>> > get an error, "Can't build MFC OLE projects using static MFC
>> > libraries."
>> I
>> > cannot find a setting (like in VC 6.0) where I can set to use MFC as a
>> > shared dll. Is that what I need to do and where is that setting?
>> >
>> > TIA
>> >
>> >
>>
>>
>
>


.

Relevant Pages

  • Re: Error building project for CEPC X86 target.
    ... > When you build your platform, the headers and libraries are there. ... > aren't installed with a SDK", you can just add the actual locations of the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Any Clojure users here?
    ... Each platform has distinct libraries for things like ... But a CL implementation can (and does, in fact, for certain libraries) ... I later want to port it to Windows and give it a native Windows GUI, ...
    (comp.lang.lisp)
  • Re: Any Clojure users here?
    ... Each platform has distinct libraries for things like ... want to port it to Windows and give it a native Windows GUI, ... In neither case do you have painless cross-platform portability. ...
    (comp.lang.lisp)
  • Re: Any Clojure users here?
    ... Again, portability is not all-or-nothing but is a varying degree - so if you use say 1 Java library call every 100 Lisp library calls, portability to another Lisp is probably not going to be a concern. ... Each platform has distinct libraries for things like ... But a CL implementation can (and does, in fact, for certain libraries) hide such details behind a OS-independent API, just like the JVM does... ... want to port it to Windows and give it a native Windows GUI, ...
    (comp.lang.lisp)
  • Re: About speed
    ... But I mean - new platform must simplify ... available to .NET applications (and keep in mind coming libraries, ... writing a critical piece of architecture or a library that will be under ... .NET show BIG difference in architecture from Win32 so my ...
    (borland.public.delphi.non-technical)