hello Britton
thank you for your advice
You are right, I was not even asked the question but it is important that I
can see if my command fails. I'll think about that. thank you
--
View this message in context:
http://gnu-make.2324884.n4.nabble.com/assign-the-result-of-my-python-script-to-a-var
hello Nicholas Clark
thank you for your advice
You are right, I was not even asked the question but it is important that I
can see if my command fails.
I tried your method. this may be a good idea.
thank you
--
View this message in context:
http://gnu-make.2324884.n4.nabble.com/assign-the-resul
One other small thing that may or may not be obvious: if your
estimationkmer.py script fails (returns non-zero), you won't be
notified (and ESTK will likely end up empty).
Paul, is there any chance of adding a different version of $(shell)
that fails noisily if the given shell command returns non-
What about doing it with an EVAL statement?
Like this:
Begin to_upper.py
-
$ cat to_upper.py
#!/usr/bin/env python
import sys
def main():
sys.stdout.write(sys.argv[1].upper().strip()+"\n")
if __name__ == "__main__":
main()
-
thank you for your help.
it works now. With your explanation, I understood how to fix the three
problems of the line.
Just a clarification. The second problem means that I could not reuse the
variable ESTK in another rule (not in the rule Quake where it is defined)?
because I can use "; \" only fo
On Wed, 2015-03-25 at 02:54 -0700, guylobster wrote:
> this is the first time I do a makefile.
> But I block to assign the result of my python script to a variable of my
> makefile.
> The function works. Here the function and the result.
>
> *My makefile*
> G_SIZE=10
> Quake:
> python esti