Since the tool shares code with the main binary, distributing it
separately is inconvenient. One of the platforms targeted is Windows,
so having it in C++ is easiest, since a scripting language would
require users to install even more tools. And there's really a pile of
resource files, the point of
On 2014-01-29 05:10 +, Pierre Phaneuf wrote:
> I've just set up a Makefile.am for a package I'm working on, and it's going
> pretty well, but I've hit a snag with cross-compilation...
>
> This package installs a binary and a resource file. That resource file is
> build with a special tool that
On 01/29/2014 06:10 AM, Pierre Phaneuf wrote:
I've just set up a Makefile.am for a package I'm working on, and it's going
pretty well, but I've hit a snag with cross-compilation...
This package installs a binary and a resource file. That resource file is
build with a special tool that is build b
I've just set up a Makefile.am for a package I'm working on, and it's going
pretty well, but I've hit a snag with cross-compilation...
This package installs a binary and a resource file. That resource file is
build with a special tool that is build by the Makefile.am. When I
cross-compile, it work
