Re: [boost] python/test/Jamfile.v2 help needed

Subject: Re: [boost] python/test/Jamfile.v2 help needed
From: Ralf W. Grosse-Kunstleve (rwgk_at_[hidden])
Date: 2010-04-05 17:34:19

I think I figured it out: I moved the new "rule" block up in Jamefile.v2 .
Now monitoring the build summaries again...
Ralf

----- Original Message ----
From: Ralf W. Grosse-Kunstleve <rwgk_at_[hidden]>
To: boost_at_[hidden]
Sent: Mon, April 5, 2010 1:05:20 PM
Subject: Re: [boost] python/test/Jamfile.v2 help needed

The recent build summaries for boost.python come up all blank.
I'm guessing this is a bad sign.
Are the log files somewhere from which I could tell what's wrong?

Given boost svn trunk, I found out I can run bootstrap.sh to get
a bjam executable. But I couldn't figure out how to build and run the
python tests. Could some help with the commands I need? I have Fedora
6, 8, 11, 12.

Ralf

----- Original Message ----
From: Vladimir Prus <ghost_at_[hidden]>
To: boost_at_[hidden]
Sent: Sat, April 3, 2010 11:21:04 PM
Subject: Re: [boost] python/test/Jamfile.v2 help needed

Ralf W. Grosse-Kunstleve wrote:
> I've merged the current boost/python and libs/python trunk into the release branch,
> followed by this patch:
> 
> Index: libs/python/test/Jamfile.v2
> ===================================================================
> --- libs/python/test/Jamfile.v2 (revision 61033)
> +++ libs/python/test/Jamfile.v2 (working copy)
> @@ -184,8 +184,10 @@
>  #     bpl-test bienstman5 ;
>  # }
> 
> -[ bpl-test calling_conventions ]
> -[ bpl-test calling_conventions_mf ]
> +# XXX disabled on release branch only,
> +# XXX to avoid failures on platforms other than Windows
> +# [ bpl-test calling_conventions ]
> +# [ bpl-test calling_conventions_mf ]
> 
>  # --- unit tests of library components ---
> 
> 
> Is it possible to have those two tests built and run only under Windows?

Yes. Create a function as follows (in your Jamfile):

    rule require-windows ( properties * )
    {
        if ! <target-os>windows in $(properties)
        {
            return <build>no ;
        }
    }

then, in requirements of your tests, use <conditional>@require-windows, e.g:

    [ bpl-test calling_conventions : : <condiitonal>@require-windows ]

Note that cygwin is a different OS from windows, so if the test must be run on
cygwin, you need to adjust conditional accordingly.

Does this help?

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost