Exiv2

Hi Steve,

You can get any version from SVN by referring to its tag, which by convention is the version number:

$ svn checkout svn://dev.exiv2.org/svn/tags/<version>

Use any tag as the <version>, e.g.,

$ svn checkout svn://dev.exiv2.org/svn/tags/0.19

Alternatively, you can also still download all the previously released tarballs and executables from the archive

Please be careful with the terminology, to avoid confusion. There is no Exiv2 release 0.19.1. Maybe Ubuntu had such a package (then it would probably have been called 0.19-1), but the Exiv2 project never released a version 0.19.1 and you won't be able to get Ubuntu packages from the Exiv2 SVN or archive. Also, there is no Exiv2 version 0.2.0, do you mean 0.20? That's the latest released version of Exiv2.

Andreas

Andreas,

Thanks for the correction on 0.2.0 versus 0.20. It's the latter I meant, not the former. Moving on....

There is no version 0.19.1?
I get this from my working Cygwin one on a -v command:

>> exiv2 -V
exiv2 0.19.1
Copyright (C) 2004-2009 Andreas Huggel.

In Cygwin I had 0.19 running, then you made the changes to include the -g command and added the namespaces for iView MP/MS Expression Media, all in the same build. I SVN'd that and now I'm looking to do the same for the version running on my Linux laptop. Might it have been only a temporary "snapshot" or "test" build? If so, it's done me very well these several months: my SVN folder shows it was last modified on April 19 of this year.

BTW: the latest version available via the Ubuntu repositories is 0.18 (this gleaned after many apt-get updates, both in terminal and via Synaptic Package Manager). That Canonical might have had an "unofficial" 0.19-1 in its repos is therefore highly unlikely; my Ubu version is two behind the latest, so I won't rule it out entirely. Such a thing was, however, not made available to me. And anyway, it was in Cygwin, not Ubuntu GNOME, that I saw (and from the c&p above am still seeing) the *.1 in that version number. Just to avoid confusion.

In the meantime, I'll try the steps you described in the last post to this thread and see what results I get. Maybe between April and now, the whole of version 0.19 equated to all the commands, patches and bug corrections (originally?) offered in your repos as 0.19.1. Time and trial will tell. don't want to "roll back" the version on my laptop, either, but if it was all 0.19, I might not be doing anything of the sort.

Thanks for the reply.

Steve W

Right, we temporarily had 0.19.1 in the repository. That sort of thing helps application developers test their apps during the development of a new release. So yes, if you have a revision from SVN, that may have version 0.19.1. But there was never an officially released version 0.19.1, it became 0.20 and I recommend you upgrade to that.

Andreas

Well, I was able to take the Ubuntu laptop to version 0.20 with no problems so far: at least no "can't find {long-string-with-altogether-too-new-release-number-at the-end}.so" -- typical of previous Ubu installs -- or stack-dumping (you'll recall my mentioning that w/re my attempt to install same on Cygwin). Time will tell, but there oughtn't be any too-big issues. At least now the laptop has a version that includes the "-g" option.

I read in the repository pages about the new error-trapping. It sounds great, but I'd like to be able to see it "in action" on my Windows box in Cygwin. Have there been any patches made (per complaints like mine and Matthias Baas') to the tarball for v.0.20 since it was first made, or would I be better off trying again with an SVN snapshot?

Steve W.

Just so you know the exact error I'm getting in Cygwin, I tried another reinstall of version 0.20 and then tried a -V command.
Here's the stdout from that:

[/exiv2-0.20]
rxvt-cygwin>> exiv2 -V
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
Aborted (core dumped)

[/exiv2-0.20]

Am I missing something? Should I try reinstalling gcc? Or should I go with the precompiled Windows binary until some of the bugs are worked out?

Steve W.

Steve

Can I help you? I've lost the plot a little here. I seldom have any difficulty building exiv2 on Cygwin or Ubuntu or Mac. Universal builds on the Mac are a little troublesome, however I don't think you're concerned. The code builds on Windows using most (all?) of Microsoft's versions of DevStudio - including the free DevStudio C++ Express editions (7.1/2003 and up).

I've just done a sync with the repos and built on Cygwin. I've pulled down the 0.20 tarball. Both build without any difficulty.

Anyway, I'm happy to help you by building stuff, zipping it, and putting it on clanmills.com for you, if you think that would help you. If I can't build something for you, I'm willing to investigate. Let me know: robin@clanmills.com

295 /c/gnu.master/exiv2> svn info
Path: .
URL: svn://dev.exiv2.org/svn/trunk
Repository Root: svn://dev.exiv2.org/svn
Repository UUID: b7c8b350-86e7-0310-a4b4-de8f6a8f16a3
Revision: 2342
Node Kind: directory
Schedule: normal
Last Changed Author: cgilles
Last Changed Rev: 2342
Last Changed Date: 2010-09-07 07:20:35 -0700 (Tue, 07 Sep 2010)

283 /c/gnu/exiv2/src/.libs> dir *.exe (gnu.master/exiv2 ~ copied to ~> /c/gnu/exiv2
exiv2.exe metacopy.exe taglist.exe
284 /c/gnu/exiv2/src/.libs> ./exiv2 -V
exiv2 0.21
Copyright (C) 2004-2010 Andreas Huggel.

289 /c/gnu/exiv2-0.20/src/.libs> ./exiv2 -V
exiv2 0.20
Copyright (C) 2004-2010 Andreas Huggel.

A little sanity check:
299 /c/gnu/exiv2> ls alt /c/R.jpg
-rwx-----+ 1 Administrators None 4607925 2010-09-05 12:52 /c/R.jpg
300 /c/gnu/exiv2> src/.libs/exiv2 -pt /c/R.jpg | wc
108 681 8056
301 /c/gnu/exiv2> cd ../exiv2-0.20/
302 /c/gnu/exiv2-0.20> src/.libs/exiv2 -pt /c/R.jpg | wc
100 452 6874
303 /c/gnu/exiv2-0.20>
(Andreas must have added some tags between 0.20 and 0.21.)

Steve Wright wrote:

Just so you know the exact error I'm getting in Cygwin, I tried another reinstall of version 0.20 and then tried a -V command.
Here's the stdout from that:
[...]
Am I missing something? Should I try reinstalling gcc? Or should I go with the precompiled Windows binary until some of the bugs are worked out?

Steve W.

A specific error that appeared (oh at least 200 times) both in the make and cmake stages from the SVN checkout I pulled down this morning was:
[pre]*361: warning: visibility attribute not supported in this configuration; ignored*[/pre]
The error numbers were often different, some three-, some four-digits in length, and on various .cpp and .hpp files right up to the big one (exiv2.cpp), with the outcome that the build (which I left behind in /usr/local/bin with a different file extension) is about 20kb "lighter" than the 0.19.1 I am still able to use. I don't think this makes much difference, however; just pointing it out.

Regardless, I think I'm missing something. Installing or updating Exiv2 is only the latest in a short string of similar compile/build flubs -- stuff I've been able to install in Cygwin before but not this time around.

Yes, Robin, I'd like one of your builds.

Steve W

A specific error that appeared (oh at least 200 times) both in the make and cmake stages from the SVN checkout I pulled down this morning was:
[pre]*361: warning: visibility attribute not supported in this configuration; ignored*[/pre]

Steve,

That means that the symbol visibility thing (#523) is not supported on this platform. You can manually disable it to avoid the warnings by adding a --disable-visibility option to the ./configure step. The resulting exiv2 utility works the same, with or without this feature.

Before you rebuild, could you send me the config.log and config/config.h files from your last build to investigate?

Andreas

Steve

http://clanmills.com/files/exiv2/exiv2-0.19.zip (16mb)
http://clanmills.com/files/exiv2/exiv2-0.20.zip (8mb)

Please see file ReadMeCygwin.zip in the archive for details. 0.20 is smaller because it doesn't include the test directory.

Your feedback is requested. If you have any issues with how the archives has been created, please discuss it off-line and I will modify and update the zips. robin@clanmills.com

Andreas,

After that last build attempt yesterday, I trashed all previous source files, SVN folders and the like associated with version 0.20. I did another svn checkout download, and used your suggestion on the --disable-visiblity option at the ./configure stage. Attached you should find a .zip with the files you requested.

On this run (./configure,make,make install) there was not a lot of difference in the result. exiv2 -V still threw that error I specified in my previous post. This time, at least, I know it's not my cmake, make or anything else from the Cygwin setup. If I had to make a guess, I'd say it's running into mixed-and-matched DLLs or something.

Back to the drawing board, so to speak.

S. Wright

Andreas Huggel wrote:

A specific error that appeared (oh at least 200 times) both in the make and cmake stages from the SVN checkout I pulled down this morning was:
[pre]*361: warning: visibility attribute not supported in this configuration; ignored*[/pre]

Steve,

That means that the symbol visibility thing (#523) is not supported on this platform. You can manually disable it to avoid the warnings by adding a --disable-visibility option to the ./configure step. The resulting exiv2 utility works the same, with or without this feature.

Before you rebuild, could you send me the config.log and config/config.h files from your last build to investigate?

Andreas

Call this one "Solved."

Robin Mills got the full story in an email, but suffice it to say that "massaging" the system memory by way of a boot-time scan with Avast! antivirus cured whatever problems Cygwin was having making use of the 0.20 install.

Steve W.