[SCM] exiv2 packaging branch, master, updated. debian/0.25-3.1-3734-gdcbc29a

[Maximiliano Curia]

Gitweb-URL: http://git.debian.org/?p=pkg-kde/kde-extras/exiv2.git;a=commitdiff;h=59dccf4

The following commit has been merged in the master branch:
commit 59dccf42e3167ee213bb331558f0543aedf2d390
Author: Robin Mills <robin at clanmills.com>
Date:   Wed Feb 11 15:25:33 2015 +0000

    Added to msvc2005/ReadMe.txt in response to Forum Topic 1880.
---
 msvc2005/ReadMe.txt | 154 +++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 153 insertions(+), 1 deletion(-)

diff --git a/msvc2005/ReadMe.txt b/msvc2005/ReadMe.txt
index 4e0c58e..1776fc4 100644
--- a/msvc2005/ReadMe.txt
+++ b/msvc2005/ReadMe.txt
@@ -8,7 +8,7 @@ exiv2\msvc2005\ReadMe.txt
 |          with Visual Studio 2003/5/8                      |
 +-----------------------------------------------------------+
 
-Updated: 2015-02-10
+Updated: 2015-02-11
 
 Robin Mills
 http://clanmills.com
@@ -34,6 +34,10 @@ T A B L E  o f  C O N T E N T S
 3.2  Running the test suite
 
 4    Building Applications to use Exiv2
+4.1  Recommended work-flow to create applications
+4.2  Link order
+4.3  tools/bin/depends32.exe and depends64.exe
+4.4  exiv2.exe --verbose --version
 
 5    Acknowledgment of prior work
 5.1  Differences between inherited project and the exiv2 projects
@@ -266,6 +270,8 @@ T A B L E  o f  C O N T E N T S
 
 4    Building Applications to use Exiv2
 
+4.1  Recommended work-flow to create applications
+
      a) add your code code to a sample applications (such as exifprint.exe)
         get the code building and running from there.
         our program will be called exifprint.exe
@@ -289,6 +295,152 @@ T A B L E  o f  C O N T E N T S
     to your build tree.  When you do this, you will have to explicitly link
     the libraries you have copied.
 
+4.2  Link order
+
+     The correct order is revealed in Visual Studio, by examining exifprint/Properties/Linker/Command-Line:
+
+     /OUT:"C:
-- 
exiv2 packaging