When I try to import the gnuplot-iostream library, I get an error that the termios.h library cannot be found. I am working on Windows as I investigated those libraries are for UNIX
Hi, Ihave a problem error: building abseil:x86-windows failed with: BUILD_FAILED Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Thank you very much, it works. I tried several ways to plot using c++ on windows and VS2019 with no luck. In my case, it took almost 2 hours the "Boost Step". Thanks again, great work.
Hey, nice video. Something not strictly related to it: it is now weeks that I am trying to figure out why wt.exe (Terminal Preview) is so laggy on my laptot, specially when in Windows Powershell prompt. But then, at 2:35 (circa) I noticed that, as to me, running the simple "cd" command just took a while (which for me, changing driver takes even longer). May you have some ideas of why?
You need a space between the final and the ", otherwise the output graph sometimes is wrong (try with seed 42 for example) Other than that, great video! It is sad how complex this is
I'd like to make a backtesting, replay-mode, charting software, to manually test and analize price charts (price data of forex, stocks, indices, commodities, etc.), like Forex Tester 5, or TradingView replay mode. I want to develop this with C++, for my Windows computer, a desktop application. But I'm not sure if I should go with libraries like this, or libraries of 2D games, because I need to interact with the charts, I don't need static charts. What do you think? Thanks!
For dynamic charting you should avoid gnuplot. You're probably better off with something like plotly or bokeh and somehow connect the dataflow over sockets. e.g. your c++ program publishes data over a socket and subscribes in your python charting application. However, technically in that case they will be two separate apps, so its not totally clean. Check out the ZeroMQ video we did. If you find a simpler way of handling it, leave a comment because I'd be curious to know.
Hello, thanks for the guide, please tell me, maybe you can know what's the matter, but I don't have any third-party library in VS, even installed via NuGet. and in the gnu library it finds about 150 errors
likely you did not do vcpkg integrate install or you didn't select the correct configuration in visual studio for the libraries you installed (32 vs 64 bit)
Hi, Thank you for your turorial. I keep running in to problems. When I compile I get: "The application has failed to start because no qt platform plugin gnuplot ....." ( visual studio 2019) . Do you know why this happens?
Are you sure you typed the path EXACTLY as I did? If you can, try setting up a virtualbox windows instance, follow the directions. If it works in the VM, then the problem is platform specific to your host. In that case, it would be very difficult for me to diagnose.
Hello, can this be done with VScode? If so I am getting an error while installing the boost packages which says "error: in triplet x64-windows: Unable to find a valid Visual Studio instance Could not locate a complete Visual Studio instance" Any suggestions?
Hi, thanks for the tutorial. Just for general information, I faced two issues. Problem 1: Installing boost via vcpkg threw a build error for the openssl package. All the other packages worked fine. Could very well be that this is an error due to my windows 8.1 machine. Fix 1: I ignored it.. For plotting I think this package is not needed. Problem 2: For some reason, the install did not include the packages boost-iostreams. Going by alphabet, they should be installed prior to the openssl package that caused an error. So no idea why they were not installed. Fix: I had to install them seperately afterwards using powershell. Rest seems to work fine. Thanks again :-)
@@pnumerics no problem. Followed the guide on a Windows 10 desktop PC and none of the errors/issues occurred. No error on the installation of openssl package. Package boost-iostreams was correctly included in the install. May have actually been an issue (at least in part) caused by my old Windows 8.1 OS. Thought I update on that.