l.
Older versions of MinGW have a .la file with an empty library_names, and
that works fine.
In the end, I had to downgrade MinGW anyway (for compatibility reasons),
so my immediate problem is solved, and I understand libtool a little bit
better, though still not as well as I'd like.
DES
-
Bob Friesenhahn writes:
> Dag-Erling Smørgrav writes:
> > I never said I had trouble linking with libjpeg. I said I could not
> > *build* libjpeg using the workaround I found floating around on the net,
> > which convinced me that the workaround is wrong.
> I am t
Dag-Erling Smørgrav writes:
> I still wish someone would answer the questions I asked...
I should amend that - Bob did answer one of them, plus another I hadn't
asked because I didn't know it needed asking, and for that I'm grateful
to him. I still need help with the other t
Vincent Torri writes:
> Dag-Erling Smørgrav writes:
> > Bob Friesenhahn writes:
> > > You did not mention the version of libtool you are using.
> > 2.2.7a, that's what currently ships with MinGW.
> 2.2.7a ? a git version ?
Yep. I must admit I didn't pay
der MinGW and have
> not noticed any problems linking with it.
I never said I had trouble linking with libjpeg. I said I could not
*build* libjpeg using the workaround I found floating around on the net,
which convinced me that the workaround is wrong.
DES
--
Dag-Er
ce must be incorrect. This hypothesis was strengthened when I found
that jpeg7 won't link with this hack (not as in "libtool fails to link
programs that use libjpeg", but as in: libtool fails to link libjpeg")
Fifth question: can someone give a concise e
