On 21 January 2014 19:49, Andrew Hundt <[email protected]> wrote:
> CMake BASIS is a set of utilities and standards created with the goal of
> making CMake projects and libraries very easy to create, share, and reuse.
> It also integrates a lot of useful new CMake functionality such as
> documentation tools and automated packaging that a CMake user would
> otherwise have to implement themselves.
>
> Website: http://opensource.andreasschuh.com/cmake-basis/index.html
> GitHub: https://github.com/schuhschuh/cmake-basis/
> [...]

Andrew, this looks very interesting.
I have been very slowly growing something with similar, though much
more limited,
capabilities for one of projects I use (I'm tired of writing the same
boilerplate :-))
If I have moment, I'd like to check BASIS out in practice.

I quickly skimmed through the docs and I have question about the
Source Code Filesystem Heirarchy.

It is fairly common to have /include folder, so the structure looks like

- <source>/
  + src/
  + include/
  + config/
...

where all public headers live.

Is such layout supported by BASIS?

I see the minimum version of CMake is 2.8.4.
Does it mean BASIS does not support/use the Object Libraries feature?

Best regards,
-- 
Mateusz  Łoskot, http://mateusz.loskot.net
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to