467,879 Members | 1,309 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,879 developers. It's quick & easy.

Using Additional Library Directories & Additional Dependencies

Hello,

I am using Visual Studio-2003. I created a project to build my library.
Since I am using third party libraries as well, I have specified those
additional library dependencies in project as "Additional Dependencies" under
Linker-Input options. Since those libraries are also in different directory,
I specified that library path in project as "Additional Library Directories"
under Linker-General options.

This is where I see some odd behavior. When I compile and link, all my
libraries specified as "Additional Dependencies" appear twice and I get lots
of linking error. When I look under Linker-Command Line property, I see that
each of my library from "Additional Dependencies" is listed there twice, once
with just the name and other with directory path (same path as specified in
"Additional Library Directories").

Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in project
as "Additional Options" under Linker-Command Line options, every thing works
fine (I have to close and restart Visual Studio), but linking works fine
without any errors.

Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?

Any thoughts?

Thanks and Regards
Yogi Watcher

May 25 '07 #1
  • viewed: 16317
Share:
6 Replies
Are these libraries also projects in your solution? If you reference a
library project from another project VS knows how to find the LIB file for
you, you don't have to add additional library directories.

Or, are those library directories set in Visual Studio's global settings?
(Tools/Options, Projects/VC++ Directoires, and "Show directories for" and
"Library files").

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Yogi Watcher" wrote:
Hello,

I am using Visual Studio-2003. I created a project to build my library.
Since I am using third party libraries as well, I have specified those
additional library dependencies in project as "Additional Dependencies" under
Linker-Input options. Since those libraries are also in different directory,
I specified that library path in project as "Additional Library Directories"
under Linker-General options.

This is where I see some odd behavior. When I compile and link, all my
libraries specified as "Additional Dependencies" appear twice and I get lots
of linking error. When I look under Linker-Command Line property, I see that
each of my library from "Additional Dependencies" is listed there twice, once
with just the name and other with directory path (same path as specified in
"Additional Library Directories").

Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in project
as "Additional Options" under Linker-Command Line options, every thing works
fine (I have to close and restart Visual Studio), but linking works fine
without any errors.

Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?

Any thoughts?

Thanks and Regards
Yogi Watcher
May 27 '07 #2
Hello Peter,

No, these additional libraries are not part of my solution. These libraries
are part of third party tool set.

I have not added the library path as VS global project setting. I added it
only as local project option (right click on the project and then properties).

I wonder if VS by default adds all libraries found in the directories
pointed to by "Additional Library Directories" option?

Thanks
Yogi Watcher
"Peter Ritchie [C# MVP]" wrote:
Are these libraries also projects in your solution? If you reference a
library project from another project VS knows how to find the LIB file for
you, you don't have to add additional library directories.

Or, are those library directories set in Visual Studio's global settings?
(Tools/Options, Projects/VC++ Directoires, and "Show directories for" and
"Library files").

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Yogi Watcher" wrote:
Hello,

I am using Visual Studio-2003. I created a project to build my library.
Since I am using third party libraries as well, I have specified those
additional library dependencies in project as "Additional Dependencies" under
Linker-Input options. Since those libraries are also in different directory,
I specified that library path in project as "Additional Library Directories"
under Linker-General options.

This is where I see some odd behavior. When I compile and link, all my
libraries specified as "Additional Dependencies" appear twice and I get lots
of linking error. When I look under Linker-Command Line property, I see that
each of my library from "Additional Dependencies" is listed there twice, once
with just the name and other with directory path (same path as specified in
"Additional Library Directories").

Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in project
as "Additional Options" under Linker-Command Line options, every thing works
fine (I have to close and restart Visual Studio), but linking works fine
without any errors.

Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?

Any thoughts?

Thanks and Regards
Yogi Watcher
May 29 '07 #3
Hello,

Can anybody help me here?

"Yogi Watcher" wrote:
Hello Peter,

No, these additional libraries are not part of my solution. These libraries
are part of third party tool set.

I have not added the library path as VS global project setting. I added it
only as local project option (right click on the project and then properties).

I wonder if VS by default adds all libraries found in the directories
pointed to by "Additional Library Directories" option?

Thanks
Yogi Watcher
"Peter Ritchie [C# MVP]" wrote:
Are these libraries also projects in your solution? If you reference a
library project from another project VS knows how to find the LIB file for
you, you don't have to add additional library directories.

Or, are those library directories set in Visual Studio's global settings?
(Tools/Options, Projects/VC++ Directoires, and "Show directories for" and
"Library files").

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Yogi Watcher" wrote:
Hello,
>
I am using Visual Studio-2003. I created a project to build my library.
Since I am using third party libraries as well, I have specified those
additional library dependencies in project as "Additional Dependencies" under
Linker-Input options. Since those libraries are also in different directory,
I specified that library path in project as "Additional Library Directories"
under Linker-General options.
>
This is where I see some odd behavior. When I compile and link, all my
libraries specified as "Additional Dependencies" appear twice and I get lots
of linking error. When I look under Linker-Command Line property, I see that
each of my library from "Additional Dependencies" is listed there twice, once
with just the name and other with directory path (same path as specified in
"Additional Library Directories").
>
Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in project
as "Additional Options" under Linker-Command Line options, every thing works
fine (I have to close and restart Visual Studio), but linking works fine
without any errors.
>
Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?
>
Any thoughts?
>
Thanks and Regards
Yogi Watcher
>
Jun 13 '07 #4

"Yogi Watcher" <Yo*********@discussions.microsoft.comwrote in message
news:E9**********************************@microsof t.com...
Hello,

Can anybody help me here?
You can configure the list of directories the linker searches. I think
you've already found that. The linker still only uses libraries named in
the makefile, not all libraries in the directory.

You can use a #pragma comment to cause a library to be linked by all users
of a header file though, which may fill your need.
>
"Yogi Watcher" wrote:
>Hello Peter,

No, these additional libraries are not part of my solution. These
libraries
are part of third party tool set.

I have not added the library path as VS global project setting. I added
it
only as local project option (right click on the project and then
properties).

I wonder if VS by default adds all libraries found in the directories
pointed to by "Additional Library Directories" option?

Thanks
Yogi Watcher
"Peter Ritchie [C# MVP]" wrote:
Are these libraries also projects in your solution? If you reference a
library project from another project VS knows how to find the LIB file
for
you, you don't have to add additional library directories.

Or, are those library directories set in Visual Studio's global
settings?
(Tools/Options, Projects/VC++ Directoires, and "Show directories for"
and
"Library files").

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Yogi Watcher" wrote:

Hello,

I am using Visual Studio-2003. I created a project to build my
library.
Since I am using third party libraries as well, I have specified
those
additional library dependencies in project as "Additional
Dependencies" under
Linker-Input options. Since those libraries are also in different
directory,
I specified that library path in project as "Additional Library
Directories"
under Linker-General options.

This is where I see some odd behavior. When I compile and link, all
my
libraries specified as "Additional Dependencies" appear twice and I
get lots
of linking error. When I look under Linker-Command Line property, I
see that
each of my library from "Additional Dependencies" is listed there
twice, once
with just the name and other with directory path (same path as
specified in
"Additional Library Directories").

Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in
project
as "Additional Options" under Linker-Command Line options, every
thing works
fine (I have to close and restart Visual Studio), but linking works
fine
without any errors.

Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?

Any thoughts?

Thanks and Regards
Yogi Watcher
Jun 14 '07 #5
Thank you.

If you look at the original post, you will see that my problem is little
different. When I use linker path using Additional Library Directories, then
each of the library named in additional dependancy is used twice, while if I
use linker path as additional options this does not happen.

"Ben Voigt [C++ MVP]" wrote:
>
"Yogi Watcher" <Yo*********@discussions.microsoft.comwrote in message
news:E9**********************************@microsof t.com...
Hello,

Can anybody help me here?

You can configure the list of directories the linker searches. I think
you've already found that. The linker still only uses libraries named in
the makefile, not all libraries in the directory.

You can use a #pragma comment to cause a library to be linked by all users
of a header file though, which may fill your need.

"Yogi Watcher" wrote:
Hello Peter,

No, these additional libraries are not part of my solution. These
libraries
are part of third party tool set.

I have not added the library path as VS global project setting. I added
it
only as local project option (right click on the project and then
properties).

I wonder if VS by default adds all libraries found in the directories
pointed to by "Additional Library Directories" option?

Thanks
Yogi Watcher
"Peter Ritchie [C# MVP]" wrote:

Are these libraries also projects in your solution? If you reference a
library project from another project VS knows how to find the LIB file
for
you, you don't have to add additional library directories.

Or, are those library directories set in Visual Studio's global
settings?
(Tools/Options, Projects/VC++ Directoires, and "Show directories for"
and
"Library files").

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Yogi Watcher" wrote:

Hello,
>
I am using Visual Studio-2003. I created a project to build my
library.
Since I am using third party libraries as well, I have specified
those
additional library dependencies in project as "Additional
Dependencies" under
Linker-Input options. Since those libraries are also in different
directory,
I specified that library path in project as "Additional Library
Directories"
under Linker-General options.
>
This is where I see some odd behavior. When I compile and link, all
my
libraries specified as "Additional Dependencies" appear twice and I
get lots
of linking error. When I look under Linker-Command Line property, I
see that
each of my library from "Additional Dependencies" is listed there
twice, once
with just the name and other with directory path (same path as
specified in
"Additional Library Directories").
>
Now, however, if I remove library path from "Additional Library
Directories", and add that same path (with "/LIBPATH:" as prefix) in
project
as "Additional Options" under Linker-Command Line options, every
thing works
fine (I have to close and restart Visual Studio), but linking works
fine
without any errors.
>
Am I doing something wrong? Did I not understand usage of "Additional
Library Directories" & "Additional Dependencies" properties?
>
Any thoughts?
>
Thanks and Regards
Yogi Watcher
>
Jun 14 '07 #6
Hello! Good Site! Thanks you! aonalsqzuk
Jun 21 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Tom | last post: by
1 post views Thread by Marcohp | last post: by
reply views Thread by Denis Sohet | last post: by
3 posts views Thread by Manny Silva | last post: by
83 posts views Thread by liketofindoutwhy | last post: by
reply views Thread by jack112 | last post: by
reply views Thread by MrMoon | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.