Changeset dc5623bb in rtems


Ignore:
Timestamp:
Jan 22, 2003, 12:25:57 PM (18 years ago)
Author:
Ralf Corsepius <ralf.corsepius@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
8a86d78
Parents:
88cd4ab
Message:

2003-01-22 Ralf Corsepius <corsepiu@…>

  • FAQ.texi: Rename section "Building RTEMS 4.5" into "Building RTEMS". build45.t: Remove references to 4.5. Several minor updates.
Location:
doc/FAQ
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • doc/FAQ/ChangeLog

    r88cd4ab rdc5623bb  
     12003-01-22      Ralf Corsepius <corsepiu@faw.uni-ulm.de>
     2
     3        * FAQ.texi: Rename section "Building RTEMS 4.5" into "Building
     4        RTEMS".
     5        build45.t: Remove references to 4.5. Several minor updates.
     6
    172003-01-22      Ralf Corsepius <corsepiu@faw.uni-ulm.de>
    28
  • doc/FAQ/FAQ.texi

    r88cd4ab rdc5623bb  
    8383* General Development Tool Hints::
    8484* RTEMS Concepts::
    85 * Building RTEMS 4.5::
     85* Building RTEMS::
    8686* BSP Questions::
    8787* Debugging Hints::
  • doc/FAQ/build45.t

    r88cd4ab rdc5623bb  
    33@c
    44
    5 @chapter Building RTEMS 4.5
     5@chapter Building RTEMS
    66
    77Building any package in a cross-compilation fashion can be difficult,
     
    1616
    1717This section of the FAQ tries to address the more frequently asked
    18 questions about building RTEMS 4.5.  Thanks to Ralf Corsepius for
     18questions about building RTEMS.  Thanks to Ralf Corsepius for
    1919compiling this section from excerpts from various postings to the
    2020rtems-users mailing list.
     
    3939
    4040No, you don't.  Or to be more accurate, you won't need them until you
    41 modify something in RTEMS's Makefile.ams/configure.ins or start to develop
     41modify something in RTEMS's Makefile.ams/configure.acs or start to develop
    4242with RTEMS.
    4343 
     
    5252@subsection Can I use a non-gcc cross-toolchain?
    5353
    54 
    5554Generally speaking, it should be possible.
    56 However, most RTEMS-4.5 development has taken place using gcc-2.9x, therefore
     55However, most RTEMS development has taken place using gcc, therefore
    5756getting it working may not be easy.
    5857
     
    8180You are probably trying to build within the source-tree.
    8281RTEMS requires a separate build directory.  I.e.  if the
    83 sources are located at @code{/usr/local/src/rtems-4.5.0},
     82sources are located at @code{/usr/local/src/rtems-@value{VERSION}},
    8483use something similar to this to configure RTEMS:
    8584
     
    8887mkdir build
    8988cd build
    90 /usr/local/src/rtems-4.5.0/configure [options]
     89/usr/local/src/rtems-@value{VERSION}/configure [options]
    9190@end example
    9291
     
    124123
    125124Host tools are supposed not to be prefixed.
    126 e.g.: cc, ld, gcc etc.
     125e.g.: cc, ld, gcc, autoconf, automake, aclocal etc.
    127126
    128127If using OAR Corporation's rpms for the toolchain, simply prepend
     
    131130@subsection Can I build RTEMS Canadian Cross?
    132131
    133 Unfortunately, not (yet).
     132RTEMS >= 4.6.0 configuration is prepared for building RTEMS Canadian Cross,
     133however building RTEMS Canadian Cross is known to be in it's infancy, so
     134your mileage may vary (See @code{README.cdn-X} in the toplevel directory of
     135RTEMS's source tree for details.)
    134136
    135137@subsection Building RTEMS is slow
     
    137139RTEMS has become fairly large :).
    138140
    139 In comparison to building previous versions, building RTEMS-4.5 is slow,
     141In comparison to building previous versions, building RTEMS is slow,
    140142 but that's the tradeoff to pay for simplier and safer configuration.
    141143
     
    167169@end example
    168170
     171
    169172@subsection Building RTEMS does not honor XXX_FOR_TARGET
    170173
    171 RTEMS currently does not support passing flags from the environment.
    172 Instead add a @code{make/custom/mybsp.cfg} for your bsp and set
    173 appropriate flags there.
     174RTEMS < 4.6.0 did not support passing flags from the environment.
     175If using RTEMS < 4.6.0, editing your BSP's @code{make/custom/mybsp.cfg} and
     176setting appropriate flags there is required.
     177
     178RTEMS >= 4.6.0 honors several XXX_FOR_TARGET environment variables.
     179Run @code{<path-to-rtems>/configure --help} for a full list of supported variables.
    174180
    175181@subsection Editing Makefile.in Makefile configure
     
    185191Changes to them will be swapped away soon and will get lost.
    186192
    187 Instead edit the sources (eg.: Makefile.ams, configure.ins) auto* generated
     193Instead edit the sources (eg.: Makefile.ams, configure.acs) auto* generated
    188194files are generated from directly.
    189195
    190 If sending patches always send Makefile.ams and configure.ins.
     196If sending patches always send Makefile.ams and configure.acs.
    191197Sending Makefile.ins, Makefiles and configure scripts is pretty much useless.
    192198If sending larger patches, consider removing all auto* generated files
     
    234240
    235241Each BSP now has its own configure script.
    236 I highly recommend you look at the Makefile.am's, configure.in, of a similar
     242I highly recommend you look at the Makefile.am's, configure.ac, of a similar
    237243BSP.  You might even want to consider running "bootstrap -c" from the top of
    238244the tree and looking at what is left.  bootstrap (cf. @ref{./bootstrap})
     
    328334need to run @code{bootstrap}, because automake automatically updates
    329335generated files when it detects some files need to be updated (Cf.
    330 @ref{--enable-maintainer-mode}).
    331 
    332 @subsection --enable-maintainer-mode
     336@ref{configure --enable-maintainer-mode}).
     337
     338@subsection configure --enable-maintainer-mode
    333339
    334340When working within the source-tree, consider to append
     
    336342
    337343@example
    338 <path>/rtems-4.5.0/configure <options> --enable-maintainer-mode
     344<path>/rtems-@value{VERSION}/configure <options> --enable-maintainer-mode
    339345@end example
    340346
     
    345351Configuring RTEMS in maintainer-mode will require to have autoconf, automake
    346352and underlying tools installed (Cf. @ref{Required Tools}).
     353
     354@subsection configure.ac vs. configure.in
     355
     356autoconf < 2.50 used the name @code{configure.in} for it's input files.
     357autoconf >= 2.50 recommends using the name @code{configure.ac}, instead.
     358
     359RTEMS > 4.5.0 applies autoconf >= 2.50, therefore all former RTEMS's
     360@code{configure.in}'s have been renamed into @code{configure.ac} and
     361adapted to autoconf >= 2.50 demands.
Note: See TracChangeset for help on using the changeset viewer.