On 3/2/06, William A. Hoffman <[EMAIL PROTECTED]> wrote:
At 10:20 AM 3/2/2006, Grant Tang wrote:>Hi,>>I have a mkdoc target, which is for extracting document information from all C/C++>and Python source files. I tried this setting:>>SET(MKDOCSRCS
>"@SOURCE_DIR@/subdir1/\\.(C|c|cpp|py)$">
At 10:20 AM 3/2/2006, Grant Tang wrote:
>Hi,
>
>I have a mkdoc target, which is for extracting document information from all
>C/C++
>and Python source files. I tried this setting:
>
>SET(MKDOCSRCS
>"@SOURCE_DIR@/subdir1/\\.(C|c|cpp|py)$"
>"@SOURCE_DIR@/subdir2/\\.(C|c|cpp|py)$"
Hi,
I have a mkdoc target, which is for extracting document information from all C/C++
and Python source files. I tried this setting:
SET(MKDOCSRCS
"@SOURCE_DIR@/subdir1/\\.(C|c|cpp|py)$"
"@SOURCE_DIR@/subdir2/\\.(C|c|cpp|py)$"
"@SOURCE_DIR@/subdir3/\\.(C|c|cpp|py)$"
OOOPS, wrong email. will post it again tomorrow.
Sorry.
On 3/1/06, William A. Hoffman <[EMAIL PROTECTED]> wrote:
Is this on the right list?At 09:01 PM 3/1/2006, Grant Tang wrote:>I just add a new target 'test' to EMAN2 makefile. Which is used to call all
>the python unit test file. All these test
I just add a new target 'test' to EMAN2 makefile. Which is used to call all
the python unit test file. All these test files will be installed to
EMAN2/test/rt directory.
So you can run unit test in one command:
$make test
after your make install.
Or you could go to EMAN2/test/rt directory run
