Subject: Re: [boost] Cmake
From: John McFarlane (john_at_[hidden])
Date: 2017-06-24 17:50:12
On the subject of VS, has it been mentioned yet that VS2017 happily loads
CMake projects without the need for an .sln file? For sure, explicitly
building project files for older releases is a necessity but if you want to
promote uptake among fresh users with less expertise, *please* make sure
that when they open the Boost folder from VS2017, things works properly.
The same goes for CLion: just point it to a folder with CMakeLists.txt and
CLion is ready to compile, debug and test at the press of a button. Who
knows which other IDEs already provide this convenience or are planning to
in the near future?
On Sat, Jun 24, 2017 at 9:06 AM Rene Rivera via Boost <boost_at_[hidden]>
> On Sat, Jun 24, 2017 at 11:01 AM, Vinnie Falco via Boost <
> boost_at_[hidden]> wrote:
> > On Sat, Jun 24, 2017 at 9:00 AM, Rene Rivera via Boost
> > <boost_at_[hidden]> wrote:
> > > One of the issues that I've seen is that the generated project files
> > > just shells around cmake invocations of all kinds. As opposed to direct
> > > project declarations.
> > I haven't seen that (but if you say it exists I don't doubt it). My
> > cmake-generated projects are 100% authentic Visual Studio projects
> > which build on their own without invoking cmake. So it is possible, if
> > the library author wishes, to generate good .vcxproj files.
> Perhaps it depends on what features of cmake you use.. I only know enough
> cmake to deal with build problems in client projects. And the ones I've
> dealt with tend to use the gamut of cmake features. Particularly the
> install targets.
> -- Rene Rivera
> -- Grafik - Don't Assume Anything
> -- Robot Dreams - http://robot-dreams.net
> -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
> Unsubscribe & other changes: