[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Checking file generation for a test script
From: |
SF Markus Elfring |
Subject: |
Checking file generation for a test script |
Date: |
Sun, 18 Jun 2017 13:03:10 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 |
Hello,
I have tried the following small script out together with the program
“GNU Make 4.2.1-1.7” on my openSUSE Tumbleweed system.
my_compilation?=echo
my_preparation?=cat
footer?=MOTD.txt
prepared_file?=MOTD.in
MOTD%.log: MOTD%.txt MOTD%.in
${my_compilation} "$<: $$(cat ${prepared_file} ${footer})" > $@
${prepared_file}: MOTD.draft
${my_preparation} $< > $@
address@hidden:~/Projekte/Bau> my_message=MOTD.log && rm -f ${my_message};
touch MOTD.draft MOTD.txt && LANG=C make --no-builtin-rules -f
../rule-check2.make && LANG=C ls -l MOTD.in ${my_message}
cat MOTD.draft > MOTD.in
ls: cannot access 'MOTD.log': No such file or directory
-rw-r--r-- 1 elfring users 6 Jun 18 12:56 MOTD.in
Now I wonder why the log file is not generated by this build approach at the
end.
Where is my knowledge and understanding incomplete for this software situation?
Regards,
Markus
- Checking file generation for a test script,
SF Markus Elfring <=