I'm working on getting libthai together with win32 Strawberry Perl, and there's a problem I'd like to ask how to address best.
The problem is that the Strawberry installation can be put in any path, and this conflicts with libthai looking for thbrk.tri in a path determined during the build (not counting the LIBTHAI_DICTDIR). I wonder if you will be willing to discuss ways to adapt libthai so its binaries could be also installed in arbitrary paths?
A crude temporary hack I made specifically for libthai win32 portable install that I roll out, is to use win32-specific ways to find out the install path of libthai.dll, f ex c:/usr/bin, and install thbrk.tri there as well. This won't work for static builds, and I'm also not proud of installing a non-executable file in $PREFIX/bin, so I'm not proposing this fix as a patch.
I would ideally see a solution as to embed either the .tri file or its memory dump in an .o so it will be loaded automatically as either .dll or .a file. I can work out a fork project if this gets your blessing. Anyway if you have interest in this let's discuss.
Hello,
I'm working on getting libthai together with win32 Strawberry Perl, and there's a problem I'd like to ask how to address best. The problem is that the Strawberry installation can be put in any path, and this conflicts with libthai looking for thbrk.tri in a path determined during the build (not counting the LIBTHAI_DICTDIR). I wonder if you will be willing to discuss ways to adapt libthai so its binaries could be also installed in arbitrary paths?
A crude temporary hack I made specifically for libthai win32 portable install that I roll out, is to use win32-specific ways to find out the install path of libthai.dll, f ex c:/usr/bin, and install thbrk.tri there as well. This won't work for static builds, and I'm also not proud of installing a non-executable file in $PREFIX/bin, so I'm not proposing this fix as a patch.
I would ideally see a solution as to embed either the .tri file or its memory dump in an .o so it will be loaded automatically as either .dll or .a file. I can work out a fork project if this gets your blessing. Anyway if you have interest in this let's discuss.
Regards Dmitry