Boost logo

Boost-Build :

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-02-22 14:22:46

Jody Hagins wrote:
> I have been trying this, and have several questions.
> How does this work if a test is already expecting a command line
> argument?

You can pass non input file arguments first, there's an "args" (the same
as the command line that unit-test has), to the run and run-fail rules.
As can be seen in the declaration...

rule run ( sources + : args * : input-files * : requirements * : name ?
: default-build * : args2 * )


rule run-fail ( sources + : args * : input-files * : requirements * :
name ? )

> How does the test know which are "input files" and which are
> normal command line arguments?

Depends on the argument you pass to the above.

> My tests currently are done with the unit-test rule. How do I convert
> them appropriately?

Use the run rule, and add the import of the testing module to you
Jamfile. Which is all that the deprecated unit-test rule does.

> What is INPUT_FILES really?

Literally, it's raw files and/or buildable targets whose path is passed
to the test program. Internally it's translated to the variant specific
full gristed id of the file or target.

> For example, if I have a DLL in the
> INPUT_FILES section, will it try to link it into the executable?

No it doesn't, and is why I added it to the input files. I knew you did
not want to have them linked in :-)



Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at