11-19-2008
My Makefile
Here is the makefile of the CODE B:
### SccsId[] = "@(#)Makefile 1.1 11/06/98"
#!/bin/sh
#
# Include the macro definition file
#
include $(MAKE_DIR)/$(MACHINE)/make.macro
#
#---------------------------START HERE------------------------------------
#
# a: Use the default definition "NO_SUB_DIR", if there is no subdirectories.
# otherwise add all the required subdirectory names in SUBDIRS.
# example:
# (1)SUBDIRS = dbll cmxlib cpulib
#
# Just uncomment the following line if there is no subdirectory.
#SUBDIRS = NO_SUB_DIR
#
SUBDIRS = NO_SUB_DIR
#
# b: PACKDEFS is the macro definitions, additional include file directories
# and debug flag for compilation.
# example:
# (1)PACKDEFS = -w -DSYS_V -DSTD_C -I$(SAM_INCLUDE)
# Leave it empty if it is not used.
#
# CGG: Anadido Compilacion con ANSI (para INTECHANGE)
PACKDEFS = -I$(CMX_AUTO_INCLUDE) -I$(CMX_USER_INCLUDE) -Aa
#
# c: To make a library add the library name in LIBRARIES, e.g cmxlib.a,
# cpulib.a etc, in the following lines define the contents of the library.
#
# example: (1)LIBRARIES = dblllib.a cmxlib.a
# (2)dblllib.a = dbload.o dbpath.o dbfileio.o dboutput.o \
# (3) dblist.o dbtemplate.o dbtabular.o
# (4)cmxlib.a = ...
#
# Note: Remember to put a SPACE before "=" or "\"
# Leave it undefined if there is no library in this package.
# The "lib.a =" is the key for parsing the makefile.
#
LIBRARIES =
#
# d: To make a specific program add the program name in EXECUTABLES, e.g
# dbll, swbusd etc. In the following lines define the objects for making
# the program.
# example: (1)EXECUTABLES = dbll
# (2)dbll.exe = dbll.o $(CMX_LIB) $(CMX_LIB)/dblllib.a \
# /usr/lib/libmV.a
#
# Note: Remember to put a SPACE before "=" or "\"
# Leave it undefined if there is no executable in this package.
# The ".exe =" is the keyword for parsing the makefile,
# You may have to add the system libraries, e.g. SYBASE, SAMMI, MOTIF etc.
# Besure to put the complete path for the system libraries, e.g.
# use /usr/lib/libmV.a not -lm.
#
EXECUTABLES = simacc
simacc.exe = simacc.o $(CMXLIBS) $(SYB_CLIENT) $(MACHINE_LIBS)
#
# Libreria especifica para proyecto SIMCOT:
# $(SIM_LIBS) = /usr/oasys/V5.2.2/HP/oasys/lib/simcotlib.a
#
#-----------------------STOP HERE------------------------------
# Include the makefile (make.include) and dependencies file (./_depend)
# You have to do a "touch ./_depend; make depend" if the dependencies
# file not exist.
#
include $(MAKE_DIR)/make.include
include $(OBJ_DIR)_depend
#
# END OF MAKEFILE
#
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have a makefile which looks like this
ProcessA :
commands
touch pro1
ProcessB : pro1
commands
touch pro2
ProcessC: pro3
commands
and after some runs, i wish only pro3 to run and I check that "pro1" and "pro2" are there in the directory, but still, if i give make... (3 Replies)
Discussion started by: sskb
3 Replies
2. Programming
My make file is
CFLAGS = -Wall -g
LDFLAGS = -lm
CC = g++
all: server client
rc4.o: rc4.cpp rc4.h
${CC} ${CFLAGS} -c rc4.cpp
server.o: server.cpp rc4.h
${CC} ${CFLAGS} -c .cpp
client.o: client.cpp rc4.h
${CC} ${CFLAGS} -c client.cpp
server: server.o... (2 Replies)
Discussion started by: neerajgoyal12
2 Replies
3. Programming
Hi all,
I have 4 '.cpp' files and 1 header files:
Tools.cpp
Code1.cpp
Code2.cpp
Code3.cpp
and Tools.hh
Now all Code1.cpp, Code2.cpp, Code3.cpp
use functions stored in Tools.cpp.
Currently, what I do to compile all of them is using
this simple shell script: (1 Reply)
Discussion started by: monkfan
1 Replies
4. UNIX for Advanced & Expert Users
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
Discussion started by: hernandinho
2 Replies
5. Programming
I need to create an executable with these two makefiles(they both have libaries i
need(qt and ruby))
i have extconf.rb
gui.ui
gui_include.h
main.cpp
ScaleIM_client.rb
ui_gui.h
i want to combine them all into one executable
please!... (2 Replies)
Discussion started by: gjgfuj
2 Replies
6. Programming
Hi,
Here is my makefile http://pastie.org/1104332. I am trying to compile different .c files and .s files (assembly files) from different sub directories into E:/em35x/build/mfg-sample-app-cortexm3-iar-em357-em3xx-dev0680/ then the linker should link all the .o files from the build directory... (1 Reply)
Discussion started by: blade2008
1 Replies
7. Programming
Im trying to build a makefile for the first time in many years and Im coming to a screaching halt on something that should be child's play; just compiling two files. Here is an excerpt of the make file.
(using GMAKE on a TI compiler)
CCHP = <<compiler>>
PROJ_DIR = .
APP_DIR ... (2 Replies)
Discussion started by: DrNismo
2 Replies
8. Emergency UNIX and Linux Support
I had created a Makefile for my project. my project file hierarchy is like this:
1. a source folder with main.c and Makefile in it
2. and a top level Makefile
here is the Makefile in src folder
all: program
program: main.c
gcc -o program main.c
clean:
rm programand here is top... (3 Replies)
Discussion started by: majid.merkava
3 Replies
9. Programming
hello, I'm trying to create a makefile to run multiple c files. I am able to run one c file only with the code I have when I tried to run 2 or more c files I'm not able. here is my code
# $Source: /home/hectormasencio/make/Makefile,v $
# $Date: 2012/11/27 11:35:30 $
CC= gcc
OBJS= temp.o... (3 Replies)
Discussion started by: Hector M.
3 Replies
10. Programming
I have written this makefile and am getting an error saying
make nfd
gfortran -O -Wall -fbacktrace -fno-align-commons -c -o fd.o fd.f
fd.f:49: Error: Can't open included file 'fd.par'
make: *** Error 1
The directory structure is as follows
.
├── library
│ ├── fd
│ │ ├──... (3 Replies)
Discussion started by: kristinu
3 Replies
md(1) BSD General Commands Manual md(1)
NAME
md -- process raw dependency files produced by cpp -MD
SYNOPSIS
md [-d] [-f] [-m makefile] [-u makefile] [-o outputfile] [-v] [-x] [-D c|d|m|o|t|D]
DESCRIPTION
The md command basically does two things:
Process the raw dependency files produced by the cpp -MD option. There is one line in the file for every #include encountered, but there are
repeats and patterns like .../dir1/../dir2 that appear which should reduce to .../dir2. md canonicalizes and flushes repeats from the depen-
dency list. It also sorts the file names and "fills" them to a 78 character line.
md also updates the makefile directly with the dependency information, so the .d file can be thrown away (see d option). This is done to
save space. md assumes that dependency information in the makefile is sorted by .o file name and it procedes to merge in (add/or replace [as
appropriate]) the new dependency lines that it has generated. For time efficiency, md assumes that any .d files it is given that were cre-
ated before the creation date of the "makefile" were processed already. It ignores them unless the force flag [f] is given.
FLAG SUMMARY
-D c|D|d|m|o|t
Specify debugging option(s):
c show file contents
D show very low level debugging
d show new dependency crunching
m show generation of makefile
o show files being opened
t show time comparisons
-d Delete the .d file after it is processed
-f Force an update of the dependencies in the makefile, even if the makefile is more recent than the .n file. (This implies that md has
been run already.)
-m makefile
Specify the makefile to be upgraded. The defaults are makefile and then Makefile.
-o outputfile
Specify an output file (other than a makefile) for the dependencies.
-u makefile
Like -m, but the file will be created if necessary.
-v Set the verbose flag.
-x Expunge old dependency information from the makefile.
SEE ALSO
make(1)
BUGS
Old, possibly not used by anyone.
HISTORY
The md utility was written by Robert V. Baron at Carnegie-Mellon University.
BSD
June 2, 2019 BSD