Lines Matching refs:architecture

9 a primary architecture -- the one the system has been built for -- and a
10 secondary architecture -- the one the additional set of system libraries has
14 Since the files for the secondary architecture will live in one or more separate
16 Haiku and install the packages for the secondary architecture later on, and
22 packages built for a secondary architecture.
26 1. Secondary architecture libraries and add-ons must live in respective
28    loading a secondary architecture executable.
29 #. Secondary architecture development libraries and headers must live in
30    "<secondary_arch>" subdirectory, where only the secondary architecture
32 #. Secondary architecture executables must live in a "<secondary_arch>"
34    symlinked to the primary architecture "bin" directory, using a symlink name
35    that doesn't clash with the primary architecture executable's name (by
36    appending to the name the secondary architecture name, e.g. "grep-x86"). If
37    there isn't a corresponding package for the primary architecture, the
40    unless there isn't a corresponding package for the primary architecture.
44 1. A secondary architecture package must not conflict with the corresponding
45    primary architecture package, so both can be active at the same time and in
48    particular architecture shouldn't need to be concerned with the
49    primary/secondary architecture issue. E.g. "cmd:grep" should provide them
51 #. Secondary architecture packages providing a command should generally provide
55    secondary architecture (3. of the general requirements actually implies that
57    command is architecture dependent (e.g. in case of compilers etc.).
58 #. Secondary architecture packages providing a library must provide