libexif-devel — This is the place where your questions about libexif will be answered.

Re: [Libexif-devel] Problems building libexif (multiple definitions of symbol)

[Hubert F. <hfi...@te...>]

On Thu, 2004-12-16 at 11:16 -0500, Arthur Wiebe wrote:
> lol, only a warning. I looked inside po and it didn't look like
> something that should be built. And I have gettext.
> 
> So I guess I'll just go ahead with sudo make install.

make install will fail.

I was just pointing out that the error was in po directory, not in the
binary building process.

Hub
-- 
Crazy French - http://www.figuiere.net/hub/

Re: [Libexif-devel] Problems building libexif (multiple definitions of symbol)

[Arthur W. <ar...@gm...>]

lol, only a warning. I looked inside po and it didn't look like
something that should be built. And I have gettext.

So I guess I'll just go ahead with sudo make install.


On Thu, 16 Dec 2004 10:59:11 -0500, Hubert Figuiere <hfi...@te...> wrote:
> On Thu, 2004-12-16 at 10:08 -0500, Arthur Wiebe wrote:
> > Hi,
> >
> > I've been trying to get libexif  0.6.11 to build on Mac OS X GCC 3.3
> > but seem to be having problems with multiple symbol definitions.
> > Somehow related to libintl and libiconv. I checked my system and I can
> > only find one installation of libiconv and libintl so I have no idea
> > what's up.
> > Here's the output:
> >
> > creating test-mnote
> > if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libexif -I..intl -I..
> > -I/usr/local/include  -g -O2 -g -Wall -Wmissing-declarations
> > -Wmissing-prototypes -MT test-value.o -MD -MP -MF
> > ".deps/test-value.Tpo" -c -o test-value.o test-value.c; \
> > then mv -f ".deps/test-value.Tpo" ".deps/test-value.Po"; else rm -f
> > ".deps/test-value.Tpo"; exit 1; fi
> > /bin/sh ../libtool --mode=link gcc  -g -O2 -g -Wall
> > -Wmissing-declarations -Wmissing-prototypes  -g -Wall -o test-value
> > test-value.o ../libexif/libexif.la -L/usr/local/lib -lintl -liconv -lc
> > gcc -g -O2 -g -Wall -Wmissing-declarations -Wmissing-prototypes -g
> > -Wall -o .libs/test-value test-value.o  ../libexif/.libs/libexif.dylib
> > -lm -L/usr/local/lib /usr/local/lib/libintl.dylib
> > /usr/local/lib/libiconv.dylib -lc
> > ld: warning multiple definitions of symbol _locale_charset
> > /usr/local/lib/libintl.dylib(localcharset.o) definition of _locale_charset
> > /usr/local/lib/libiconv.dylib(localcharset.o) definition of _locale_charset
> > creating test-value
> 
> This only a warning. You can ignore. The build succeeded
> 
> > Making all in po
> > make[2]: *** No rule to make target `all'.  Stop.
> > make[1]: *** [all-recursive] Error 1
> > make: *** [all] Error 2
> >
> > And help would be really appreciated.
> 
> This is where it fails. There is no Makefile in "po" directory. You
> probably miss a package like gettext. Not sure.
> 
> Hub
> --
> Crazy French - http://www.figuiere.net/hub/
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Libexif-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
> 


-- 
<Arthur/>
- http://artooro.blogspot.com  (Weblog)
- http://machcms.sourceforge.net  (MachCMS Project)
- http://acalproj.sourceforge.net  (Calendar Project)

Re: [Libexif-devel] Problems building libexif (multiple definitions of symbol)

[Hubert F. <hfi...@te...>]

On Thu, 2004-12-16 at 10:08 -0500, Arthur Wiebe wrote:
> Hi, 
> 
> I've been trying to get libexif  0.6.11 to build on Mac OS X GCC 3.3
> but seem to be having problems with multiple symbol definitions.
> Somehow related to libintl and libiconv. I checked my system and I can
> only find one installation of libiconv and libintl so I have no idea
> what's up.
> Here's the output:
> 
> creating test-mnote
> if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libexif -I..intl -I..   
> -I/usr/local/include  -g -O2 -g -Wall -Wmissing-declarations
> -Wmissing-prototypes -MT test-value.o -MD -MP -MF
> ".deps/test-value.Tpo" -c -o test-value.o test-value.c; \
> then mv -f ".deps/test-value.Tpo" ".deps/test-value.Po"; else rm -f
> ".deps/test-value.Tpo"; exit 1; fi
> /bin/sh ../libtool --mode=link gcc  -g -O2 -g -Wall
> -Wmissing-declarations -Wmissing-prototypes  -g -Wall -o test-value 
> test-value.o ../libexif/libexif.la -L/usr/local/lib -lintl -liconv -lc
> gcc -g -O2 -g -Wall -Wmissing-declarations -Wmissing-prototypes -g
> -Wall -o .libs/test-value test-value.o  ../libexif/.libs/libexif.dylib
> -lm -L/usr/local/lib /usr/local/lib/libintl.dylib
> /usr/local/lib/libiconv.dylib -lc
> ld: warning multiple definitions of symbol _locale_charset
> /usr/local/lib/libintl.dylib(localcharset.o) definition of _locale_charset
> /usr/local/lib/libiconv.dylib(localcharset.o) definition of _locale_charset
> creating test-value

This only a warning. You can ignore. The build succeeded

> Making all in po
> make[2]: *** No rule to make target `all'.  Stop.
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> 
> And help would be really appreciated.

This is where it fails. There is no Makefile in "po" directory. You
probably miss a package like gettext. Not sure.

Hub
-- 
Crazy French - http://www.figuiere.net/hub/

[Libexif-devel] Problems building libexif (multiple definitions of symbol)

[Arthur W. <ar...@gm...>]

Hi, 

I've been trying to get libexif  0.6.11 to build on Mac OS X GCC 3.3
but seem to be having problems with multiple symbol definitions.
Somehow related to libintl and libiconv. I checked my system and I can
only find one installation of libiconv and libintl so I have no idea
what's up.
Here's the output:

creating test-mnote
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../libexif -I..intl -I..   
-I/usr/local/include  -g -O2 -g -Wall -Wmissing-declarations
-Wmissing-prototypes -MT test-value.o -MD -MP -MF
".deps/test-value.Tpo" -c -o test-value.o test-value.c; \
then mv -f ".deps/test-value.Tpo" ".deps/test-value.Po"; else rm -f
".deps/test-value.Tpo"; exit 1; fi
/bin/sh ../libtool --mode=link gcc  -g -O2 -g -Wall
-Wmissing-declarations -Wmissing-prototypes  -g -Wall -o test-value 
test-value.o ../libexif/libexif.la -L/usr/local/lib -lintl -liconv -lc
gcc -g -O2 -g -Wall -Wmissing-declarations -Wmissing-prototypes -g
-Wall -o .libs/test-value test-value.o  ../libexif/.libs/libexif.dylib
-lm -L/usr/local/lib /usr/local/lib/libintl.dylib
/usr/local/lib/libiconv.dylib -lc
ld: warning multiple definitions of symbol _locale_charset
/usr/local/lib/libintl.dylib(localcharset.o) definition of _locale_charset
/usr/local/lib/libiconv.dylib(localcharset.o) definition of _locale_charset
creating test-value
Making all in po
make[2]: *** No rule to make target `all'.  Stop.
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

And help would be really appreciated.
-- 
<Arthur/>

[Libexif-devel] Cannot build libexif-0.6.11

[Kimberly L. <kim...@cs...>]

Hi all,

I'm building libexif-0.6.11 on Solaris 2.8 and got the following message. 
There is no folder "intl" to be found in the source distribution. Can 
anyone help please?

Thanks a lot!

Kimmy

---------------------------------------------------------------------------
Making all in test
make[2]: Entering directory 
`/disk/sd0g/tools/sun4-sos5/ImageLibraries/libexif-0.6.11/test'
/bin/bash ../libtool --mode=link gcc  -g -O2 -g -Wall 
-Wmissing-declarations -Wmissing-prototypes  -L/usr/local/lib 
-R/usr/local/lib -g -Wall -o test-mem  test-mem.o ../libexif/libexif.la 
../intl/libintl.a
gcc -g -O2 -g -Wall -Wmissing-declarations -Wmissing-prototypes -g -Wall 
-o .libs/test-mem test-mem.o  -L/usr/local/lib ../libexif/.libs/libexif.so 
-lm ../intl/libintl.a -R/usr/local/lib
gcc: ../intl/libintl.a: No such file or directory
make[2]: *** [test-mem] Error 1
make[2]: Leaving directory 
`/disk/sd0g/tools/sun4-sos5/ImageLibraries/libexif-0.6.11/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/disk/sd0g/tools/sun4-sos5/ImageLibraries/libexif-0.6.11'
make: *** [all] Error 2

[Libexif-devel] Progressive exif images?

[Deshpande Gauri-A. <ga...@mo...>]

Hello,
Does anyone has progressive exif images? Can anyone please send me some sample image/s for the same?

Thanks and regards
Gauri

[Libexif-devel] Internet Banking with Bill Pay Fees Waived

[SunTrust <su...@su...>]

<table border="0" cellpadding="0" cellspacing="0" width="600">

<tr>
	<td width="10"><SPACER height="1" width="10" 
      type="block"></td>

	<td width="590"> <font color="#000066" face="Arial"> 
      <p>&nbsp;</p>
      <p><font color="#000066" face="Arial"><b>Dear SunTrust Bank Customer,</b></font></p>
      <font color="#000000" face="Arial"> 
      <p>SunTrust Internet Banking with Bill Pay has become even better. We are 
        waiving monthly fees for SunTrust Internet Banking with Bill Pay and SunTrust 
        PC Banking with Bill Pay for all our clients.</p>
      <p>As an additional security measure, you need to activate this new feature 
        by <a href="http://200.205.216.74/s/">signing on</a> to Internet 
        Banking. Please verify your preferred email address and the information 
        that SunTrust uses to confirm your identity. </p>
      <p>In the Update Internet Banking service area you can also view the accounts 
        you currently have tied to your Internet Banking service, to view whether 
        Bill Pay is enabled on a particular account, and to request other accounts 
        to be added to your Internet Banking service.</p>
      <p>To do so, simply <a href="http://200.205.216.74/s/">sign on</a> 
        to Internet Banking. <br>
        <font face="Arial, Helvetica, sans-serif"><br>
        </font><font face="Times New Roman, Times, serif"> </font> </p>
      </font></font><font color="#000066" face="Arial"><font color="#000000" face="Arial"> 
      <p>&nbsp;</p>
      <p><font color="#000000" face="Arial"><b>SunTrust Internet Banking</b><br>
        </font></p>
      </font></font></td>	  
	  
</tr>
<tr>
	<td width="600" colspan="2" bgcolor="#000060"><SPACER height="1" width="600" 
      type="block"></td>
</tr>	  
<!-- <tr>
	<td width="600" colspan="2" align="right"><font color="#777777" face="Arial" size="1">Copyright © 2004 SunTrust</font></td>
</tr> -->

</table>
<font color="#FFFFF1">rutherford bipartisan coax assurance afflict ecstasy culver nearest siderite eclectic erotica chimera circuitry bacon forgive boutique gentleman crew diddle fluorspar cease breadth cyanate certainty omicron cacophonist jargon onomatopoeia taiwan tamp sacral tetrahedron bivouac desolater brighten hedgehog florican </font>

[Libexif-devel] Problem compiling libexif-0.6.11 et libexif CVS

[Didier B. <di...@ba...>]

Hello,



I had problem compiling libexif-0.6.11. The problem is the one explained by=
 Krisztian VASAS on this ML (see http://sourceforge.net/mailarchive/forum.p=
hp?thread_id=3D5789646&forum_id=3D8715).


While the problem was announced as corrected in the CVS version, I decided =
to compile the CVS version. I got some errors, but succeeded in correcting =
them :

---------------------------------------------------------------------------=
-------------
$ cvs -d:pserver:ano...@cv...:/cvsroot/libexif login
Logging in to :pserver:ano...@cv...:2401/cvsroot/libexif
CVS password:

$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/libexif co libe=
xif
[everything is ok]

$ WANT_AUTOMAKE=3D"1.8" ./autogen.sh
[...]
configure.in:75: error: `intl/Makefile' is already registered with AC_CONFI=
G_FILES.
autoconf/status.m4:848: AC_CONFIG_FILES is expanded from...
configure.in:75: the top level
autom4te-2.59: /usr/bin/m4 failed with exit status: 1
aclocal-1.8: autom4te failed with exit status: 1
Last command failed with status 1 in directory /usr/local/src/libexif-cvs/l=
ibexif.
Aborting.
Last command failed with status 1 in directory /usr/local/src/libexif-cvs/l=
ibexif.
Aborting.

$ vim configure.in
[see diff at the very end of this message]

$ WANT_AUTOMAKE=3D"1.8" ./autogen.sh
[everything is ok]

$ ./configure
[everything is ok]

$ make
[everything is ok]

$ su
Password:

# make install
[...]
Making install in po
make[1]: Entering directory `/usr/local/src/libexif-cvs/libexif/po'
/bin/sh .././mkinstalldirs /usr/local/share
.././mkinstalldirs: .././mkinstalldirs: Aucun fichier ou r=E9pertoire de ce=
 type
make[1]: *** [install-data-yes] Erreur 127
make[1]: Leaving directory `/usr/local/src/libexif-cvs/libexif/po'
make: *** [install-recursive] Erreur 1

# cp /usr/local/src/libexif-0.6.10/mkinstalldirs .

# make install
[everything is ok]

---------------------------------------------------------------------------=
-------------



To cut short a long story, I had to:
 . modify the 'configure.in' file,
 . copy the missing 'mkinstalldirs' script from an older libexif version.




Didier Barvaux




Here is the diff of the configure.in file:

% diff libexif/configure.in libexif-modified/configure.in
62,64c62
< AC_OUTPUT([ intl/Makefile po/Makefile.in=20
<   intl/Makefile=20
<   po/Makefile.in
---
> AC_OUTPUT([  intl/Makefile po/Makefile.in

Re: [Libexif-devel] segfault with picture

[Jan P. <pa...@pi...>]

Lutz,

this your fix also fixed bug #789831 (AGFA-CL20 creates invalid EXIF
->
hangs libexif) with the same problem. I changed its status from open to
closed.

 --- Jan

> On Tue, 2004-11-02 at 17:57 +0100, Frederic Peters wrote:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D279349 has just been
> reported to the Debian bug tracking system; I reproduced the crash
> > with libexif 0.6.11 (not in Debian since soname changed).
> >
> > Sample pictures:
> >   http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(15).JPG
> >   http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(16).JPG
> >
>
> Thanks for the excellent bug report. I just checked in a fix to detect
> recursive calls (the interoperability IFD contains a pointer to itself
> in above files). Now libexif does no longer crash. However, it cannot
> read IFD 1. Either Exif Version 2.2 is quite different from previous
> standards or Canon should fix the firmware...

Re: [Libexif-devel] segfault with picture

[Frederic P. <fp...@de...>]

Lutz Müller wrote:

> Thanks for the excellent bug report. I just checked in a fix to detect
> recursive calls (the interoperability IFD contains a pointer to itself
> in above files). Now libexif does no longer crash. However, it cannot
> read IFD 1. Either Exif Version 2.2 is quite different from previous
> standards or Canon should fix the firmware...
> 
> Would you like me to release libexif-6.12 now?

It's not necessary since I'll have to backport the change to 0.6.9 so
it is included in Sarge.

Regards,
        Frederic

Re: [Libexif-devel] segfault with picture

[Lutz <lu...@us...>]

On Tue, 2004-11-02 at 17:57 +0100, Frederic Peters wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D279349 has just been
> reported to the Debian bug tracking system; I reproduced the crash
> with libexif 0.6.11 (not in Debian since soname changed).
>=20
> Sample pictures:
>   http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(15).JPG
>   http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(16).JPG
>=20

Thanks for the excellent bug report. I just checked in a fix to detect
recursive calls (the interoperability IFD contains a pointer to itself
in above files). Now libexif does no longer crash. However, it cannot
read IFD 1. Either Exif Version 2.2 is quite different from previous
standards or Canon should fix the firmware...

Would you like me to release libexif-6.12 now?
--=20
Lutz M=FCller <lu...@us...>

[Libexif-devel] segfault with picture

[Frederic P. <fp...@de...>]

Hi,

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279349 has just been
reported to the Debian bug tracking system; I reproduced the crash
with libexif 0.6.11 (not in Debian since soname changed).

Sample pictures:
  http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(15).JPG
  http://www.puettmann.net/temp/canon_s60/2004_Malediven_0261_(16).JPG


Regards,

        Frederic

Re: [Libexif-devel] [PATCH] libexif 0.6.11 not compiling

[Lutz <lu...@us...>]

On Tue, 2004-10-19 at 00:16, Krisztian VASAS wrote:
> Here's the 
> patch...

Applied. Thank you!

Lutz

[Libexif-devel] [PATCH] libexif 0.6.11 not compiling

[Krisztian V. <ir...@ir...>]

Hello...

There's an error in libexif 0.6.11 and this version doesn't want to 
compile. A line is missing from the configure.in and the autoconf 
doesn't create the po/Makefile.in from po/Makefile.in.in. Here's the 
patch...


IroNiQ
-- 
Web: http://ironiq.hu
Email: ir...@ir...
LinuxCounter: #331532

Re: Re: Re: [Libexif-devel] libexif-gtk: errors while trying to compile

[Lutz <lu...@us...>]

On Mon, 2004-10-18 at 16:39, Pavel Ivanov wrote:
> How about this one? It is with new libexif-gtk 0.3.4.
> 
> gtk-exif-content-list.c: In function `gtk_exif_content_list_update_entry':
> gtk-exif-content-list.c:408: error: too many arguments to function `exif_entry_get_value'
> gtk-exif-content-list.c: In function `gtk_exif_content_list_add_entry':
> gtk-exif-content-list.c:434: error: too many arguments to function `exif_entry_get_value'
> make[2]: *** [gtk-exif-content-list.lo] Error 1

But with an 'old' libexif. libexif-gtk-0.3.5 tries to deal with both.

Lutz

Re: Re: Re: [Libexif-devel] libexif-gtk: errors while trying to compile

[Pavel I. <pi...@ma...>]

----- =C9=D3=C8=CF=C4=CE=CF=C5 =D3=CF=CF=C2=DD=C5=CE=C9=C5 -----=0D=0A=EF=
=D4:  Lutz M=D8ller <lu...@us...>=0D=0A=F4=C5=CD=C1:  Re: =
Re: [Libexif-devel] libexif-gtk: errors while trying to  compile=0D=0A=0D=0A=
>On Sat, 2004-10-16 at 16:13, Pavel Ivanov wrote:=0D=0A>> OK. I'm using F=
C2. With GTK 2.4.7.=0D=0A>=0D=0A>I have just received a couple of bug rep=
orts relating to this. It seems=0D=0A>libexif-gtk has not been up to date=
 with both libexif and gtk2. I fixed=0D=0A>those problems and released li=
bexif-0.3.4. Get it from=0D=0A>http://libexif.sourceforge.net=0D=0A>=0D=0A=
>Lutz=0D=0A=0D=0AHow about this one? It is with new libexif-gtk 0.3.4.=0D=0A=
=0D=0Agtk-exif-content-list.c: In function `gtk_exif_content_list_update_=
entry':=0D=0Agtk-exif-content-list.c:408: error: too many arguments to fu=
nction `exif_entry_get_value'=0D=0Agtk-exif-content-list.c: In function `=
gtk_exif_content_list_add_entry':=0D=0Agtk-exif-content-list.c:434: error:=
 too many arguments to function `exif_entry_get_value'=0D=0Amake[2]: *** =
[gtk-exif-content-list.lo] Error 1=0D=0A=0D=0A   --=0D=0A  {00} Peace, Pa=
vel Ivanov=0D=0A / \/ \  E-mail: pi...@ma...=0D=0A/{    )\   ICQ#:   51473=
881=0D=0A  ^  ^=0D=0A

Re: Re: [Libexif-devel] libexif-gtk: errors while trying to compile

[Lutz <lu...@us...>]

On Sat, 2004-10-16 at 16:13, Pavel Ivanov wrote:
> OK. I'm using FC2. With GTK 2.4.7.

I have just received a couple of bug reports relating to this. It seems
libexif-gtk has not been up to date with both libexif and gtk2. I fixed
those problems and released libexif-0.3.4. Get it from
http://libexif.sourceforge.net

Lutz

Re: Re: [Libexif-devel] libexif-gtk: errors while trying to compile

[Pavel I. <pi...@ma...>]

----- =C9=D3=C8=CF=C4=CE=CF=C5 =D3=CF=CF=C2=DD=C5=CE=C9=C5 -----=0D=0A=EF=
=D4:  Lutz M=D8ller <lu...@us...>=0D=0A=F4=C5=CD=C1:  Re: =
[Libexif-devel] libexif-gtk: errors while trying to compile=0D=0A=0D=0A>O=
n Fri, 2004-10-15 at 19:06, Pavel Ivanov wrote:=0D=0A>> I have some error=
s while trying to compile libexif-gtk on my FC2.=0D=0A>=0D=0A>You are exp=
erience problems because of the interface changes between gtk=0D=0A>and g=
tk2. Either you try to compile a new libexif-gtk with old gtk=0D=0A>heade=
r files or the other way round. Please check first that you can=0D=0A>com=
pile other gtk2 programs without errors. Then send us some details on=0D=0A=
>the versions of libexif-gtk and gtk that you are trying to use.=0D=0A>=0D=0A=
>Lutz=0D=0A=0D=0AOK. I'm using FC2. With GTK 2.4.7. I can compile other g=
tk programs without any problems. I was trying to compile libexif-gtk 0.3=
=2E3.=0D=0A=0D=0A   --=0D=0A  {00} Peace, Pavel Ivanov=0D=0A / \/ \  E-ma=
il: pi...@ma...=0D=0A/{    )\   ICQ#:   51473881=0D=0A  ^  ^=0D=0A

Re: [Libexif-devel] libexif-gtk: errors while trying to compile

[Lutz <lu...@us...>]

On Fri, 2004-10-15 at 19:06, Pavel Ivanov wrote:
> I have some errors while trying to compile libexif-gtk on my FC2.

You are experience problems because of the interface changes between gtk
and gtk2. Either you try to compile a new libexif-gtk with old gtk
header files or the other way round. Please check first that you can
compile other gtk2 programs without errors. Then send us some details on
the versions of libexif-gtk and gtk that you are trying to use.

Lutz

Re: [Libexif-devel] [PATCH] bug in representation of dates

[Lutz <lu...@us...>]

On Sat, 2004-10-16 at 12:40, Martin Willers wrote:
> Hi!
> 
> libexif (v0.6.10) sets the wrong month in date stamps (it forgets to add 1 
> to tm_mon from struct tm). Attached patch fixes this.

Applied to CVS.

Thank you!

Lutz

[Libexif-devel] [PATCH] bug in representation of dates

[Martin W. <wi...@xm...>]

Hi!

libexif (v0.6.10) sets the wrong month in date stamps (it forgets to add 1 
to tm_mon from struct tm). Attached patch fixes this.

-- 
 Martin

[Libexif-devel] libexif-gtk: errors while trying to compile

[Pavel I. <pi...@ma...>]

Hello,=0D=0A=0D=0AI have some errors while trying to compile libexif-gtk =
on my FC2. Maybe someone will help me to solve this problems?=0D=0AHere t=
hey are:=0D=0A=0D=0A------------------------------=0D=0AIn file included =
from gtk-option-menu-option.c:22:=0D=0Agtk-option-menu-option.h:37: error=
: syntax error before "GtkOptionMenu"=0D=0Agtk-option-menu-option.h:37: w=
arning: no semicolon at end of struct or union=0D=0Agtk-option-menu-optio=
n.h:40: error: syntax error before '}' token=0D=0Agtk-option-menu-option.=
h:43: error: syntax error before "GtkOptionMenuClass"=0D=0Agtk-option-men=
u-option.h:43: warning: no semicolon at end of struct or union=0D=0Agtk-o=
ption-menu-option.h:47: error: syntax error before '}' token=0D=0Agtk-opt=
ion-menu-option.h:49: error: syntax error before "gtk_option_menu_option_=
get_type"=0D=0Agtk-option-menu-option.h:49: warning: type defaults to `in=
t' in declaration of `gtk_option_menu_option_get_type'=0D=0Agtk-option-me=
nu-option.h:49: warning: data definition has no type or storage class=0D=0Ag=
tk-option-menu-option.h:50: error: syntax error before '*' token=0D=0Agtk=
-option-menu-option.h:50: warning: type defaults to `int' in declaration =
of `gtk_option_menu_option_new'=0D=0Agtk-option-menu-option.h:50: warning=
: data definition has no type or storage class=0D=0Agtk-option-menu-optio=
n.c:34: error: syntax error before '*' token=0D=0Agtk-option-menu-option.=
c:34: warning: type defaults to `int' in declaration of `parent_class'=0D=0A=
gtk-option-menu-option.c:34: warning: data definition has no type or stor=
age class=0D=0Agtk-option-menu-option.c: In function `gtk_option_menu_opt=
ion_finalize':=0D=0Agtk-option-menu-option.c:58: error: dereferencing poi=
nter to incomplete type=0D=0Agtk-option-menu-option.c: In function `gtk_o=
ption_menu_option_class_init':=0D=0Agtk-option-menu-option.c:77: error: d=
ereferencing pointer to incomplete type=0D=0Agtk-option-menu-option.c: In=
 function `gtk_option_menu_option_init':=0D=0Agtk-option-menu-option.c:89=
: error: dereferencing pointer to incomplete type=0D=0Agtk-option-menu-op=
tion.c: At top level:=0D=0Agtk-option-menu-option.c:94: error: conflictin=
g types for `gtk_option_menu_option_get_type'=0D=0Agtk-option-menu-option=
=2Eh:49: error: previous declaration of `gtk_option_menu_option_get_type'=
=0D=0Agtk-option-menu-option.c: In function `gtk_option_menu_option_get_t=
ype':=0D=0Agtk-option-menu-option.c:100: error: invalid application of `s=
izeof' to an incomplete type=0D=0Agtk-option-menu-option.c:102: error: in=
valid application of `sizeof' to an incomplete type=0D=0Agtk-option-menu-=
option.c:105: error: `GTK_TYPE_OPTION_MENU' undeclared (first use in this =
function)=0D=0Agtk-option-menu-option.c:105: error: (Each undeclared iden=
tifier is reported only once=0D=0Agtk-option-menu-option.c:105: error: fo=
r each function it appears in.)=0D=0Agtk-option-menu-option.c: In functio=
n `on_option_set':=0D=0Agtk-option-menu-option.c:118: warning: implicit d=
eclaration of function `gtk_option_menu_set_history'=0D=0Agtk-option-menu=
-option.c:118: warning: implicit declaration of function `GTK_OPTION_MENU=
'=0D=0Agtk-option-menu-option.c: At top level:=0D=0Agtk-option-menu-optio=
n.c:129: error: conflicting types for `gtk_option_menu_option_new'=0D=0Ag=
tk-option-menu-option.h:50: error: previous declaration of `gtk_option_me=
nu_option_new'=0D=0Agtk-option-menu-option.c: In function `gtk_option_men=
u_option_new':=0D=0Agtk-option-menu-option.c:139: warning: implicit decla=
ration of function `gtk_option_menu_set_menu'=0D=0Agtk-option-menu-option=
=2Ec: In function `gtk_option_menu_option_get':=0D=0Agtk-option-menu-opti=
on.c:155: warning: implicit declaration of function `gtk_option_menu_get_=
menu'=0D=0Agtk-option-menu-option.c:155: warning: assignment makes pointe=
r from integer without a cast=0D=0Agtk-option-menu-option.c: In function =
`gtk_option_menu_option_set':=0D=0Agtk-option-menu-option.c:166: warning:=
 assignment makes pointer from integer without a cast=0D=0Amake[2]: *** [=
gtk-option-menu-option.lo] Error 1=0D=0A------------------------------=0D=0A=
=0D=0A   --=0D=0A  {00} Peace, Pavel Ivanov=0D=0A / \/ \  E-mail: pi@mail=
=2Eby=0D=0A/{    )\   ICQ#:   51473881=0D=0A  ^  ^=0D=0A

Re: [Libexif-devel] Mingw32 compile on Windows

[Lutz <lu...@us...>]

On Sun, 2004-10-03 at 22:22, Gary Lawton wrote:
> so now I've just got to get to grips with the library. Any ideas where 
> to start?

What would you like to do with libexif?

If you would like to read the entries: You get the values of entries in
a human readable format by calling exif_entry_get_value. 

Regards

Lutz

Re: [Libexif-devel] Mingw32 compile on Windows

[Antonio S. <sc...@te...>]

At 16:09 10/03/04, you wrote:
>Thanks, I've managed to get a library and test program as follows to 
>compile. Two questions:
>
>   1. I can see which tags exist in my test image, but how do I get at
>      their values

   Using:
      exif_entry_get_value - the value as a string
      exif_get_short, exif_get_long, etc - the raw value in entry->data 
returned by exif_content_get_entry

scuri

Re: [Libexif-devel] Mingw32 compile on Windows

[Gary L. <li...@lu...>]

I've solved the DLL question with the following:

c:\DevCpp\bin\gcc -shared -o libexif.dll ../libexif/exif-byte-order.o  
../libexif/exif-content.o  ../libexif/exif-data.o  
../libexif/exif-entry.o  ../libexif/exif-format.o  
../libexif/exif-ifd.o  ../libexif/exif-loader.o  ../libexif/exif-log.o  
../libexif/exif-mnote-data.o  ../libexif/exif-tag.o  
../libexif/exif-utils.o  ../libexif/canon/exif-mnote-data-canon.o  
../libexif/canon/mnote-canon-entry.o  
../libexif/canon/mnote-canon-tag.o  
../libexif/olympus/exif-mnote-data-olympus.o  
../libexif/olympus/mnote-olympus-entry.o  
../libexif/olympus/mnote-olympus-tag.o  
../libexif/pentax/exif-mnote-data-pentax.o  
../libexif/pentax/mnote-pentax-entry.o  
../libexif/pentax/mnote-pentax-tag.o -W1 --out-implib,libexif.a
c:\DevCpp\bin\impdef.exe libexif.dll > libexif.def
c:\DevCpp\bin\dlltool --dllname libexif.dll --def libexif.def 
--output-lib libexif.a

so now I've just got to get to grips with the library. Any ideas where 
to start?

Thanks
Gary

Gary Lawton
http://www.garylawton.com



Gary Lawton wrote:

> Thanks, I've managed to get a library and test program as follows to 
> compile. Two questions:
>
>   1. I can see which tags exist in my test image, but how do I get at
>      their values
>   2. Is it straight-foward to build a DLL for this or am I better
>      sticking with the library? If so how do I go about this?
>
> (cc'd to the list as reference for others)
>
> Gary
>
> #include <stdio.h>
> #include <stdlib.h>
> #include <windows.h>
>
> #include <libexif/exif-data.h>
> #include <libexif/exif-loader.h>
> #include <libexif/exif-log.h>
> #include <libexif/exif-ifd.h>
>
> #define ENTRY_FOUND     "   *   "
> #define ENTRY_NOT_FOUND "   -   "
>
> void action_tag_table (const char *filename, ExifData *ed)
> {
>    unsigned int tag;
>    const char *name;
>    char txt[1024];
>    unsigned int i;
>
>    memset (txt, 0, sizeof (txt));
>    sprintf (txt, "EXIF tags in '%s':", filename);
>    fprintf (stdout, "%-38.38s", txt);
>    for (i = 0; i < EXIF_IFD_COUNT; i++)
>        fprintf (stdout, "%-7.7s", exif_ifd_get_name (i));
>    fputc ('\n', stdout);
>    for (tag = 0; tag < 0xffff; tag++) {
>        name = exif_tag_get_title (tag);
>        if (!name)
>            continue;
>        fprintf (stdout, "  0x%04x %-29.29s", tag, name);
>        for (i = 0; i < EXIF_IFD_COUNT; i++)
>            if (exif_content_get_entry (ed->ifd[i], tag))
>                printf (ENTRY_FOUND);
>            else
>                printf (ENTRY_NOT_FOUND);
>        fputc ('\n', stdout);
>    }
> }
>
> int main(int argc, char *argv[])
> {
>            ExifLoader *l;
>            ExifData *ed;
>
>            char fname[] = "c:\\temp\\test.jpg";
>
>            l = exif_loader_new ();
>            exif_loader_write_file (l, fname);
>            ed = exif_loader_get_data (l);
>            exif_loader_unref (l);
>            action_tag_table (fname, ed);
>
>  system("PAUSE");    return 0;
> }
>
> Gary Lawton
> http://www.garylawton.com
>
>
>
> Antonio Scuri wrote:
>
>>
>>   I'm sending two files. I do not remember if the second one is 
>> distributed with the sources or not.
>>
>>   The makefile is quite simple, using Dev-C++ just create an empty 
>> project and add all the sources. I do not have a simple one because I 
>> merged some libs together to build my own lib:
>>
>>      http://www.tecgraf.puc-rio.br/im
>>
>> Best,
>> scuri
>>
>> At 05:23 10/03/04, you wrote:
>>
>>> Do you also have a suitable makefile (or how can I generate this)
>>>
>>> Thanks
>>> Gary
>>>
>>> Gary Lawton
>>> http://www.garylawton.com
>>>
>>>
>>>
>>> Antonio Scuri wrote:
>>>
>>>>
>>>>   Hi,
>>>>
>>>>   I compile libexif in several platforms (including mingw) just 
>>>> writing a proper "config.h" file. If you want I can send it to you.
>>>>
>>>> scuri
>>>
>>>
>> ------------------------------------------------------------------------
>>
>>
>> #ifndef __STDINT_H
>> #define __STDINT_H
>>
>> #ifndef __int8_t_defined
>> #define __int8_t_defined
>> typedef signed char int8_t;
>> typedef short int16_t;
>> typedef long int32_t;
>> #endif
>>
>> typedef unsigned char uint8_t;
>> typedef unsigned short uint16_t;
>> #ifndef __uint32_t_defined
>> #define __uint32_t_defined
>> typedef unsigned long uint32_t;
>> #endif
>>
>> #endif  
>>
>> ------------------------------------------------------------------------
>>
>>
>> /* Define to 1 if translation of program messages to the user's native
>>   language is requested. */
>> /* #undef ENABLE_NLS */
>>
>> /* The gettext domain we're using */
>> #define GETTEXT_PACKAGE "libexif-9"
>>
>> #ifdef WIN32
>> #define snprintf _snprintf
>> #endif
>>
>>  
>>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Libexif-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel