[Rpm-maint] Problems using RPM to build cross-compiled (MinGW/Windows) packages
Richard W.M. Jones
rjones at redhat.com
Mon Aug 4 13:58:51 UTC 2008
On Mon, Aug 04, 2008 at 07:56:31AM -0500, Mark Hatle wrote:
> You will want to probably define _strip as true or provide a custom
> __os_install_post. This is a necessity if you are creating a cross
> compiler with binaries for another architecture.
I maybe should have said that I'm aware of the workarounds used to
modify __os_install_post and was just wondering if we could get
something in base RPM instead, but ...
> For packages compiled to run on a different target the right approach is
> to provide a macro file that will be autoloaded by rpm using
> --target=i686-mingw32. In this file you can specify all of the things
> that a target package uses to compile, strip, etc.
... I didn't know you could do this, and it looks like a better
approach to try.
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
More information about the Rpm-maint