Charles Wilson wrote:
Corinna Vinschen wrote:
If only these two tools are using cyggettext*.dll and the other one,
why not linking statically against them? I don't see a reason to
have dlls hanging around for that purpose.
No, you got it backwards. There are only two programs --
FYI, the new gettext package is NOT imminent. There are some variables
exported from cyggettext*.dll to the msg*.exe programs that are not
auto-importable. (direct access to elements in an array of structs).
So, I need to muck with the code some -- and add accessor functions or
something.
On Tue, Jun 18, 2002 at 02:25:59PM -0400, Charles Wilson wrote:
FYI, the new gettext package is NOT imminent. There are some variables
exported from cyggettext*.dll to the msg*.exe programs that are not
auto-importable. (direct access to elements in an array of structs).
So, I need to
Corinna Vinschen wrote:
If only these two tools are using cyggettext*.dll and the other one,
why not linking statically against them? I don't see a reason to
have dlls hanging around for that purpose.
No, you got it backwards. There are only two programs -- the two MAIN
programs
Nicholas Wourms wrote:
Is xgettext.exe included or has that been phased out?
xgettext.exe is considered one of the development oriented tools, not
end user tools. So it's in the gettext-tools package (which I'm
calling gettext-devel).
--Chuck
Gerrit P. Haase wrote:
:-) Great. Well, I don't like the part about 'whining', but all the
rest is great.
Ok. I'll take the two packages if no one steps on my toes now...
Cool. I didn't mean that you, in particular, *must* take these two
packages or I won't do libiconv. It's just
