问题
I have the following working code using _popen, on windows,
m_pGNUPlot = _popen("/gnuplot/bin/gnuplot.exe", "w");
fprintf(m_pGNUPlot, "set term win\n");
fprintf(m_pGNUPlot, "set term pngcairo\n");
fprintf(m_pGNUPlot, "plot \"\Data.txt\" using 1:2 notitle\n");
fprintf(m_pGNUPlot, "set output \"\Out.png\"\n");
fprintf(m_pGNUPlot, "replot\n");
fflush(m_pGNUPlot);
But the problem with this is that cmd window keeps poping up, and there is no way to prevent that (Link) So, I write the equivalent code in boost::process
bp::pipe m_Write;
bp::environment env = boost::this_process::environment();
m_Plot = new bp::child("/gnuplot/bin/gnuplot.exe", bp::std_in < m_Write, env, boost::process::windows::hide);
m_Write.write("set term win\n", sizeof(char)*14);
m_Write.write("set term pngcairo\n", sizeof(char) * 19);
m_Write("plot \"\Data.txt\" using 1:2 notitle\n", sizeof(char)*35);
m_Write("set output \"\Out.png\"\n", sizeof(char)*22);
m_Write.write("replot\n", sizeof(char) * 8);
So, my question is - are the two code snippets equivalent? And if so, why might the second one not work?
回答1:
I don't have windows, so I tested it on my linux box, slightly simplified:
#include <boost/process.hpp>
#include <iostream>
namespace bp = boost::process;
int main() {
bp::opstream m_Write;
boost::filesystem::path program("/usr/bin/gnuplot");
bp::child m_Plot(program, bp::std_in = m_Write);
m_Write << "set term png\n";
m_Write << "set output \"Out.png\"\n";
m_Write << "plot \"Data.txt\" using 1:2 notitle\n";
m_Write.flush();
m_Write.pipe().close();
m_Plot.wait();
std::cout << "Done, exit code: " << m_Plot.exit_code() << "\n";
}
Prints:
Done, exit code: 0
And created this nice image from simplistic data:
Windows
On windows, leverage the power of Boost Filesystem's path
to do the path:
boost::filesystem::path program("C:\\gnuplot\\bin\\gnuplot.exe");
Other Notes
If the whole script is, indeed, fixed, consider using a raw literal:
m_Write << R"(set term png
set output "Out.png"
plot "Data.txt" using 1:2 notitle)" << std::flush;
m_Write.pipe().close();
回答2:
Yes, thank you sehe! Boost is powerful, but lack of tutorials and examples make it hard to get started with.
Yes, so the final working code for me -
bp::opstream m_Write; //output stream to pipe
boost::filesystem::path program("/gnuplot/bin/gnuplot.exe");
m_Plot = new bp::child(program, bp::std_in = m_Write, bp::windows::hide); //this solves the problem with _popen
m_Write << "set term png\n";
m_Write << "set term pngcairo\n";
m_Write << "set output \"" + ToPosixPath(sPath) + "\"\n"; //Notice how this works with std::string :)
m_Write << "plot \"" + CreateTemp(X, Y) + "\" using 1:2 notitle\n";
m_Write << "exit\n";
m_Write.flush();
m_Write.pipe().close();
m_Plot->wait(); //boost doc states "The call to wait is necessary, to obtain it and tell the operating system, that no one is waiting for the process anymore."
delete m_Plot;
Some points-
In windows the exe that supports pipes in gnuplot.exe itself, whereas in linux there are two - gnuplot.exe and pgnuplot.exe.
Be sure to test your scripts in the GUI, this code fails silently! Return code will be 0.
来源:https://stackoverflow.com/questions/49509960/why-does-popen-work-here-but-boostprocess-does-not