[SCM] exiv2 packaging branch, master, updated. debian/0.25-3.1-3734-gdcbc29a
Maximiliano Curia
maxy at moszumanska.debian.org
Thu Jul 13 17:44:52 UTC 2017
Gitweb-URL: http://git.debian.org/?p=pkg-kde/kde-extras/exiv2.git;a=commitdiff;h=666513c
The following commit has been merged in the master branch:
commit 666513c71a3a8a9ad29f66d36f40c3090ec9d1f5
Author: Robin Mills <robin at clanmills.com>
Date: Wed Feb 11 04:32:13 2015 +0000
Updated msvc2005/ReadMe.txt to include comments in http://dev.exiv2.org/boards/3/topics/1880
---
msvc2005/ReadMe.txt | 108 +++++++++++++++++++++++++++++++++-------------------
1 file changed, 69 insertions(+), 39 deletions(-)
diff --git a/msvc2005/ReadMe.txt b/msvc2005/ReadMe.txt
index 5685587..4e0c58e 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-01-12
+Updated: 2015-02-10
Robin Mills
http://clanmills.com
@@ -33,8 +33,10 @@ T A B L E o f C O N T E N T S
3.1 buildall.bat
3.2 Running the test suite
-4 Acknowledgment of prior work
-4.1 Differences between inherited project and the exiv2 projects
+4 Building Applications to use Exiv2
+
+5 Acknowledgment of prior work
+5.1 Differences between inherited project and the exiv2 projects
## End Table of Contents End ##
####
@@ -46,9 +48,10 @@ T A B L E o f C O N T E N T S
Some Express editions don't support 64 bit builds
however it is possible to build 32 bit libraries with "Express".
See notes below about DevStudio Express and building only Win32 or x64 builds
-
- You need a DOS version of perl to build openssl. Not the cygwin version. I use ActiveState Perl.
-
+
+ You need a DOS version of perl to build openssl. Not the cygwin version.
+ I use ActiveState Perl.
+
You need Cygwin to run the test suite because it is written in bash.
1.2 Install zlib and expat sources.
@@ -56,27 +59,27 @@ T A B L E o f C O N T E N T S
c:\gnu>dir
Directory of c:\gnu
- 2010-12-05 10:05 <DIR> exiv2 <--- this tree
- 2012-05-04 23:35 <DIR> expat <--- "vanilla" expat 2.1.0 source tree
- 2012-05-04 23:35 <DIR> zlib <--- "vanilla" zlib 1.2.7 source tree
- 2012-05-04 23:35 <DIR> curl <--- "vanilla" curl 7.39.0 source tree
- 2012-05-04 23:35 <DIR> openssl <--- "vanilla" openssl 1.0.1j source tree
- 2012-05-04 23:35 <DIR> libssh <--- "vanilla" libssh 0.5.5 source tree
+ 2010-12-05 10:05 <DIR> exiv2 <--- this tree
+ 2012-05-04 23:35 <DIR> expat <--- "vanilla" expat 2.1.0 source tree
+ 2012-05-04 23:35 <DIR> zlib <--- "vanilla" zlib 1.2.7 source tree
+ 2012-05-04 23:35 <DIR> curl <--- "vanilla" curl 7.39.0 source tree
+ 2012-05-04 23:35 <DIR> openssl <--- "vanilla" openssl 1.0.1j source tree
+ 2012-05-04 23:35 <DIR> libssh <--- "vanilla" libssh 0.5.5 source tree
c:\gnu>
-
+
You can obtain the libraries from http://clanmills.com/files/exiv2libs.zip (20mb)
I copy those to the directory c:\exiv2libs
The script msvc2005/copylibs.bat will copy them from c:\exiv2libs to the correct location
-
+
11/05/2014 07:26 AM <DIR> curl-7.39.0
12/07/2014 09:18 AM <DIR> expat-2.1.0
12/17/2014 09:40 AM <DIR> libssh-0.5.5
12/17/2014 09:38 AM <DIR> openssl-1.0.1j
12/07/2014 09:18 AM <DIR> zlib-1.2.7
-
+
The following directories are also in the archive for use by msvc2003
- 01/07/2015 11:11 AM <DIR> expat-2.0.1
- 01/07/2015 11:10 AM <DIR> zlib-1.2.3
+ 01/07/2015 11:11 AM <DIR> expat-2.0.1
+ 01/07/2015 11:10 AM <DIR> zlib-1.2.3
The URLs from which to obtain zlib and expat are documented in exiv2\msvc2003\ReadMe.txt
expat-2.1.0 is available from http://voxel.dl.sourceforge.net/sourceforge/expat/expat-2.1.0.tar.gz
@@ -92,7 +95,7 @@ T A B L E o f C O N T E N T S
x 2 Platforms (x64|Win32)
x 4 Configurations (Debug|Release|DebugDLL|ReleaseDLL)
= 36x2x4 = 288 builds.
-
+
When building with webready, you add 5 libraries for a total of 328 builds.
If you haven't installed the x64 compiler, don't select the 64 bit configurations!
@@ -107,17 +110,17 @@ T A B L E o f C O N T E N T S
Building the complete library with webready support requires building
5 additional libraries. This is time consuming. The build time
increases from 5 to 20 minutes.
-
+
By default, you will not build with webready.
-
+
To build with webready:
1 copy include\exiv2\exv_msvc-webready.h include\exiv2\exv_msvc.h
- 2 open msvc2005\exiv2-webready.vcproj
+ 2 open msvc2005\exiv2-webready.vcproj
1.5 What is built
The DLL builds use the DLL version of the C runtime libraries
The Debug|Release builds use static C runtime libraries
- This is discussed in exiv2\msvc2003\ReadMe.txt
+ This is discussed in exiv2\msvc2003\ReadMe.txt
1.6 Express editions of DevStudio (or 32 bit only builds, or 64 bit only builds)
Some Express Editions do not provide a 64 bit compiler.
@@ -131,7 +134,7 @@ T A B L E o f C O N T E N T S
1) Restore the build environment with: setbuild.py all
2) Select x64 bit builds only with: setbuild.py x64
- If you don't have python available (it's a free download from ActiveState.com),
+ If you don't have python available (it's a free download from ActiveState.com),
you can "doctor" to project files manually to remove mentiosn of X64 using an editor:
Cleanup your tree and edit the files.
@@ -154,14 +157,14 @@ T A B L E o f C O N T E N T S
2 Design
expat and zlib1.2.5 (and earlier) do not provide 64 bit builds for DevStudio.
-
+
The projects provided for zlib1.2.7 support 64 bit builds, however it didn't
work cleanly for me. They use different projects for VC9 and VC10.
They don't provide support for VC8 or 11beta.
-
+
I have created build environments for zlib and expat within exiv2/msvc2005.
I don't include the source code for zlib or expat - only the build environment.
-
+
You are expected to install the "vanilla" expat and zlib libraries
in a directory at the same level as exiv2.
I personally always build in the directory c:\gnu,
@@ -188,7 +191,7 @@ T A B L E o f C O N T E N T S
exiv2lib\x64\{Debug|Release|DebugDLL|ReleaseDLL} 64 bit builds
Final builds and include directories (for export to "foreign" projects)
- bin\{win32|x64}\Win32\{Debug|Release|DebugDLL|ReleaseDLL}
+ bin\{win32|x64}\Win32\{Debug|Release|DebugDLL|ReleaseDLL}
2.2 Relationship with msvc2003 build environment
msvc2005 is similar to msvc2003.
@@ -199,7 +202,7 @@ T A B L E o f C O N T E N T S
4) msvc2005 supports DevStudio 2005 and later (no support for 2003)
5) msvc2005 does not require you to build 'vanilla' expat and zlib projects in advance
6) msvc2005 does not support the organize application
- 7) msvc2005 supports building with zlib1.2.7 or 1.2.8
+ 7) msvc2005 supports building with zlib1.2.7 or 1.2.8
7) msvc2005 supports building with expat2.1.0
msvc2003 will continue to be supported for 32 bit builds using DevStudio 2003/05/08,
@@ -217,7 +220,7 @@ T A B L E o f C O N T E N T S
3.2 Running the test suite
You will need to install cygwin to run the test suite.
-
+
This is a two stage process:
Step1: Build exiv2 for cygwin and run the test suite
Typical Unix type build:
@@ -225,41 +228,68 @@ T A B L E o f C O N T E N T S
./configure --disable-visibility
export PKG_CONFIG_PATH=$PWD/config
make clean ; make ; make samples ; make install ; cd test ; make test
-
+
Step2: set the environment variable EXIV2_BINDIR appropriately and rerun make test
export EXIV2_BINDIR=<path-to-directory-with-exiv2.exe>
I find the following little bash loop very useful. You should test
against all the directories in the msvc2005/bin directory:
- for d in $(find /c/gnu.2005/exiv2/msvc2005/bin -name exiv2.exe -exec dirname {} ";"); do
+ for d in $(find /c/gnu.2005/exiv2/msvc2005/bin \
+ -name exiv2.exe -exec dirname {} ";"); do
export EXIV2_BINDIR=$d
echo ---------------------------------
echo ---- $d ----
echo ---------------------------------
make test
done
-
+
Free gift: (you get what you pay for)
The script testMSVC.sh to runs this loop for you.
The script verifyMSVC.sh validates the output of testMSVC.sh
I've added those for my convenience and I hope you'll find them useful.
And to pass the time (the test suite takes about an hour to run)
- I recommend running listdlls exiv2.exe occasionally during testing to be confident
- that the test suite is running the MSVC built versions of exiv2 and libraries.
-
+ I recommend running listdlls exiv2.exe occasionally during testing to be
+ confident that the test suite is running the MSVC built
+ versions of exiv2 and libraries.
+
From cygwin:
while sleep 1 do; listdlls exiv2.exe ; done
or
while sleep 10 do ; listdlls exiv2.exe | grep exiv2.exe ; done
-
+
Note: Cygwin currently ships diff-utils 2.9.2 which treats binary files differently
from 2.8.7 (on Mac) and 3.2 (on Ubuntu 12.04). For this reason, the executable (and
support dlls) for GNU diff.exe 2.8.7 is provided in msvc2003/diff.exe.
The test suite has been "doctored" on cygwin to modify the path appropriately to
use this preferred version of diff.exe.
-
-4 Acknowledgement of prior work
+
+4 Building Applications to use Exiv2
+
+ 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
+ you will be very confident that your code works!
+
+ b) copy <exiv2dir>/msvc2005/exifprint to <exiv2dir>/msvc2005/yourprojectname
+ get yourprojectname.exe to build and run.
+ By using <exiv2dir>/msvc2005/exifprint as a template,:
+ i) you can build 32/64 dll/static debug/release "out of the box".
+ ii) your include path, dependent libraries and link order are already set.
+ Revert your changes to <exiv2dir>/msvc2005/exifprint
+
+ c) move <exiv2dir>/msvc2005/yourprojectname in your buildtree.
+
+ d) It's a good idea for your buildtree to reference <exiv2dir>/msvc2005
+ When you reference <exiv2dir>, you can update <exiv2dir> occasionally
+ and rebuild with little effort.
+
+ Of course, there are always other ways to achieve your goals in software.
+ You may prefer to copy the generated libs and dlls in bin/$platform/$configuration
+ to your build tree. When you do this, you will have to explicitly link
+ the libraries you have copied.
+
+5 Acknowledgement of prior work
This work is based on work by the following people:
zlib 64 bit build
@@ -274,7 +304,7 @@ T A B L E o f C O N T E N T S
I recognise and respect the work performed by those individuals.
-4.1 Differences between inherited projects and the exiv2 projects
+5.1 Differences between inherited projects and the exiv2 projects
There is no compatiblity.
# That's all Folks!
--
exiv2 packaging
More information about the pkg-kde-commits
mailing list