Changeset 977623b in rtems


Ignore:
Timestamp:
10/05/99 18:39:56 (24 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
0439dba
Parents:
b22feedc
Message:

Removed targets and configurations that are no longer functional
and not likely to become so. Comments on each configuration
are below.

+ Force CPU386 - This BSP was developed as part of the initial

port of RTEMS to the i386. This board has been unavailable
for a long time now.

+ GO32 - This BSP and some CPU code supported djgpp v1.x. This

version is now quite old. No one has stepped forward to
update the code to v2.x which may be technically impossible
anyway. More importantly, go32 has been superceded by the pc386 BSP.

Files:
3 deleted
3 edited

Legend:

Unmodified
Added
Removed

  • README.configure

    rb22feedc r977623b  
    187187
    188188a29k            : portsw
    189 i386            : force386 i386ex pc386
    190 i386-go32       : go32 go32_p5
     189i386            : i386ex pc386
    191190i960            : cvme961
    192191hppa1.1         : simhppa

  • c/src/make/README

    rb22feedc r977623b  
    9797        example):
    9898
    99             o-force386/                -- binaries (no debug, no profile)
    100             o-force386-debug/          -- debug binaries
    101             o-force386-profile/        -- profiling binaries
     99            o-pc386/                -- binaries (no debug, no profile)
     100            o-pc386-debug/          -- debug binaries
     101            o-pc386-profile/        -- profiling binaries
    102102
    103103        Using the template Makefiles, this will all happen automatically.
    104104
    105         Within a Makefile, the ${ARCH} variable is set to o-force386,
    106         o-force386-debug, etc., as appropriate.
    107 
    108         Typing 'make' will place objects in o-force386.
    109         'make debug' will place objects in o-force386-debug.
    110         'make profile' will place objects in o-force386-profile.
    111 
    112         NOTE:  For RTEMS work, the word 'force386' is the specified
     105        Within a Makefile, the ${ARCH} variable is set to o-pc386,
     106        o-pc386-debug, etc., as appropriate.
     107
     108        Typing 'make' will place objects in o-pc386.
     109        'make debug' will place objects in o-pc386-debug.
     110        'make profile' will place objects in o-pc386-profile.
     111
     112        NOTE:  For RTEMS work, the word 'pc386' is the specified
    113113               RTEMS_BSP (specified in the modules file)
    114114
    … …  
    189189        RTEMS_CUSTOM must point to this file; eg:
    190190
    191                 /.../make/custom/force386.cfg
     191                /.../make/custom/pc386.cfg
    192192
    193193        All leaf Makefile's also include either 'make/leaf.cfg' (or
    … …  
    218218            files you want to include.
    219219
    220             Example: custom/force386.cfg
     220            Example: custom/pc386.cfg
    221221
    222222               CONFIG.$(HOST_ARCH).OS = $(RTEMS_ROOT)/make/os/HPUX-9.0.cfg
    … …  
    229229               ## Target compiler config file, if any
    230230               CC_$(TARGET_ARCH)_DIR=$(RTEMS_GNUTOOLS)
    231                CONFIG.$(TARGET_ARCH).CC = $(RTEMS_ROOT)/make/compilers/gcc-force386.cfg
     231               CONFIG.$(TARGET_ARCH).CC = $(RTEMS_ROOT)/make/compilers/gcc-pc386.cfg
    232232
    233233        generic rules file
    … …  
    277277        ---------------------
    278278
    279             RTEMS_BSP      -- name of your 'bsp' eg: force386
     279            RTEMS_BSP      -- name of your 'bsp' eg: pc386
    280280
    281281            RTEMS_ROOT     -- The root of your source tree.
    … …  
    328328
    329329            ARCH        -- target sub-directory for object code
    330                            [ eg: o-force386 or o-force386-debug ]
     330                           [ eg: o-pc386 or o-pc386-debug ]
    331331
    332332            HOST_ARCH
    … …  
    336336            VARIANTS    -- full list of all possible values for $(ARCH);
    337337                           used mainly for 'make clean'
    338                            [ eg: "o-force386 o-force386-debug o-force386-profile" ]
     338                           [ eg: "o-pc386 o-pc386-debug o-pc386-profile" ]
    339339
    340340            VARIANT_VA  -- Variant name.
    … …  
    456456                               you don't need to duplicate items in both.
    457457
    458                 TARGET_ARCH -- target architecture (eg: o-force386)
     458                TARGET_ARCH -- target architecture (eg: o-pc386)
    459459                               leaf makefiles only.
    460460                               Should be specified before 'include leaf.cfg'.

  • make/README

    rb22feedc r977623b  
    9797        example):
    9898
    99             o-force386/                -- binaries (no debug, no profile)
    100             o-force386-debug/          -- debug binaries
    101             o-force386-profile/        -- profiling binaries
     99            o-pc386/                -- binaries (no debug, no profile)
     100            o-pc386-debug/          -- debug binaries
     101            o-pc386-profile/        -- profiling binaries
    102102
    103103        Using the template Makefiles, this will all happen automatically.
    104104
    105         Within a Makefile, the ${ARCH} variable is set to o-force386,
    106         o-force386-debug, etc., as appropriate.
    107 
    108         Typing 'make' will place objects in o-force386.
    109         'make debug' will place objects in o-force386-debug.
    110         'make profile' will place objects in o-force386-profile.
    111 
    112         NOTE:  For RTEMS work, the word 'force386' is the specified
     105        Within a Makefile, the ${ARCH} variable is set to o-pc386,
     106        o-pc386-debug, etc., as appropriate.
     107
     108        Typing 'make' will place objects in o-pc386.
     109        'make debug' will place objects in o-pc386-debug.
     110        'make profile' will place objects in o-pc386-profile.
     111
     112        NOTE:  For RTEMS work, the word 'pc386' is the specified
    113113               RTEMS_BSP (specified in the modules file)
    114114
    … …  
    189189        RTEMS_CUSTOM must point to this file; eg:
    190190
    191                 /.../make/custom/force386.cfg
     191                /.../make/custom/pc386.cfg
    192192
    193193        All leaf Makefile's also include either 'make/leaf.cfg' (or
    … …  
    218218            files you want to include.
    219219
    220             Example: custom/force386.cfg
     220            Example: custom/pc386.cfg
    221221
    222222               CONFIG.$(HOST_ARCH).OS = $(RTEMS_ROOT)/make/os/HPUX-9.0.cfg
    … …  
    229229               ## Target compiler config file, if any
    230230               CC_$(TARGET_ARCH)_DIR=$(RTEMS_GNUTOOLS)
    231                CONFIG.$(TARGET_ARCH).CC = $(RTEMS_ROOT)/make/compilers/gcc-force386.cfg
     231               CONFIG.$(TARGET_ARCH).CC = $(RTEMS_ROOT)/make/compilers/gcc-pc386.cfg
    232232
    233233        generic rules file
    … …  
    277277        ---------------------
    278278
    279             RTEMS_BSP      -- name of your 'bsp' eg: force386
     279            RTEMS_BSP      -- name of your 'bsp' eg: pc386
    280280
    281281            RTEMS_ROOT     -- The root of your source tree.
    … …  
    328328
    329329            ARCH        -- target sub-directory for object code
    330                            [ eg: o-force386 or o-force386-debug ]
     330                           [ eg: o-pc386 or o-pc386-debug ]
    331331
    332332            HOST_ARCH
    … …  
    336336            VARIANTS    -- full list of all possible values for $(ARCH);
    337337                           used mainly for 'make clean'
    338                            [ eg: "o-force386 o-force386-debug o-force386-profile" ]
     338                           [ eg: "o-pc386 o-pc386-debug o-pc386-profile" ]
    339339
    340340            VARIANT_VA  -- Variant name.
    … …  
    456456                               you don't need to duplicate items in both.
    457457
    458                 TARGET_ARCH -- target architecture (eg: o-force386)
     458                TARGET_ARCH -- target architecture (eg: o-pc386)
    459459                               leaf makefiles only.
    460460                               Should be specified before 'include leaf.cfg'.
Note: See TracChangeset for help on using the changeset viewer.