Home / Questions / 58530
Accepted
NaCl
Asked: 2020-03-29 06:57:37 +0800 CST 2020-03-29 06:57:37 +0800 CST

How to build the project once and link it when building other projects?

  • 772

I have the following problem, assuming my project structure is the following ( /is the root).

/bin                   # Directorio vacío, es la salida del makefile.
/include/*.h           # assembler.h core.h utils.h, Todos los headers estan aquí.
/src/assembler/*.c     # assembler.c tokenizer.c y otras herramientas del ensamblador.
/src/core/*.c          # utils.c core.c y todos los ficheros del núcleo compartido.
/src/machine/*.c       # bla.c foo.c .... Todos los ficheros de la máquina virtual.

All projects under /srchave the project as a dependency core, but have access to the directory headers/include

Using GNU makeI need to be able to compile only one of the projects I am working on, without the need to alter other projects, so far I have used the following Makefile:

# #$@% Makefile
CC=gcc
FLAGS=-Wall -Wextra -Wpedantic -Werror -std=c11 -O3
INCLUDES=-Iinclude

checkbin:
    # Ensure bin is there.
    @if [ ! -e "bin" ]; then mkdir "bin"; fi

assembler: checkbin # First check for binaries folder.
    $(CC) -o bin/assembler $(INCLUDES) $(FLAGS) src/core/*.c src/assembler/*.c

vm: checkbin
    $(CC) -o bin/vm $(INCLUDES) $(FLAGS) src/core/*.c src/machine/*.c

clean:
    @if [ -e "bin" ]; then \
        rm -rf "bin"; \
    fi

default: assembler # set assembler to default...

He Makefileactually does the work, but he does a lot of work; it is recompiling the coreevery time i go to compile some other project like machineor assembler.

To compile them separately I know I have to use the flag -c, gccbut when inputting multiple files with this flag, it doesn't allow me to use the flag -oto specify the output, for example:

$(CC) -c $(FLAGS) $(INCLUDES) /src/core/*.c 
# Si intento poner -o "bin/core" en este caso, me arroja error

How can I move the compiled files of the dependency project , for this case, coreinto their respective directory /bin/coreso that it can be used later to compile any other project?

For example:

/bin/core/utils.o
/bin/core/core.o

And binds to the following statement:

# Asumiendo los valores puestos arriba:
assembler: checkbin
    @if [ ! -e "bin/assembler" ]; then mkdir "bin/assembler"; fi
    # ... <- instrucción que pondrá los .o en el directorio /bin/assembler/*.o
    $(CC) -o /bin/assembler/assembler /bin/core/*.o /bin/assembler/*.o
    # Sólo necesitamos enlazar los archivos objeto.
gcc

1 Answers

  1. Best Answer

    The basic solution was as Trauma described in his comment, for this I had to re-structure the project in such a way that it would be as follows:

    /components/*.h      # Todos los archivos cabecera
/core/bin            # Carpeta que contendra los archivos objeto.
/core/*.c            # Archivos de codigo del core
/core/Makefile       # Makefile del proyecto Core
/hasm/bin        
/hasm/*.c            # Codigo del proyecto assembler
/hasm/Makefile
/machine/bin     
/machine/*.c         # Codigo del proyecto machine
/machine/Makefile

    And Makefileit configures it in each project that it needs from coreso that it will check if it is compiled and thus copy its object files, otherwise it compiles the project. Staying as follows:

    # hasm makefile.
CC=gcc
FLAGS=-Wall -Wextra -Wpedantic -Werror -O3 -std=c11 -c
INCLUDES=-I../components
OUTPUT=hasm # Cambia con el nombre del proyecto.

default: build

# Crea un objetivo condicionalmente, si existen los binarios del proyecto Core.
ifeq ("$(wildcard $(ls ../core/bin/*.o 2> /dev/null))","") # Verifica si hay archivos en /core/bin
dependencies:
    @make -C ../core;
else
dependencies:
    @echo "Core good.";
endif

# Mira a ver si existe el foder bin en el directorio actual.
checkbin:
    @if [ ! -e "bin" ]; then mkdir "bin"; echo "Created!"; else echo "Exists!"; fi

# Construye el proyecto.
build: dependencies checkbin 
    @echo "Building project..."
    $(CC) $(FLAGS) $(INCLUDES) src/*.c  # Compila con el flag -c los archivos del proyecto.
    @mv *.o bin/                        # Mueve todos los archivos objeto al folder bin.
    @cp ../core/bin/*.o bin/;           # Copia los archivos de "../core/bin/" a "./bin/"
    $(CC) -o bin/$(OUTPUT) bin/*.o      # Enlaza con gcc.

# Elimina el folder bin y algun .o que quede en el directorio actual.
clean:
    @if [ -e "bin" ]; then rm -rf "bin"; fi
    @if [ -f *.o ]; then rm -f *.o; fi

    When doing , the recipemake is executed , which has as a prerequisite a and , in , it is in charge of calling , where it specifies that it is in the directory to its right, with this the dependencies of the project are compiled, that is, . builddependenciescheckbindependenciesmake -C ../core-CMakefilecore

    After that, proceed to copy the object files inside the folder /core/bin/to the folder of the project you are working on and link them without problem.

    • 3