- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I specify 2 paths, separated by a semicolon (as instructed under Project/Properties/Linker/General/AdditionalLibraryDirectories), "CommandLine" shows it generates two /LIBPATH statements, so I had expected the Linker would parse the line and re-append the values, but it appears that the first path is being lost and only the 2nd one is used.
Has anyone else experienced this?
For Additional Library Directories, I'm entering
../../../lib;Debug/
and the error message shows it can't find a file that I have in ../../../lib, but is looking in /Debug instead. This is behaving as I'd expect a normal command line parse to act ... which is to use the last occurence of a multi-specified option ... or am I doing something wrong?
Has anyone else experienced this?
For Additional Library Directories, I'm entering
../../../lib;Debug/
and the error message shows it can't find a file that I have in ../../../lib, but is looking in /Debug instead. This is behaving as I'd expect a normal command line parse to act ... which is to use the last occurence of a multi-specified option ... or am I doing something wrong?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should add that I tried replacing the relative path reference ("../../../lib") with an absolute path reference and it didn't make any difference ... the link fails telling me it can't find the target file in the 2nd path I specified.
If I switch the path order, it finds the file OK, but then fails on the files belonging to the other path.
If I switch the path order, it finds the file OK, but then fails on the files belonging to the other path.
Message Edited by [email protected] on 09-29-2005 07:02 AM
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page