[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Different architectures on different packages built from one.spec file



On Thu, 2001-12-13 at 06:23, Toralf Lund wrote:
> Is there any way at all I can mark the different (sub) packages in an RPM
> .spec file for different architectures? I have an application for Linux on
> Intel which is split into several packages, and I know that one of the
> packages will work on the particular variant of the CPU I'm building on,
> while the others are compatible with all i386 based CPUs. In other words,
> when building on an i686, I want 'rpm -bb' to output something like
> (if the application is called "app", sub packages "pkg_a", "pkg_b" and
> "pkg_c", and version and release number is 1):
> 	app-pkg_a-1-1.i386.rpm
> 	app-pkg_b-1-1.i386.rpm
> 	app-pkg_c-1-1.i686.rpm
> 
> Is this possible? It looks like the "BuildArch:" tag is always applied
> globally, so I can't use that. Is there anything else I can do?

I don't believe that you can do this with in a single pass build. 
However, with creative use of BuildArch, and ExclusiveArch, you should
be able to do this in a couple of passes.  So, you'd run 'rpm -bb' and
it would generate app-pkg_a-1-1.i386.rpm and app-pkg_b-1-1.i386.rpm, and
then you'd run 'rpm -bb --target=i686' and it would generate
app-pkg_c-1-1.i686.rpm.  Not particularly pretty, but it should work to
do what you want.  I don't know of any "good" examples on doing this
though.  Read MaxRPM, I guess.  :)
	Greg

-- 
Portland, Oregon, USA.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []