I just completed a PLPlot/wxwidgets build using VS 2017 and VCPKG without issue. Total build time was less than 15 minutes. If you built VCPKG on your system, run the following command to integrate it into your system. I built VCPKG on my desktop and ran it from there using a Visual Studio x64 Native Command Prompt: C:\Users\steve\Desktop\vcpkg-master>vcpkg integrate install
You should be greeted with following afterward: Applied user-wide integration for this vcpkg root.All MSBuild C++ projects can now #include any installed libraries. Linking will be handled automatically.Installing new libraries will make them instantly available.CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=C:/Users/steve/Desktop/vcpkg-master/scripts/buildsystems/vcpkg.cmake" Next, I searched for the correct package with: C:\Users\steve\Desktop\vcpkg-master>vcpkg search plplot And was presented with the following packages: plplot 5.13.0-1 PLplot is a cross-platform software package for creating scientific plots whos...plplot[wxwidgets] plplot wxwidgets module Next, I invoked the build process for PLPlot/wxwidgets with: C:\Users\steve\Desktop\vcpkg-master>vcpkg install plplot[wxwidgets]:x64-windows And the resulting console output is below: The following packages will be built and installed: plplot[core,wxwidgets]:x64-windows * wxwidgets[core]:x64-windowsAdditional packages (*) will be modified to complete this operation.Starting package 1/2: wxwidgets:x64-windowsBuilding package wxwidgets[core]:x64-windows...-- Downloading https://github.com/wxWidgets/wxWidgets/archive/v3.1.1.tar.gz...-- Extracting source C:/Users/steve/Desktop/vcpkg-master/downloads/wxWidgets-wxWidgets-v3.1.1.tar.gz-- Applying patch disable-platform-lib-dir.patch-- Using source at C:/Users/steve/Desktop/vcpkg-master/buildtrees/wxwidgets/src/v3.1.1-e6df9985ee-- Configuring x64-windows-- Building x64-windows-dbg-- Building x64-windows-rel-- Performing post-build validation-- Performing post-build validation doneBuilding package wxwidgets[core]:x64-windows... doneInstalling package wxwidgets[core]:x64-windows...Installing package wxwidgets[core]:x64-windows... doneElapsed time for package wxwidgets:x64-windows: 11.13 minStarting package 2/2: plplot:x64-windowsBuilding package plplot[core,wxwidgets]:x64-windows...-- Downloading https://sourceforge.net/projects/plplot/files/plplot/5.13.0%20Source/plplot-5.13.0.tar.gz/download...-- Extracting source C:/Users/steve/Desktop/vcpkg-master/downloads/plplot-5.13.0.tar.gz-- Applying patch C:/Users/steve/Desktop/vcpkg-master/ports/plplot/install-interface-include-directories.patch-- Configuring x64-windows-- Building x64-windows-dbg-- Building x64-windows-rel-- Installing: C:/Users/steve/Desktop/vcpkg-master/packages/plplot_x64-windows/share/plplot/copyright-- Performing post-build validation-- Performing post-build validation doneBuilding package plplot[core,wxwidgets]:x64-windows... doneInstalling package plplot[core,wxwidgets]:x64-windows...Installing package plplot[core,wxwidgets]:x64-windows... doneElapsed time for package plplot:x64-windows: 1.911 min Total elapsed time: 13.04 min The package plplot:x64-windows provides CMake targets: find_package(plplot CONFIG REQUIRED) target_link_libraries(main PRIVATE plplot csirocsa qsastime plplotcxx) This is by far the easiest method for building on Windows. Regards, Steve -- The quality of your thoughts will determine the quality of your life. On Thursday, October 17, 2019, 04:19:40 PM MST, David Bergman <stuntguitar1...@gmail.com> wrote: Stephan, perhaps you can help then. I have never had an easy time getting plplot to build and install with VS in my environment and right now my current build/install crashes when I close any app that uses plplot. I do not know why. But there is another reason and that is that my dell tower is not on-line and VS requires monthly renewal of the license for their Express or Community editions of the VS IDE. I may still be able to use the compilers but hadn't considered that. On 10/17/2019 6:54 PM, Ferrell, Stephen wrote: Is there a reason why you've moved from Visual Studio to MinGW and CodeBlocks? I've built several releases of PLPlot for Windows in the past using Visual Studio and had no problems. As Visual Studio is the most popular development environment for Windows, support for building PLPlot and its dependencies is a bit more solid and you'll find there are more folks out there who can lend a hand when you do run into a problem. I'd suggest switching back to VS unless you have some good reasons for switching to CodeBlocks/MinGW. -- The quality of your thoughts will determine the quality of your life. On Thursday, October 17, 2019, 03:09:27 PM MST, David Bergman <stuntguitar1...@gmail.com> wrote: I have the patch but the file changes indicated in the header do not match lines the appear in the /mingw/include/stdlib.h. I'm guessing that I have a different distribution, the one that comes with code blocks, and the c/c++ headers are not the same (though hopefully do the same thing). I agree that this is clearly not a widgets issue but I'm still including that group since you were able to help so far. I am very reluctant to edit the stdlib.h file I have if the line numbers and sample info do not match at all. Can you confirm which version of MinGW you applied the patch to? Perhaps I will just get that one, or another compiler supported by Code Blocks and start over. David On 10/17/2019 5:17 PM, Vadim Zeitlin wrote: > On Thu, 17 Oct 2019 17:06:09 -0400 David Bergman wrote: > > DB> Thank you. I had installed using codeblocks-17.12mingw-nosetup.zip > DB> which comes with the MinGW compiler (circa 12/2017). If I understand > DB> your comment correctly the bug will not be released until later, or is > DB> there an existing patch? > > Yes, it's linked from the ticket URL I gave in the previous reply: > > https://dotsrc.dl.osdn.net/osdn/ticket/g/m/mi/mingw/39658/5565/declare-rand_s.patch > > DB> Rather than edit plplot source might it be better do grab the most > DB> recent compiler or is that not stable? > > I'm not really sure, but adding a declaration to stdlib.h (i.e. applying > the patch above) should be the simplest. OTOH you could also just copy > rand_s declaration in the file which needs it in plplot and avoid modifying > MinGW headers at all. But this is really not wx-related at all any more... > > DB> Doing the rand fix just exposed another bug related to seed (see > DB> below). Is there a list of all possible changes needed? Or is it safe > DB> to say any related to the _WIN32 condition, or rand() generators? > DB> > DB> David > DB> > DB> [ 79%] Building CXX object > DB> drivers/CMakeFiles/wxwidgets.dir/wxwidgets_dev.cpp.obj > DB> C:\temp\src\plplot-5.15.0\drivers\wxwidgets_dev.cpp: In constructor > DB> 'Rand::Rand()': > DB> C:\temp\src\plplot-5.15.0\drivers\wxwidgets_dev.cpp:647:25: error: > DB> 'rand_s' was not declared in this scope > DB> rand_s( &m_seed ); > > This seems to be exactly the same problem. > > Regards, > VZ > -- David Bergman David R Bergman Music LLC "Have Guitar Will Travel" Morristown NJ 551-655-4720 stuntguitar1...@gmail.com www.davidrobertbergmanmusic.com --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general -- David Bergman David R Bergman Music LLC "Have Guitar Will Travel" Morristown NJ 551-655-4720 stuntguitar1...@gmail.com www.davidrobertbergmanmusic.com | | Virus-free. www.avast.com | _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
_______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
