Using $(SolutionDir)../ as the prefix for include directories interfere with using projects in external solutions
The solution is to use $(ProjectDir)../../ instead of $(SolutionDir)../
This makes the project able to be linked to a solution that is outside the exiv2 directory hierarchy and keeps the include paths relative to the libexiv2 (or similar) project rather than relying on being able to reference the exiv2 include folders from the external solution.
Specifically, this problem is found in the vcproj files of the msvc2005 folder. Nowhere else.
- Status changed from New to Assigned
- Priority changed from Low to Normal
Have checked in Revision r4437 to resolve this.
I will close it when I get an indication that this doesn't break any build.
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
- Estimated time changed from 1.00 h to 2.00 h
r4437 Thank you, Sridhar for taking care of this. The buildserver has successfully built/tested this.
Also available in: Atom