"cross-running" boost tests
I've managed to cross-compile boost for BlackBerry10 devices. (Side-note: there is very little docs on cross compiling) Now, how would I go about "cross-running" the boost tests? In particular, can I hook into the unit-test and/or run rules of Boost.Build? Given a command line, I can load and run it on device and then retrieve the results, I just need to know where to hook in. Tony
Le 22/11/12 16:51, Gottlob Frege a écrit :
I've managed to cross-compile boost for BlackBerry10 devices. (Side-note: there is very little docs on cross compiling)
Now, how would I go about "cross-running" the boost tests?
In particular, can I hook into the unit-test and/or run rules of Boost.Build? I guess you should see how Boost.Build could support this.
Best, Vicente
On Thu, Nov 22, 2012 at 1:11 PM, Vicente J. Botet Escriba < vicente.botet@wanadoo.fr> wrote:
Le 22/11/12 16:51, Gottlob Frege a écrit :
I've managed to cross-compile boost for BlackBerry10 devices.
(Side-note: there is very little docs on cross compiling)
Now, how would I go about "cross-running" the boost tests?
In particular, can I hook into the unit-test and/or run rules of Boost.Build?
I guess you should see how Boost.Build could support this.
Best, Vicente
Right. That's kind of what I'm asking. Does Boost.Build support this already? Is there a way to hook into 'run'? I don't find Boost.Build (or docs) easy to use/understand, so my poking around at it didn't find anything, but I could have easily missed it. Tony
You could use testing.launcher, like this: b2 testing.launcher=my_custom_launcher It'll call my_custom_launcher to run your tests. On Thu, Nov 22, 2012 at 4:28 PM, Gottlob Frege <gottlobfrege@gmail.com>wrote:
On Thu, Nov 22, 2012 at 1:11 PM, Vicente J. Botet Escriba < vicente.botet@wanadoo.fr> wrote:
Le 22/11/12 16:51, Gottlob Frege a écrit :
I've managed to cross-compile boost for BlackBerry10 devices.
(Side-note: there is very little docs on cross compiling)
Now, how would I go about "cross-running" the boost tests?
In particular, can I hook into the unit-test and/or run rules of Boost.Build?
I guess you should see how Boost.Build could support this.
Best, Vicente
Right. That's kind of what I'm asking. Does Boost.Build support this already? Is there a way to hook into 'run'? I don't find Boost.Build (or docs) easy to use/understand, so my poking around at it didn't find anything, but I could have easily missed it.
Tony
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
That is along the right track. But I don't want to have to do that for every boost test file. This isn't for my own tests, I want to run the boost tests. I sort of need a global launcher that I can hook into. On Thu, Nov 22, 2012 at 1:40 PM, Paulo Márcio Figueiredo Alves < pauloalves1986@gmail.com> wrote:
You could use testing.launcher, like this: b2 testing.launcher=my_custom_launcher It'll call my_custom_launcher to run your tests.
On Thu, Nov 22, 2012 at 4:28 PM, Gottlob Frege <gottlobfrege@gmail.com>wrote:
On Thu, Nov 22, 2012 at 1:11 PM, Vicente J. Botet Escriba < vicente.botet@wanadoo.fr> wrote:
Le 22/11/12 16:51, Gottlob Frege a écrit :
I've managed to cross-compile boost for BlackBerry10 devices.
(Side-note: there is very little docs on cross compiling)
Now, how would I go about "cross-running" the boost tests?
In particular, can I hook into the unit-test and/or run rules of Boost.Build?
I guess you should see how Boost.Build could support this.
Best, Vicente
Right. That's kind of what I'm asking. Does Boost.Build support this already? Is there a way to hook into 'run'? I don't find Boost.Build (or docs) easy to use/understand, so my poking around at it didn't find anything, but I could have easily missed it.
Tony
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Hi Tony, On Thursday, 22. November 2012 15:27:46 Gottlob Frege wrote:
That is along the right track. But I don't want to have to do that for every boost test file.
This isn't for my own tests, I want to run the boost tests.
I sort of need a global launcher that I can hook into.
Well, that is exactly the purpose of "testing.launcher". I use this to start valgrind on all my test cases. Jamfile syntax is: <testing.launcher>"valgrind --leak-check=full --leak-resolution=high --track- origins=yes --error-exitcode=1 --gen-suppressions=all" and that would be on commandline: b2 testing.launcher="valgrind --leak-check=full ..." This will start all tests with valgrind. Handy for catching memory leaks, uninitialised variables and all the other things valgrind can detect. You really only need to write a wrapper script which does the necessary setup and stuff and use this as launcher skript Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
Ah, awesome. Thanks. I didn't realize you could pass that on the command line. Makes sense of course. I'm just not comfortable with boost build yet. Tony Sent from my BlackBerry® PlayBook™ www.blackberry.com ------------------------------ *From:* "Jürgen Hunold" <jhunold@gmx.eu> *To:* "boost-users@lists.boost.org" <boost-users@lists.boost.org> *Sent:* 23 November, 2012 2:54 AM *Subject:* Re: [Boost-users] "cross-running" boost tests Hi Tony, On Thursday, 22. November 2012 15:27:46 Gottlob Frege wrote:
That is along the right track. But I don't want to have to do that for
every boost test file.
This isn't for my own tests, I want to run the boost tests.
I sort of need a global launcher that I can hook into.
Well, that is exactly the purpose of "testing.launcher". I use this to start valgrind on all my test cases. Jamfile syntax is: <testing.launcher>"valgrind --leak-check=full --leak-resolution=high --track-origins=yes --error-exitcode=1 --gen-suppressions=all" and that would be on commandline: b2 testing.launcher="valgrind --leak-check=full ..." This will start all tests with valgrind. Handy for catching memory leaks, uninitialised variables and all the other things valgrind can detect. You really only need to write a wrapper script which does the necessary setup and stuff and use this as launcher skript Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany
participants (4)
-
Gottlob Frege -
Jürgen Hunold -
Paulo Márcio Figueiredo Alves -
Vicente J. Botet Escriba