I would suggest doing this in your IOC and support library Makefiles, not globally.
For example, this is my Makefile for a library for VME/Industry Pack hardware.
*********************
corvette:ip330/ip330App/src>more Makefile
TOP=../..
include $(TOP)/configure/CONFIG
#----------------------------------------
# ADD MACRO DEFINITIONS AFTER THIS LINE
#=============================
LIBRARY_IOC_vxWorks += ip330
LIBRARY_IOC_RTEMS += ip330
# If your Linux system supports drvIpac and devLib then uncomment this line
LIBRARY_IOC_Linux += ip330
ip330_SRCS += drvIp330.c
INC += drvIp330.h
DBD += ip330Support.dbd
ip330_LIBS += $(EPICS_BASE_IOC_LIBS)
#=============================
#===========================
include $(TOP)/configure/RULES
#----------------------------------------
# ADD RULES AFTER THIS LINE
*********************
Mark
________________________________
From: [email protected] on behalf of Angus Gratton
Sent: Sun 9/19/2010 9:27 PM
To: tech-talk
Subject: Configuring an IOC to -not- build for host arch
I have a simple build question, answer must be in the build docs
somewhere but I can't track it down.
I have EPICS base building for RTEMS-mvme3100 and linux-x64 (host arch.)
Until now I've been building our IOC for both as well. The few places
where I needed RTEMS-specific calls I just #ifdefed them in.
I'm now adding significant RTEMS-specific functionality, so I'd like to
only build the IOC (and our specific hardware support library) for
RTEMS.
CROSS_COMPILER_TARGET_ARCHS seems to always apply "in addition to" the
host. What is the best way to disable a specific arch target in the
EPICS build system?
Cheers,
Angus