Python in Makefile Question

[Efrat Regev]

Hello,

I'd like to ask a question concerning a python script in a makefile.
Suppose I have a C++ project (sorry for raising this in a Python newsgroup),
with some makefile for it. Before compiling the code, I'd like to check that
there are no C++ convention violations (e.g., identifiers beginning with an
underscore). So my makefile looks something like this:

target: ...
verify.py
$(CC) ...

verify.py is a python script that checks for convention violations, i.e.,
its first line is

#! /usr/bin/env python

I can't figure out the following:
1. How can I get the python script to return a value to make, so that if it
decides that there are convention violations make will fail?
2. How can I pass information from the makefile to the python script, e.g.,
the base directory to check?

Thanks,

Efrat

[Dan Bishop]

Efrat Regev wrote:

Hello,

I'd like to ask a question concerning a python script in a makefile. Suppose I have a C++ project (sorry for raising this in a Python newsgroup), with some makefile for it. Before compiling the code, I'd like to check that there are no C++ convention violations (e.g., identifiers beginning with an underscore). So my makefile looks something like this:

target: ...
verify.py
$(CC) ...

verify.py is a python script that checks for convention violations, i.e., its first line is

#! /usr/bin/env python

I can't figure out the following:
1. How can I get the python script to return a value to make, so that if it decides that there are convention violations make will fail?
raise SystemExit(1)
2. How can I pass information from the makefile to the python script, e.g., the base directory to check?

Use command-line arguments. The Python equivalent of "argv" is
"sys.argv".

[Daniel Dittmar]

Efrat Regev wrote:

1. How can I get the python script to return a value to make, so that if it
decides that there are convention violations make will fail?
You can set the return code of your Python script through sys.exit (3)
2. How can I pass information from the makefile to the python script, e.g.,
the base directory to check?

Python side:
Commandline arguments can be read through the list sys.argv. Parsing of
commandline options can be done with the module optparse.

Makefile side:
I don't know if there is a special variable in GNU make for the
directory of the current target. Why don't you set the default for the
directory option to the current directory? Most Makefiles won't work
anyway if they are called from a different directory.

Daniel

[Efrat Regev]

"Efrat Regev" <ef*********@ya hoo.com> wrote in message
news:MK******** ************@ad elphia.com...

Hello,

I'd like to ask a question concerning a python script in a makefile.
...

Many thanks for the very useful (and very quick) answers!

Efrat

[Bart van Deenen]

Another option would be to move from Makefiles to AAP, the build
mechanism for vim. We did just that, and are very happy with it. Aap is
python based, so the kind of question you have is very easily handled
within the 'aap' file.

http://www.a-a-p.org/

Aap has the advantage that you don't need to define the dependencies
yourself, it understands C files, and does the work for you. Our
Makefile shrunk by a factor of 5 after converting to aap.

Highly recommended.

Bart van Deenen.