Another question pops up, though: what is the difference between these catgets libraries and the ones found in libgw32c (from gnuwin32)? I was trying to work with the latter but if the former can compile with MS Visual C then this option would be OK too.
Paul.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Another question pops up, though: what is the difference between
> these catgets libraries and the ones found in libgw32c?
I was unsuccessful in locating a catgets implementation, which would work successfully on native Woe32; the GNU implementation carried too much ancillary baggage, which I didn't have the energy to port, and I couldn't find a complete and consistent source package for the BSD implementation, (and what I did find was borderline incomprehensible), so I wrote my own implementation from scratch.
Every catgets implementation will define its own unique binary format for message catalogues; the GnuWin32 catgets is unlikely to grok the format of catalogues generated by my gencat.exe.
> if [these] can compile with MS Visual C then this option would be OK too.
Bill's crapware doesn't work too well as a cross-compiler, hosted on GNU/Linux, so I've never used it. My bin and dev packages have been built with the MinGW port of GCC, but you should be able to use the pre-built DLL with MSVC; consult http://www.mingw.org/MinGWiki/index.php/MSVC-MinGW-DLL for guidance. Alternatively, you could adapt my sources to build with MSVC -- do remember that I publish the package under GPLv2.
Regards,
Keith.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I should also have mentioned that I've included both static and dynamic variations of the catgets library; if you rename libcatgets.a, (not libcatgets.dll.a -- that's just an import library to facilitate GCC linking to the DLL), to catgets.lib, then AFAIK, that should link statically OOTB with MSVC compiled code.
Regards,
Keith.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can I find gencat.exe somewhere? I tried to compile it from libgw32c source library but was unsuccessful.
Thank you,
Paul.
Curiously, I recently posted one here:
https://sourceforge.net/project/showfiles.php?group_id=2435&package_id=11988
You also need the compatible catgets development libraries, from the same place, since the binary message catalogue format is implementation specific.
HTH,
Keith.
Thanks for your help.
Another question pops up, though: what is the difference between these catgets libraries and the ones found in libgw32c (from gnuwin32)? I was trying to work with the latter but if the former can compile with MS Visual C then this option would be OK too.
Paul.
> Another question pops up, though: what is the difference between
> these catgets libraries and the ones found in libgw32c?
I was unsuccessful in locating a catgets implementation, which would work successfully on native Woe32; the GNU implementation carried too much ancillary baggage, which I didn't have the energy to port, and I couldn't find a complete and consistent source package for the BSD implementation, (and what I did find was borderline incomprehensible), so I wrote my own implementation from scratch.
Every catgets implementation will define its own unique binary format for message catalogues; the GnuWin32 catgets is unlikely to grok the format of catalogues generated by my gencat.exe.
> if [these] can compile with MS Visual C then this option would be OK too.
Bill's crapware doesn't work too well as a cross-compiler, hosted on GNU/Linux, so I've never used it. My bin and dev packages have been built with the MinGW port of GCC, but you should be able to use the pre-built DLL with MSVC; consult http://www.mingw.org/MinGWiki/index.php/MSVC-MinGW-DLL for guidance. Alternatively, you could adapt my sources to build with MSVC -- do remember that I publish the package under GPLv2.
Regards,
Keith.
I should also have mentioned that I've included both static and dynamic variations of the catgets library; if you rename libcatgets.a, (not libcatgets.dll.a -- that's just an import library to facilitate GCC linking to the DLL), to catgets.lib, then AFAIK, that should link statically OOTB with MSVC compiled code.
Regards,
Keith.