orbixsol2s4.mk

C++的CORBA程序源代码,isporb.1.1.1.tar.gz

# This file is used to create the implicit rules -- DO NOT INSTALL!
# ------------------------------------------------------------
# Orbix 2.0 implicit rules for SunOS/GNU Make: 15/6/93 jmason
# ------------------------------------------------------------
#
# If you cut'n'paste this into your /usr/include/make/default.mk
# file, beware! This is not officially supported by Iona
# Technologies, and you may want to be a bit of a Makefile hacker
# to make it integrate well with your site's setup.

# The best thing to do would be put it in a standard place and
# anyone who wants the Orbix implicit rule set can include
# it with an "include <pathname>/orbix.mk" line in their
# Makefile. A good place to put it might be /usr/include/make.

# These rules define default C++, C++FLAGS and C++SUFFIX.
# C++ is the C++ compiler to use; C++FLAGS are command-line
# flags to the C++ compiler for use in compiling C++ source
# files into objects; C++SUFFIX is the filename suffix
# indicating C++ source. By default, it's set to "C" for AT&T C++,
# and "cc" for GNU g++.

# Feel free to override these in your Makefiles *after*
# including this file.

# IMPORTANT: If the -M switch is specified in IDLFLAGS, the IDL
# compiler appends to the user-specified file. The dependency for
# specified_file.o in the linking target should appear _after_ any use
# of the IDL compiler which takes the -M flag.  Putting it _last_
# is normally the best approach.

# Note that these rule definitions use pattern matching,
# and therefore only work with SunOS make and GNU make.

# They may not work with other vendor's versions of make.
# If they do not, you may wish to try using GNU make, which
# is free software produced by the Free Software Foundation.

# If the version of make you wish to use does not support
# pattern matching, use the sample explicit rule set in
# the comments at the end of this file.

# ------------------------------------------------------------
# Essential: set these to the locations into which you
#		have installed Orbix' components:

ORBIX_BINDIR    = /opt/Orbix_2.0/corba2/bin
ORBIX_LIBDIR    = /opt/Orbix_2.0/corba2/lib
ORBIX_INCDIR    = /opt/Orbix_2.0/corba2/include

#-------------------------------------------------------------
# To compile the demos, you should change these values as
# appropriate for your particular system installation
#-------------------------------------------------------------

X11BASE         = /usr/openwin
X11INCDIR       = $(X11BASE)/include
X11LIBDIR       = $(X11BASE)/lib

C++             = /vol/sparcworks/bin/CC
C++FLAGS        = -I$(ORBIX_INCDIR)
C++SUFFIX       = cc

# ------------------------------------------------------------
# ITCLT, IRCLT and ITSRV can be either statically or dynamically linked
# Use -Bdynamic or -Bstatic as appropriate.
# ------------------------------------------------------------
ITCLT           = -Bdynamic -lITclt
IRCLT           = -Bdynamic -lIRclt
ITSRV           = -Bdynamic -lITsrv
LDFLAGS         = -L$(ORBIX_LIBDIR)

# ------------------------------------------------------------
# SYSLIBS must be dynamically linked; otherwise you can expect to
# get linkage errors for symbols in the nsl library
# ------------------------------------------------------------
SYSLIBS         = -Bdynamic -lnsl -lsocket

IDL             = $(ORBIX_BINDIR)/idl 
IDLFLAGS        =

# ------------------------------------------------------------
# The following section defines implicit rules for creating
# *.{C,S}.C files, rules for compiling those
# into objects, and even a rule for compiling C++ source into
# objects (in case one isn't already defined).

# ------------------------------------------------------------
# first, put the new suffixes at the *head* of the suffix list,
# overriding any existing .C compilation method.
.SUFFIXES:
.SUFFIXES: .$(C++SUFFIX) .idl $(SUFFIXES)

# .SUFFIXES: .$(C++SUFFIX) .idl .hh $(SUFFIXES)
# ------------------------------------------------------------
# *[CS].o must be compiled here, and depends
# mostly on the C++ files produced from the IDL file.

%C.o: %C.$(C++SUFFIX)
	$(C++) -c $(C++FLAGS) $<

%S.o: %S.$(C++SUFFIX)
	$(C++) -c $(C++FLAGS) $<

%.o: %.$(C++SUFFIX)
	$(C++) -c $(C++FLAGS) $<

# and here's how to compile C++ files from the IDL file.
# only ONE of these rules will be run at make-time,

%S.$(C++SUFFIX): %.idl
	$(IDL) $(IDLFLAGS) $<

%C.$(C++SUFFIX): %.idl
	$(IDL) $(IDLFLAGS) $<

%.hh: %.idl
	$(IDL) $(IDLFLAGS) $<

# ------------------------------------------------------------
# If the version of make you wish to use does not support
# pattern matching, here's a sample of an explicit rule set.

# We assume the IDL file is called "foobar.idl", we wish
# to compile "foobarC.o", "foobarS.o", and
# "foobar.hh", and the C++ file suffix.
# ------------------------------------------------------------

# foobarC.o: foobar.hh foobarC.C
#	$(C++) -c ($C++FLAGS) foobarC.C
#
# foobarS.o: foobar.hh foobarS.C
#	$(C++) -c ($C++FLAGS) foobarS.C
#
# foobarC.C: foobar.idl
#	$(IDL) -c ($IDLFLAGS) foobar.idl
#
# foobarS.C: foobar.idl
#	$(IDL) -c ($IDLFLAGS) foobar.idl
#
# foobar.hh: foobar.idl
#	$(IDL) -c ($IDLFLAGS) foobar.idl