Make's purpose is to build a project by compiling only those source files that have changed since the previous build, resolving dependencies along the way, according to well defined rules (with a sane set of default rules).
PREMISE
Is it a good idea to use two separate directories (development directory and production/compiling/building directory)?
Here is a concrete example
Code:
# SOURCE : dev (the development directory)
# DESTINATION: ../prod (the production/compiling/building directory)
+ cd dev
+ rsync \
-a \
--exclude makefile \
--exclude a \
--exclude b \
--delete \
--delete-excluded \
. \
../prod
+ find
./makefile
./b
./a
+ cat makefile
test1:
cat a b > x
test2:
cat ${SRC}/a ${SRC}/b x
+ make \
-f $PWD/makefile \
-C ../prod \
test1
+ make: Entering directory '/tmp/tmp.acvquFbBZk/prod'
cat a b > x
cat: a: No such file or directory
cat: b: No such file or directory
mmmhhh...
Let's try again with <B>test2</B>
Bash:
+ make \
-f $PWD/makefile \
-C ../prod \
test2
make: Entering directory '/tmp/tmp.acvquFbBZk/prod'
cat /a /b x
cat: /a: No such file or directory
cat: /b: No such file or directory
mmmhhh... it doesn't work, maybe because, in reality, the variable ${SRC} doesn't exist: I abandoned myself to my intuition...
So how to solve?
Anyway, as already said at the beginning, Is it a good idea to use two separate directories?
Or, especially if you use make command, is it better to do everything in one directory (have source files and compiled files in a single directory)?
PS
I don't understand much English and I don't speak English, so try to answer calmly and clearly.
One question at a time, one answer at a time; but at the same time try to answer all the questions.
Let me understand the concepts well!!!
Calm down, calm down, examine carefully what I wrote, and then calmly answer, otherwise I am forced to always ask for further explanations.
