[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] RPM Targets for binaries
On Fri, 18 Jun 2010, Miro Kropacek wrote:
1. Why do you set CFLAGS="-m68020-60 ${RPM_OPT_FLAGS}" when
RPM_OPT_FLAGS are already set to m68020-60?
I think the example you are speaking of is a m68kmint target, so the CPU
needs to be specified.
2. You begin with rpm -ba make.spec / rpm -ba make.spec --target
m68k020mint / rpm -ba make.spec --target cfmint approach (i.e. build
for each architecture separately) and then you zlib example contains
3-in-1 rpm? Or did you misunderstand something?
With libraries, the Multilib support is easy on the end user, and also
simpler just to package everything together. With make being a binary,
one binary for each target, with Zlib being a lib, one dev package with
all targets.
I really can't decide what's the best option for multilib environment.
Each has its pros and cons... I think one thing needs clarification:
we're talking about devel-only rpm files, right? Because normal rpms
(like 'awk' for example) clearly can be in m68kmint / m68k020mint /
cfmint versions (and conflicting with each other). And about devel
ones containing binaries: would it be really such a big sin to have it
in /usr/bin/m68020-60 and /usr/bin/m5475?
Yeah, pure binaries can each be set for their own target, and the user
would just pick what they want and be done with it.
Dev packages with binaries is where the issue lies.
One problem with packing all 3 target binaries is the size. Libraries are
definitely a low cost, disk space wise, addition, but binaries start
eating space. I was trying to come up with a way to detect installed CPU
at install time with RPM, and have a post script run to pick the right
binary for the user to not do like you suggest above with CPU specific bin
paths, but, so far, did not find something I liked and that would work
cleanly.
Although, the binary paths could be the best solution.
Anyway, I'm going to hopefully patch RPM today for those additional
targets and get it tested so can move forward. RPM will most likely need
to be patched again once the Coldfire is released....
Keith
--
MiKRO / Mystic Bytes
http://mikro.atari.org