Re: [Mingw-cross-env-list] x86_64-w64-mingw32.shared => exiv2

[Jos De Laender]

Hi Tony,

Thanks for the answer.

Meanwhile I spent a little bit more time to understand your mxe build 
system, but I stay only an user of it, not a developper for it.

I found out that indeed it's in the first place a matter of enabling. 
See my exiv2.mk in attachment. Did I do this according to your intentions ?

But then, it still didn't create the dll and I applied a patch that I 
needed to apply also when I still was trying to compile under windows 
with mingw. See attached as well. I agree it qualifies for 
quick-and-dirty and that spending some time to have this right makes sense.
Only , I'm not familiar with that matter at all, so I can't really help.

Many thanks for the great work !

Jos



Tony Theodore schreef op 10/06/2014 13:30:
> On 10 Jun 2014, at 00:28, Jos De Laender <address@hidden> wrote:
>
> > Can someone give me some help with respect to exiv2 with the target as in 
> > subject.
> >
> > Many, many packages compile fine under it (including graphicsmagick and qt) but 
> > it fails on a (relative) simple one as exiv2.
> >
> > It seems just nothing is generated ([nobuild]).
> >
> > Does someone know what's going on and/or how I can assist in trying to find the 
> > issue ?
> Shared builds are still very much a work-in-progress, roughly half[1] the packages haven’t had 
> their shared builds enabled yet. Sometimes it’s a simple matter of replacing 
> "build,host,prefix,[en|dis]able-[static|shared]" with "$(MXE_CONFIGURE_OPTS)” 
> (e.g. src/expat.mk), but it really depends on the build system. exiv2 requires a workaround 
> for libtool’s detection of shared libs:
>
> https://github.com/mxe/mxe/commit/f4202755f56e4062d64fce3c731e0db4c2c695ff
>
> which isn’t ideal and we don’t want to enable many more like that without some 
> greater understanding and cleaner solutions. There are a few open tickets (375, 
> 393, 408) relating to shared builds, if you have some input on those or general 
> knowledge about the intricacies of shared builds (declspec header macros, 
> pkg-config files, libtool setup, linker options, autotools install locations 
> ...), it would be very helpful. Maybe a wiki page to consolidate all this 
> before adding it to the docs?
>
> Cheers,
>
> Tony
>
> [1] 
> http://htmlpreview.github.io/?https://raw.github.com/mxe/mxe/master/index.html

exiv2.mk
Description: Text document

exiv2-2-configure.patch
Description: Text document