vishal thakur wrote:
> Firstly according to me this should not happen. With library u must be able
> to link to another program else what would be use of library.
>
> R u sure that unresolved symbols are related with same (project B ) library.
>
> On 2/26/07, Sumit Chawla <[EMAIL PROTECTED]> wrote:
>> Hi
>>
>> In one of my code A i was using function of project B. The project gives a
>> B.lib on compiling. I added the B.lib to the list of Linker Libraries for
>> project A, but got linker error showing unresolved symbols. Then i removed
>> B.lib and added B as dependency project of A, and i was able to make my
>> program work. Now my doubt is about the difference between two. i.e.
>> linking a library statically to your program vs using project
>> dependencies.
>> Moreover I dont find any information related to project dependencies in
>> .DSW
>> file of my project A. Where is that information stored. Both of my
>> projects
>> A and B were compiled using VC++ 6.0 .
>>
>> Any help on these topics will be of great use.
>> --
>> Regards
>> Sumit Chawla ("eNetra : Hail the Invention")
Dependency information should be stored in the DSW/DSP files. And the
correct way to build libraries into an executable is to use
dependencies. The only time you actually enter the library name into
the linker settings is when a third-party library is being used.
Consider upgrading to a newer compiler suite: VS.NET 2003/2005 have
very nice solution configuration and dependency managers. Way better
than the VC6 clunky method of doing the equivalent.
--
Thomas Hruska
CubicleSoft President
Ph: 517-803-4197
*NEW* VerifyMyPC 2.2
Change tracking and management tool.
Reduce tech. support times from 2 hours to 5 minutes.
Free for personal use, $10 otherwise.
http://www.CubicleSoft.com/VerifyMyPC/
