Re: where is wininet.lib coming from?
- From: "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
- Date: Mon, 11 Jul 2005 13:48:28 -0700
You might just arrange, in your CEC file, to copy individual headers to
$(_PROJECTROOT)\cesysgen\sdk\inc, and individual libraries to
$(_PROJECTROOT)\cesysgen\sdk\lib\$(_TGTCPU)\$(WINCEDEBUG). You shouldn't
have to modify your SDK configuration, if you do that (at least in CE.NET
4.2).
Paul T.
"J Garcia" <jggarcia@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23rTqBUlhFHA.1464@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for your help in this and other posts.
>
> I'm really starting to get a "grip" on how things work and have configured
> my own CEC file to compile and include custom drivers in an image. I did
> some reading on the SDK about how to include additional files in an SDK.
> The only thing I saw was that I could include a directory which contain
> the file(s) that I want included. However, in one situation, I am trying
> to include just the windev.h header file. Is it possible to include
> (specify) just that file out of the directory which contains many, many
> header files. It's either that or I need to add a copy command to my cec
> file to copy out the header file to a "working" directory to include.
>
> Thanks,
>
>
> "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
> wrote in message news:uS1ivMkgFHA.3316@xxxxxxxxxxxxxxxxxxxxxxx
>> WinINet is in the catalog under the browser components. It's call
>> Windows Internet Services.
>>
>> You didn't tell us which base configuration (WebPad, Internet Appliance,
>> etc., etc.), you used as the base for your OS configuration. That would
>> probably tell us where the component came from.
>>
>> 1. Library files are not associated with header files. Header files
>> might define function calls which are implemented in one or more
>> libraries, but that's it. As far as what goes into the SDK, when you
>> include a component in the OS, that 'tells' the SDK generator that, hey,
>> here are some .h files and some .lib files that need to be in the SDK.
>>
>> 2. Including header files in your drivers or OS components doesn't force
>> libraries to be in the image. If your SOURCES files are built correctly
>> and reference the sysgened library set, you'll get a library-not-found
>> error when linking with a component library that doesn't exist in the OS
>> (this is a good thing, since it points out that your component won't work
>> on the real device).
>>
>> 3. Read up on exporting a SDK. You can add whatever extra files you want
>> to it.
>>
>> Paul T.
>>
>> "J Garcia" <jggarcia@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:eqGNwajgFHA.3912@xxxxxxxxxxxxxxxxxxxxxxx
>>> First, the build - we are using PB4.2. we use the wizard to create a
>>> customized configuration using the GEODE BSP as a base. It has a
>>> graphical interface. We select the MFC and C Runtime Libraries options
>>> in the wizard. We also select hive-based registry. After the wizard
>>> finishes, we add support for ATAPI PCI/IDE storage device.
>>>
>>> We add two custom device drivers for i/o devices that we build - one is
>>> for generic input output of a keypad and the other is for a DSP board.
>>>
>>> This image compiles and downloads fine.
>>>
>>> I then create an SDK for this to use in eVC++. In eVC++ I create a new
>>> (generic) MFC application and compile. I get a linker error that it
>>> can't find the wininet.lib file. Everything will work fine if I add the
>>> $(_WINCEROOT)\PUBLIC\IE\OAK\LIB\X86\RETAIL to the libary inclusion
>>> directory listing.
>>>
>>> Nowhere in our system do we add support for IE. The only thing I do see
>>> unders "Standard Shell" option support for "Internet Explorer UI
>>> component" and "Pocket Internet Explorer UI component".
>>>
>>> 1. Why are these added?
>>> 2. Even though the above components are added, why doesn't the
>>> wininet.lib file get explicitely added to the SDK? Or is it even needed
>>> for those components?
>>>
>>> I will accept that the problem comes from our drivers and the include
>>> files used. For instance, we add windev.h to get the CTL_CODE macro.
>>> Which brings up additional questions as I'm not familiar with
>>> header/library file relations.
>>>
>>> 1. How are library files associated with header files. That is, when I
>>> include specific header files for code that is included in a library
>>> file, where is the association made to the compiler/linker? Or does the
>>> linker check all libraries to find the module.
>>> 2. What header files would force a required wininet.lib?
>>> 3. When we include the windev.h file in an application, the file is
>>> missing unless we specify the include path. How do we "force" the SDK to
>>> include header files that we are using in our custom drivers?
>>>
>>> thanks in advance
>>>
>>
>>
>
>
.
- References:
- where is wininet.lib coming from?
- From: J Garcia
- Re: where is wininet.lib coming from?
- From: Paul G. Tobey [eMVP]
- Re: where is wininet.lib coming from?
- From: J Garcia
- where is wininet.lib coming from?
- Prev by Date: Re: OS image will not load driver.
- Next by Date: Re: pxa270 resume from sleep (mainstone II)
- Previous by thread: Re: where is wininet.lib coming from?
- Next by thread: Add bluetooth support to CE .NET 4.2 core
- Index(es):
Relevant Pages
|
|
