Re: where has linker got list of libraries from in command line?

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



Inline...
"Stephen Howe" <sjhoweATdialDOTpipexDOTcom> wrote in message
news:bl9st45j008tgm70r8elesgppcasjqspua@xxxxxxxxxx
Hi

Using Visual Studio 2005.

It is now so complicated that i dont even know where input is
specified anymore

If I right-click on a MFC project that is dependent on a variety of
user-defined subsidiary DLLs, cliick on Linker, click on command line,
I see a variety of LIBs that I recognise.

For example?


But if I click on Linker, Input - none of them are specified.
Where has VS2005 got these from?

Are you referring to the default libraries?


I am emitting #pragma comment(lib, libraryname) in object files but
these dont match what I see as linker input, so again, where has it
got this from?

I am perplexed as to where the linker command line libraries specified
are obtained.
There are no env variables set with these either, I have checked.

Is this a strictly academic question or are you trying to solve a problem?


Thanks

Stephen Howe


.



Relevant Pages

  • where has linker got list of libraries from in command line?
    ... It is now so complicated that i dont even know where input is ... I see a variety of LIBs that I recognise. ... But if I click on Linker, Input - none of them are specified. ... I am perplexed as to where the linker command line libraries specified ...
    (microsoft.public.vc.language)
  • Linker error 1104
    ... The project itself links against some import libraries ... When I now look at the linker command line it ... the correct linker command line would be: ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Defining many classes in a single file
    ... And one can declare just as many in a header file. ... Another reason for one class one file is due to linker ... smallest resolution. ... In this case, you can have libraries. ...
    (comp.lang.cpp)
  • FreeBSD 5.1 BETA 2 make cvsup-without-gui fails
    ... checking if the linker is GNU ld... ... checking whether the linker supports shared libraries... ... checking if libtool supports shared libraries... ...
    (freebsd-current)
  • Re: orphaned port?
    ... checking if the linker is GNU ld... ... updating cache .././config.cache ... checking if libtool supports shared libraries... ...
    (freebsd-questions)