Quote:
The key here is the case. Uppercase BUILD is ignored by default by mercurial, so won't be mistakenly checked in to a repository.
Not exactly, in my .hgignore I only have 2 rules nothing more.
Code:
glob:BUILD/*
glob:Binaries/Debug/*
Like a newcomer and hobbyist (I'm still learning GLSL which I wanted to learn long time a go... so), when I saw those sln files and have installed VS C++ 2010 (and C#), I clicked on them run and when building I get errors in the output about mismatched name and output... so I go for correcting errors
like this, and in a later post I explain how to add a "new project" with my assumptions about the migration changes to the properties of the project I have done... like you see there I have marqued them as deprecated and actually I'm writing about how to use cmake-gui for do the correct job: compile main sources and add your own source.
I think if a project provides a way to do things, then the ones that use it (yeah is like the tabs in python that some people say "why!!!!") should get used to it. That is why I request to forget sln files (and because compatibility issues with anterior and new VS 2010).
I have used previously cmake in Linux for some work and watching that there are CMakeLists.txt in folders doesn't have apealed me to use cmake, but instead to migrate first with the automatic wizard and then modifying "manually" the configurations.
About the adventages... they are mainly about structure personally I will like to see for example glfw in a top folder called externals or some like that.
But at less let me say that the main adventage is
- To add SET(THEBASE ${CMAKE_SOURCE_DIR}) to main CMakeLists.txt let 'know' in subfolders wher CMakeLists.txt is pressent where the real path is
Because is more easy to know where the other things are knowing the initial base, specially samples... (also I guess glfw could be inside a top "external" folder).
- Moving Content to THEBASE let you have only one Content dir which can be used for the extensions and the code base (I think they don't overlap), and samples, and maybe tutorials? without need to calculate 2 different paths (like the Terrain sample setup of content).
- Using only CMake let you choose if build or not Terrain, Samples.
That is why I say to forget sln files... shame that like I see for anterior VS and 2010 are named the same not like vcproj and vcxproj.
-------------- editActually asking I know this now...
CMAKE_SOURCE_DIR *is* the "top" directory, it remains the same even on subfolders.
CMAKE_CURRENT_SOURCE_DIR to get the subfolder's source dir.
So THEBASE is not necesary... so I guess you should use that info for rewrite some of the cmake files.