On 2016-10-09 02:27-0400 Pedro Vicente wrote: > ok, I see the issue now. > yes, it's possible to build each individual project in Visual Studio > > I just did a "build solution" , that builds all generated projects that were > generated by cmake > > the fix then is not to have cmake generate "generate_announcements" for > Windows, > not only this but others too that fail > > Build started: Project: create_staging_announce, > Build started: Project: check_plplotcapi_defines, > Build started: Project: create_staging, > Build started: Project: test_c_ps > Build started: Project: test_c_wingcc > Build started: Project: test_c_wxwidgets
Hi Pedro: The problem with your suggested fix is that Windows is actually many different platforms with a wide variety of generators. For example, if you used a generator that was not associated with visual studio such as "NMake Makefiles" then there would be no capability of indiscrimately building every target with one command so you would never encounter the trouble you are encountering above unless you specifically request some target that only works on platforms with Unix capabilities. Note also that many/all of the above targets would work on Windows platforms with Unix capabilites such as Cygwin, MinGW-w64/MSYS2, and MinGW/MSYS (although in those cases the associated make command is limited in the same way as the nmake case for Windows platforms without Unix capabilities, i.e., there is no overall target that automatically builds every target). So it is non-trivial to sort out which target will work on which platform/generator and even assuming I had the time/energy to figure that out, I would not want to complicate our build system with such filtering for the hundreds of different targets (some of which are quite experimental) that our build system configures. So instead what you should do is simply never do a "build solution" (which apparently from your remarks above indiscriminately attempts to build every target for visual studio). Instead, build well-known generic targets such as "all" (which is a misnomer because instead of building all targets it only builds the most important subset of the targets, e.g., the PLplot libraries, that should build without issues on all platforms) or "install" (which depends on "all" so all the "all"-related targets get built) and which also installs PLplot in the prefix location you have specified). Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
