Visit Our UNIX and Linux User Community


Makefile instructions to create directories (CentOS7 , GNU Make 3.82)


 
Thread Tools Search this Thread
Top Forums Programming Makefile instructions to create directories (CentOS7 , GNU Make 3.82)
# 1  
Old 01-29-2020
Makefile instructions to create directories (CentOS7 , GNU Make 3.82)

Hello,

My makefiles are set up to generate an environment specific build directory based on the local configuration and some values passed to make. It generally looks like,

Code:
# compilers, may be passed to make
CC++ = g++
FCOMP = gfortran

# version of program, may be passed to make
ver = debug

# manually assign linux distro
OS=CentOS-7.7

# collect name information
ARCH := $(shell uname -m)
KERN := $(shell uname -r | cut -d. -f 1,2)

# find g++ compiler version
# this can vary with the distribution
CMP := $(shell g++ --version | cut -d ' ' -f 3 | sed q)

# create names for build directory name
CNAME := gpp-$(CMP)
FNAME := gfortran-$(CMP)

# archdir is executed as part of all and will create the necessary
# version specific directories if they do not exist
archdir: ${BDIR}

# concatenate the name for the build directory
BDIR := bld_$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directories do not exist
${BDIR}:
    @mkdir -p ${BDIR}

# archdir is part of all
all archdir program_name

When make is called with all, all runs archdir, archdir runs BDIR and the build directory gets created if it does not exist. This has generally worked well.

Recently I wanted to create some additional directories and so attempted to implement the same method.

I added a new directory name and instruction to make the directory. That instruction was added to archdir so that the resulting code looks like,

Code:
# archdir is executed as part of all and will create the necessary
# version specific directories if they do not exist
archdir: ${BDIR}  ${TESTDIR}

# create name for the build directory
BDIR := bld_$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directories do not exist
${BDIR}:
    @mkdir -p ${BDIR}

# create name for test directory
TESTDIR = ./test/(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directory does not exist
${TESTDIR}:
    @mkdir -p ${TESTDIR}

The directory ./test/ already exists. When I run the make file with all, the build completes without error but the new directory $TESTDIR is not created.

Any suggestions as to what I am missing here? Do I have a syntax issue? Is something out of order?

Some of this could probably be better done with a config script since there is no way that I know of to collect all of the above from every version of linux and windows with the same code. Sometimes I think it just makes more sense to pass values in the call to make or hard code the make file. Making up a directory name and creating the directory is something I think I should be able to do.

LMHmedchem
# 2  
Old 01-29-2020
Hi,
You have bad declare TESTDIR variable ( Forgot '$' for '(OS)' ) :
Code:
TESTDIR = ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)

These 2 Users Gave Thanks to disedorgue For This Post:
# 3  
Old 01-29-2020
Quote:
Originally Posted by disedorgue
Hi,
You have bad declare TESTDIR variable ( Forgot '$' for '(OS)' ) :
Code:
TESTDIR = ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)

Thanks for the suggestion, I did fix this error but it did not resolve the issue.

I decided to move the assignment of archdir to after the definitions of ${BDIR} and ${TESTDIR}.

Now the revised code looks like this,
Code:
# create name for the build directory
BDIR := bld_$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directories do not exist
${BDIR}:
    @mkdir -p ${BDIR}

# create name for test directory
TESTDIR = ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directory does not exist
${TESTDIR}:
    @mkdir -p ${TESTDIR}

# archdir is executed as part of all and will create the necessary
# version specific directories if they do not exist
archdir: ${BDIR} ${TESTDIR}

This now works and the test directory is created.

Of course, it seems logical that these instructions should need to be defined in the order above in that a variable is declared and assigned before the value is used. Make has never seemed to function like this. For instance, I have OBJSC = $(OBJCM) $(OBJSCLS) $(OBJSBGR) where OBJSC is a list of objects used in a build rule. The items in the lists, $(OBJCM), $(OBJSCLS), etc, are all assigned much later in the makefile after the assignment above. This has no effect and the applications builds correctly. The build rules for the linker always seem to come before the compile rules, which is also counterintuitive.

Perhaps all of my makefiles are set up in the wrong order even though the seem to work in the main?

LMHmedchem
This User Gave Thanks to LMHmedchem For This Post:
# 4  
Old 01-29-2020
Another error that maybe explain why not work when to declare archdir before TESTDIR :
Code:
TESTDIR := ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)


Last edited by disedorgue; 01-29-2020 at 01:15 PM.. Reason: grammar
# 5  
Old 01-29-2020
Quote:
Originally Posted by disedorgue
Another error that maybe explain why not work when to declare archdir before TESTDIR :
Code:
TESTDIR := ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)

So I wasn't expanding the components variables of TESTDIR correctly? I guess I should have at least noticed the TESTDIR was not being assigned using the same operator as BDIR.

I have tried now to use a similar method to copy files into the newly created directories and am having more issues. It seems to me as if the following code,
Code:
# create name for test directory
TESTDIR = ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)
# mkdir if the directory does not exist
${TESTDIR}:
    @mkdir -p ${TESTDIR}

overwrites the original value of TESTDIR which is,

./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)

with the mkdir instruction such that if you printed ${TESTDIR} after the
second assignment, it would print,

mkdir -p ./test/$(OS)_$(KERN).$(ARCH)_$(CNAME)_$(FNAME)_$(ver)

with the variables such as $(OS) expanded. This would mean that you could no longer use $(TESTDIR) to refer to the location that was originally assigned.

Is this true or am I not understanding how this is working?

LMHmedchem

Previous Thread | Next Thread
Test Your Knowledge in Computers #953
Difficulty: Medium
A memory-resident virus installs itself as part of the operating system when executed, after which it remains in RAM from the time the computer is booted up to when it is shut down.
True or False?

10 More Discussions You Might Find Interesting

1. Solaris

SunOS 5.5.1 usage of Makefile command in make file

I am new to Solaris and compilation using make files. I have a code base which is organized into different folders. At the root folder is a master make file and in the sub directories, there are make files for that particular folder. In the make files present in subdirectories, I am seeing... (2 Replies)
Discussion started by: rajujayanthy
2 Replies

2. Homework & Coursework Questions

Create Makefile from source files

1. The problem statement, all variables and given/known data: Create a makefile for a set of source files. Several sources files are given but we are not allowed to modify them. 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... (5 Replies)
Discussion started by: pintu1228
5 Replies

3. Shell Programming and Scripting

Bash script from makefile - it is called each time i call make

I've created a tag in the makefile: mytag: $(shell ${PWD}/script.sh) When i do: make clean - the script is executed When i perform make or make mytag the script is again executed with the output: make: Nothing to be done for mytag What i want ? I want script.sh to be executed only... (0 Replies)
Discussion started by: Pufo
0 Replies

4. Programming

Makefile No rule to make target

I am trying to create a makefile to build a program and am getting the following error: make -f tsimplex.mk make: *** No rule to make target `/main/tsimplex_main.cpp', needed by `tsimplex_main.o'. Stop. OPSYS = $(shell uname -s ) TARGET = tsimplex ROOTDIR = ../../.. GTSDIR =... (1 Reply)
Discussion started by: kristinu
1 Replies

5. Shell Programming and Scripting

Need help with a script to make makefile

How do we create a shell script that creates a makefile? what if we want to use the #include header files too? (2 Replies)
Discussion started by: sslokhan
2 Replies

6. Shell Programming and Scripting

automake does not create Makefile.in

hi all, I have written a simple C program hello.c and a Makefile.ac but when i try to run automake it does not create Makefile.in hence I am not able to run ./configure command in my directory. Following are the containts of my prog. hello.c -------- Code: #include<stdio.h> main() {... (0 Replies)
Discussion started by: useless79
0 Replies

7. Programming

A question about Makefile run by GNU make

Hello everybody, Currently I'm learning how to build projects (C programming) with GNU make. I have a problem with one Makefile and I would appreciate if you could kindly give me a hand. Here is the environment: OS: Redhat linux 5 compiler: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)... (2 Replies)
Discussion started by: dariyoosh
2 Replies

8. Shell Programming and Scripting

check if multiple directories exist else create missing directories

Hi , I 'm trying to check if multiple directories exist on a server, if not create the missing ones and print " creating missing directory. how to write this in a simple script, I have made my code complex if ; then taskStatus="Schema extract directory exists, checking if SQL,Count and... (7 Replies)
Discussion started by: ramky79
7 Replies

9. UNIX for Dummies Questions & Answers

make and clean in a single rule in the makefile.

Hi, This stems from the following thread https://www.unix.com/showthread.php?t=18299 I have a makefile which makes either executables or a shared library. i.e. make -f unix.mak will create the executables and make -f unix.mak libolsv will create the shared library. Since these have to be... (4 Replies)
Discussion started by: vino
4 Replies

10. Programming

about create Makefile

hello! i want to create a Makefile on the freebsd 4.5,so i vi the hello.c #include int main(int argc, char** argv) { printf(''Hello, GNU!\n''); return 0; } #autoscan #cp configure.scan configure.in #vi configure.in modify:AC_OUTPUT AC_OUTPUT(Makefile) #aclocal #autoconf... (0 Replies)
Discussion started by: mzp
0 Replies

Featured Tech Videos