Re: where is wininet.lib coming from?

In eVC, you are *always* targeting a device SDK. The drop-down list in the
tool bar indicates which one. One of the characteristics of every SDK is a
set of available library and header files, so the paths to those files are
always in the default list when targeting that SDK. The only case where
you'd need to change your project settings to see a .h file or a .lib file
would be if you add some files to the SDK and put them somewhere other than
the default include or library folders or if you're using a 'library' (not
in the sense of a .lib file, but an external package), which has some extra
..h and/or .lib files that don't come with the SDK (there are settings on the
C/C++ and Link tabs for the locations and, for libraries, names of extra
things that the tools should use).

When you use the new project wizard in eVC to create an application, it
always sets a default set of libraries to be linked with (corelib.lib,
etc.). For some devices, not all of those libraries even exist in the SDK,
you have a step that you always have to do after creating a new project
(remove the bad libraries from the Link options). On headless devices, for
example, the inclusion of commctrl.lib makes no sense, but the wizard always
includes it.

I don't know where your wininet.lib reference is coming from, but the eVC
new project wizard is my guess. Try building a simple, non-MFC, windows
program using the wizard, as a test...

Paul T.

"J Garcia" <jggarcia@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23rPq5qkgFHA.2852@xxxxxxxxxxxxxxxxxxxxxxx
> Thx for the reply. I guess I wasn't clear when I said that it was a
> customized configuration - no base configuration selected. Which is why I
> was supprised by the addition of the components I mentioned and the linker
> in eVC++ looking for that libraby.
>
> Can you explain a little (or give me a good link) that explains how a
> linker find the appropriate libraries - that is, are the specified
> specifically? Or does the linker just browse the libraries in a specified
> directory? etc.
>
> "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
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: where is wininet.lib coming from?
    ... my own CEC file to compile and include custom drivers in an image. ... some reading on the SDK about how to include additional files in an SDK. ... Library files are not associated with header files. ... > libraries to be in the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: where is wininet.lib coming from?
    ... > some reading on the SDK about how to include additional files in an SDK. ... >> You didn't tell us which base configuration (WebPad, Internet Appliance, ... Library files are not associated with header files. ... >> libraries, but that's it. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: where is wininet.lib coming from?
    ... You didn't tell us which base configuration (WebPad, Internet Appliance, ... Library files are not associated with header files. ... As far as what goes into the SDK, ... libraries to be in the image. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE6.0 App Building/Linking using Plat-Builder/SDK
    ... making sure to select Smart Device as the target, ... given that you've already installed your SDK. ... static library, the next DLL, or the EXE. ... You must compile all libraries that you're going to use *for Windows CE*, ...
    (microsoft.public.windowsce.app.development)
  • Re: Adding SDK
    ... When you target the SDK, ... Studio knows where to find its include files, libraries, etc. I'd say that ... Finally I've built the project ... eVC/Visual Studio. ...
    (microsoft.public.windowsce.platbuilder)
Loading