Re: [Tuxmath-devel] po/ conflicts

[David B. <dav...@gm...>]

Hi Bill and John,

> FYI Tux Paint doesnt include libintl stuff in its codebase.
> We do have our own (patched?) builds of same for Windows, IIRC.
>
> John P might be able to explain our situation. Cc'ing.
>

We won't need the internal libintl directory for the Windows
crossbuild once the remaining snags for the mingw-cross-env based
build are worked out.

I would indeed like to get John's native Windows environment set up,
or at least have someone in our project set it up.  However, I don't
have windows at home, and I don't really have full control of my win32
box at work - or at any rate I'm not supposed to have full control of
it ;)

There are some places where tuxmath and tuxtype will likely break in a
native build due to paths not matching up to how they are set in the
crossbuild.  In other words, if you do a "make" and "make install",
the resulting installation probably won't work.  However, I don't see
any reason why we couldn't do "make" and then "make nsis" (the target
used to create the NSIS win32 installer using our current crossbuild)
on windows, and then execute the resulting installer to install the
program.

David