I have no idea why you have done what you have, now. Why bother rewriting it if you're going to do exactly what you said you were trying to avoid? You've got exactly what you had before, except instead of nicely organized into folders, it's one enormous mess.
You might as well have just let them live in their own folders and used their old makefiles. Then you could do this:
Then you could do 'make all' and it would run make in each of the folders.
I have concatenated 2 makefiles, to produce 1 however it is not running all of the code, producing a fatal error: symbol referencing errors. No output written. Can anybody please help? (4 Replies)
I need to develop a makefile that spans across directories. For example, let's say i have an upper level directory (main) and about 2 subdirectories. I want my .cpp files and .o files to be in one subdirectory. I want my .a files to be in the other subdirectory. The .a files are made up of the... (0 Replies)
for example in my make file im building path from env variables and string but need to see what is did
what is the best way to print the result?
say I have in my Makefile :
exec_prefix = $(RUN_ENV_LOCAL)/apache
and I will like to print the exec_prefix value , how can it be done ? (1 Reply)
Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right... (1 Reply)
I have several programs in several directories and want to use make to build the executables. What I have done is to put the main programs in their own directory together with a makefile to build the program. Then I am thinking of having another makefile residing in the directory above so I can run... (1 Reply)
I have the following part of a makefile and want to simplify it
using rules rather than having to code the same two blocks
when I need ti build another program.
An having difficulty doing it
all: 1dvel2 1dvel 2dvel
... (8 Replies)
I am trying to practice to create Makefiles. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be rebuilt by typing make at the command line.
I have the following files:
ac.cc: has include ac.h and pg.h
fr.cc: has main... (8 Replies)
Hey guys,
Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries.
However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Hi All,
I was going through some makefiles where I saw occurrences of explib_subdirs and expinc_subdirs, which I could not understand.
Exporting libs to subdirs ? Exporting include files to specified subdirs ? When do we need to do that ?
What I could understand is, for a build, I would... (4 Replies)
Discussion started by: alltaken
4 Replies
LEARN ABOUT REDHAT
aimk
AIMK(1PVM) PVM Version 3.4 AIMK(1PVM)NAME
aimk - Portable make wrapper script
SYNOPSIS
aimk [ -here ] [ make arguments ]
DESCRIPTION
aimk is a wrapper program for make, used to portably select options to build PVM and PVM applications on various machines. Each port of
PVM is assigned an architecture name. The name is used both during compilation (to conditionally switch in code) and at runtime (to select
an executable or host).
aimk uses the value of environment variable $PVM_ARCH if it is set, otherwise it calls $PVM_ROOT/pvmgetarch to determine the architecture
name. pvmgetarch is a script that sniffs at various parts of the system to determine the correct architecture name. It is updated as new
PVM ports are defined, and can be augmented locally.
aimk determines the machine architecture and execs make, passing it the architecture and a configuration file along with arguments supplied
to aimk. It runs make in a subdirectory to prevent executables from becoming intermixed and to permit overlapping compiles. A different
makefile can be placed in each subdirectory or a single makefile, Makefile.aimk, can be shared between architectures. Per-architecture
definitions from the $PVM_ROOT/conf directory are appended to the common makefile. aimk calls make is called in one of three ways, depend-
ing on what makefiles are present:
i. If $PVM_ARCH/Makefile or $PVM_ARCH/makefile exists, change directory to $PVM_ARCH and exec make there:
(cd $PVM_ARCH ; make PVM_ARCH=$PVM_ARCH < aimk args >)
ii. Else if Makefile.aimk exists, create $PVM_ARCH directory if it doesn't exist, then:
(cd $PVM_ARCH ;
make -f $PVM_ROOT/conf/$PVM_ARCH.def
-f ../Makefile.aimk PVM_ARCH=$PVM_ARCH < aimk args >)
iii. Else just exec make in current directory:
make PVM_ARCH=$PVM_ARCH < aimk args >
If aimk succeeds in calling make, the exit status is that of make, otherwise it is 1.
FLAGS -here Forces aimk to run make in the current directory, e.g. converts case i. to case iii.
EXAMPLES
The following Makefile.aimk file builds and installs hello, creating the PVM binary directory if it doesn't exist. It can be run concur-
rently on machines of different types, sharing the same source directory.
LDIR = -L$(PVM_ROOT)/lib/$(PVM_ARCH)
PVMLIB = -lpvm3
SDIR = ..
BDIR = $(HOME)/pvm3/bin
XDIR = $(BDIR)/$(PVM_ARCH)
CFLAGS = -g -I$(PVM_ROOT)/include
LIBS = $(LDIR) $(PVMLIB) $(ARCHLIB)
$(XDIR):
- mkdir $(BDIR) $(XDIR)
hello: $(SDIR)/hello.c $(XDIR)
$(CC) $(CFLAGS) -o $@ $(SDIR)/$@.c $(LIBS)
mv $@ $(XDIR)
ENVIRONMENT
$PVM_ROOT Root path of PVM installation.
$PVM_ARCH PVM architecture name for machine.
FILES
$PVM_ROOT/lib/aimk The aimk program
$PVM_ROOT/conf/$PVM_ARCH.def Arch config file
SEE ALSO pvm_intro(1PVM)
02 May, 1994 AIMK(1PVM)