[liblouis-liblouisxml] AW: Re: LoadLibrary and ABI
- From: "Bijewitz, Volker" <v.bijewitz@xxxxxxx>
- To: <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Mon, 29 Jun 2009 13:02:04 +0200
Hi all,
I am using LibLouis.dll in a "side-by-side"-szenario. I put the lib inside my
application directory, so I am shure that I load allways the right library.
So, for me there are no benefits putting a version suffix to the liblouis
name. It would be really good to have a version information in the resources
like it is the standard way in windows. I have a routine that collects the
version strings of all libs in my app directory that works with that
resources.
I think, if there are users that install LibLouis as a real shared library in
common places, appending a version suffix to the lib name is the best way to
avoid "DLL hell". I do not want to use LibLouis from a common place, because
I like more to have the full control over all modules I use, and dont care
about some kilobytes more installing on a users system. And it is a risk to
put the lib into shared places, because then the app can be broken by a
incorrect implemented 3d party uninstaller that does not use the shared files
counter the right way or a installer that overwrites the files with older
versions...
After all, I think it is a good idea to put a version suffix to the name.
Greetings,
Volker Bijewitz
> -----Ursprüngliche Nachricht-----
> Von: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Im Auftrag
> von James Teh
> Gesendet: Freitag, 26. Juni 2009 02:22
> An: liblouis-liblouisxml@xxxxxxxxxxxxx
> Betreff: [liblouis-liblouisxml] Re: LoadLibrary and ABI
>
> In Windows, we currently build liblouis as just liblouis.dll.
> However, with this patch, maybe we can go back to
> liblouis-x.dll; we may not even need the Unix/Windows
> conditional, as I assume LIBLOUIS_SONAME will resolve to
> liblouis-x.dll on Windows.
>
> Thoughts from other Windows users? Appending the version
> suffix is still generally non-standard on Windows, but this
> would help to solve the ABI change problem.
>
> Jamie
>
> On 26/06/2009 10:10 AM, Samuel Thibault wrote:
> > Hello,
> >
> > The python bindings of liblouis uses LoadLibrary then
> ctypes to access
> > liblouis' functions. However, this does not handle the case
> when the
> > library ABI changes (e.g. if length parameters were turned into
> > size_t) and both new versions of the library and old
> versions of the
> > library co-exist. Also, some systems do not use the .so
> extension, but
> > .dylib, etc. The attached subversion patch extracts the
> precise name
> > of the library that the python bindings was built with, to
> make sure
> > to load the correct file. It assumes that you have run
> >
> > svn mv __init__.py __init__.py.in
> >
> > Samuel
>
> --
> James Teh
> Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx Web site:
> http://www.jantrid.net/ For a description of the software and
> to download it go to http://www.jjb-software.com
>
>
For a description of the software and to download it go to
http://www.jjb-software.com
Other related posts:
- » [liblouis-liblouisxml] AW: Re: LoadLibrary and ABI - Bijewitz, Volker
