[CMake] Complete beginner question about tutorial

[David Aldrich]

Hi Arjen

Thanks for your answer.

Best regards

David

> -----Original Message-----
> From: Arjen Markus [mailto:arjen.markus at deltares.nl]
> Sent: 07 September 2010 15:07
> To: David Aldrich
> Cc: CMake at cmake.org
> Subject: Re: [CMake] Complete beginner question about tutorial
> 
> Hi David,
> 
> I would say put the CMakeLists.txt files under version control.
> This is what we do within the PLplot project and that is what I
> generally see: generated files are not managed, as you can always
> generate them again.
> 
> (For convenience you can put them in version control, for instance,
> to get people started rightaway. But then if they need to add a
> file or change compile options, they will have to use CMake again.
> If running CMake - or any other tool that generates files - is
> problematic, then putting such files in the distribution is
> one way out again.)
> 
> Regards,
> 
> Arjen
> 
> On 2010-09-07 15:24, David Aldrich wrote:
> > Hi Eike and Arjen
> >
> > Thanks for your answers. Sorry for my trivial question!
> >
> > I would like to ask a question about best practice. I think that,
> initially, we would use CMake only on Linux, to replace our hardcoded of
> gnu makefiles (we don't use autotools). So only one platform is involved.
> I am wondering what to put under version control. Would it be best to
> version control only CMakeLists.txt and let each developer separately run
> CMake and then make? Or should the modifier of CMakeLists.txt be
> responsible for running CMake and check-in the generated Makefile, so that
> the user only needs to update his (svn) working copy and run make?
> >
> > Best regards
> >
> > David
> >
> >> -----Original Message-----
> >> From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On
> Behalf
> >> Of Rolf Eike Beer
> >> Sent: 07 September 2010 13:11
> >> To: cmake at cmake.org
> >> Subject: Re: [CMake] Complete beginner question about tutorial
> >>
> >> Am Tuesday 07 September 2010 schrieb David Aldrich:
> >>> Hi
> >>>
> >>> I want to run the CMake tutorial
> >>> (http://www.cmake.org/cmake/help/cmake_tutorial.html).
> >>>
> >>> The tutorial appears not to show the CMake commands necessary to build
> >>> program. On Windows what command should I use to build the Tutorial
> >>> executable with Visual C++ 2008?
> >> You should create the programs with '-G "Visual Studio 9 2008"' to get
> a
> >> MSVC solution file. Load that one and just let it build.
> >>
> >> You could open a compiler console (Start -> Programs -> Microsoft
> Visual
> >> Studio 2008 -> Tools -> x86 command prompt (or something like that))
> and
> >> use '-G "NMake Makefiles"'. Then you would run "nmake" from that
> command
> >> window to build. You need to run cmake in that window or it will not be
> >> able to detect the proper compiler settings for nmake otherwise.
> >>
> >> Eike
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.cmake.org/mailman/listinfo/cmake
> >
> 
> 
> DISCLAIMER: This message is intended exclusively for the addressee(s) and
> may contain confidential and privileged information. If you are not the
> intended recipient please notify the sender immediately and destroy this
> message. Unauthorized use, disclosure or copying of this message is
> strictly prohibited.
> The foundation 'Stichting Deltares', which has its seat at Delft, The
> Netherlands, Commercial Registration Number 41146461, is not liable in any
> way whatsoever for consequences and/or damages resulting from the improper,
> incomplete and untimely dispatch, receipt and/or content of this e-mail.
> 
> 
> 
> 
> 
> 
>  Click
> https://www.mailcontrol.com/sr/oVYFfp6aJO3TndxI!oX7Uk4Sez3Gz8UuorlPT0KRpTX
> DNf1gB46MmTrsF!ZJR+qGvLNars4x0jXi5jK2rp2Ftw==  to report this email as
> spam.