Re: [chromium-dev] How to compile and run TabSwitchingUITest on Linux
Thank you. I tried to compile 'test_binary', but there is no such executable. $ make out/Debug/test_binary make: *** No rule to make target `out/Debug/test_binary'. Stop. $ ./out/Debug/test_binary bash: ./out/Debug/test_binary: No such file or directory And I tried to run 'automation_proxy_uitest' and that did not work either. $ make out/Debug/automation_proxy_uitest make: *** No rule to make target `out/Debug/automation_proxy_uitest'. Stop. On Fri, Dec 25, 2009 at 2:15 PM, Robert Sesek rse...@chromium.org wrote: The --gtest_filter switch should do what you want: ./test_binary --gtest_filter='TestClassName.*'. You can replace the .* with a specific test case name. The quotes are necessary if your shell expands the asterisk. Find out more with the --help flag. Also, I don't think TabSwitchingUITest is in base_unittests but rather its own binary (Debug/tab_switching_test), though I'm not sure about that. rsesek / @chromium.org On Fri, Dec 25, 2009 at 2:02 PM, n179911 n179...@gmail.com wrote: Hi, Here is how to compile and run all tests on linux: $make ./out/Debug/base_unittests $./out/Debug/base_unittests Can you please tell me how can I run 1 specific test, namely TabSwitchingUITest? Thank you. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] How to compile and run TabSwitchingUITest on Linux
test_binary was just an example. The target you want is named tab_switching_test. rsesek / @chromium.org On Sat, Dec 26, 2009 at 4:29 PM, n179911 n179...@gmail.com wrote: Thank you. I tried to compile 'test_binary', but there is no such executable. $ make out/Debug/test_binary make: *** No rule to make target `out/Debug/test_binary'. Stop. $ ./out/Debug/test_binary bash: ./out/Debug/test_binary: No such file or directory And I tried to run 'automation_proxy_uitest' and that did not work either. $ make out/Debug/automation_proxy_uitest make: *** No rule to make target `out/Debug/automation_proxy_uitest'. Stop. On Fri, Dec 25, 2009 at 2:15 PM, Robert Sesek rse...@chromium.org wrote: The --gtest_filter switch should do what you want: ./test_binary --gtest_filter='TestClassName.*'. You can replace the .* with a specific test case name. The quotes are necessary if your shell expands the asterisk. Find out more with the --help flag. Also, I don't think TabSwitchingUITest is in base_unittests but rather its own binary (Debug/tab_switching_test), though I'm not sure about that. rsesek / @chromium.org On Fri, Dec 25, 2009 at 2:02 PM, n179911 n179...@gmail.com wrote: Hi, Here is how to compile and run all tests on linux: $make ./out/Debug/base_unittests $./out/Debug/base_unittests Can you please tell me how can I run 1 specific test, namely TabSwitchingUITest? Thank you. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Modifying .gyp files
I used a custom action with success and I believe that sounds better for module updates purposes. We used to do things like that in the pre-GYP days. When we moved our builds over to GYP, we decided that it wasn't anywhere near worthwhile. It inflated build times (autoconf's configure is SLOW) and was difficult to capture dependency data properly and get the output in the right place. I don't recommend adding configure steps when you can configure once for the platforms you need and check the results in. I see. Well, if you see GYP as a self-contained tool, support for configure sounds pretty handy especially for those who do not care about first make call being slow. I'd say user might specify both input and output files (being optional). Is there a wishlist? I'd like to vote for support for both configure step and .proto files. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Modifying .gyp files
http://code.google.com/p/gyp/issues/list http://code.google.com/p/gyp/issues/listSearch for the issue or create a new one. ☆PhistucK On Sun, Dec 27, 2009 at 04:08, Igor Gatis igorga...@gmail.com wrote: I used a custom action with success and I believe that sounds better for module updates purposes. We used to do things like that in the pre-GYP days. When we moved our builds over to GYP, we decided that it wasn't anywhere near worthwhile. It inflated build times (autoconf's configure is SLOW) and was difficult to capture dependency data properly and get the output in the right place. I don't recommend adding configure steps when you can configure once for the platforms you need and check the results in. I see. Well, if you see GYP as a self-contained tool, support for configure sounds pretty handy especially for those who do not care about first make call being slow. I'd say user might specify both input and output files (being optional). Is there a wishlist? I'd like to vote for support for both configure step and .proto files. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
