DavidGH wrote:mkorhonen wrote:
Running program: /usr/bin/codelite_xterm 'bin/packet-daemon_unit_test --gtest_filter='Mp4ParserTest.youtube_hd_moov' ' '/bin/sh -f /usr/bin/codelite_exec LD_LIBRARY_PATH=../vendor/qpid/target/arch/x86_64/lib:/home/MATTER/mkorhonen/svn/sw/sw/branches/qsrv-dev/protocol_buffers/target/arch/x86_64/lib:../vendor/boost/target/arch/x86_64/lib:../vendor/liburcu/target/arch/x86_64/lib:../vendor/tbb/target/arch/x86_64/lib/ bin/packet-daemon_unit_test --gtest_filter='Mp4ParserTest.youtube_hd_moov' '
Two thoughts:
- It was a good idea to paste that line into a normal terminal. Did you first cd to /home/MATTER/mkorhonen/svn_working/sw/sw/branches/qsrv-dev/chassis/packet_proc?
Yes I ran it from the .../packet_proc directory. If I don't run it in the correct directory, I get a different error message (which is expected): 'packet-daemon_unit_test not found'
DavidGH wrote:
You seem to have a lot of single-quotes there. Some are from CodeLite; try removing the others/escaping them/changing them to double-quotes/
[/list]
Regards,
David
Thanks for the feedback. I tried the following:
1. Removing the program argument [--gtest_filter='Mp4ParserTest.youtube_hd_moov'] "fixed" the problem; an xterm window opened when I hit CTRL-F5 and the program ran in it.
2. I tried adding the program argument [--gtest_filter='Mp4ParserTest.youtube_hd_moov' ] back and reproduced the issue. CTRL-F5 doesn't run launch an xterm window, but I can copy and paste the /usr/bin/codelite_xterm line in a terminal and it works
3. I noticed that I accidentally had a space after the last single quote in (2). I tried fixing this using the program argument [--gtest_filter='Mp4ParserTest.youtube_hd_moov'], but this had the same behavior as (2).
4. I tried changing the single quotes to double quotes by using the program argument [--gtest_filter="Mp4ParserTest.youtube_hd_moov"]. This did launch an xterm window, but the application I'm using doesn't appear to support the double quotes.
5. I tried escaping the single quotes by using the program argument [--gtest_filter=\'Mp4ParserTest.youtube_hd_moov\']. This launched an xterm window with CTRL-F5, but it looks like the application didn't see the correct arguments. When I tried copying and pasting the /usr/bin/codelite_xterm line in a terminal, the single quotes weren't terminated correctly
6. I tried escaping the single quotes by using the program argument [--gtest_filter=\''Mp4ParserTest.youtube_hd_moov\'']. This didn't launch an xterm window with CTRL-F5; when I tried copying and pasting the /usr/bin/codelite_xterm line in a terminal, the application saw extra backslash characters in the commandline arguments
7. I tried the same program argument as (3) [--gtest_filter='Mp4ParserTest.youtube_hd_moov'], and changed Settings->Global Editor Preferences->Terminal to use double quotes by specifying this command: [/usr/bin/codelite_xterm "$(TITLE)" "$(CMD)"]. Both CTRL-F5 and copying-and-pasting had the same behavior: an xterm was launched, but the application didn't appear to recognize the commandline argument.
8. I tried the same program argument as (3) [--gtest_filter='Mp4ParserTest.youtube_hd_moov'], and changed Settings->Global Editor Preferences->Terminal to use this command: [$(CMD)]. CTRL-F5 didn't run the application (similar to the original problem). Copying-and-pasting allowed my to run the application on the shell
Can you think of anything else I can try? Let me know if you need more information.
Thanks!
Mark