These are chat archives for toeb/cmakepp

21st
Apr 2015
Tobias Becker
@toeb
Apr 21 2015 14:52
hello
Manu Sánchez
@Manu343726
Apr 21 2015 18:19
hi!
A markdown ready chat! Even displays tweets https://twitter.com/Manu343726/status/590579808431640578
Far better than having to put ellipsis each 140 chars...
So, what I'm thinking for cmakepp and biicode is:
Manu Sánchez
@Manu343726
Apr 21 2015 18:24
This message was deleted
This message was deleted
Manu Sánchez
@Manu343726
Apr 21 2015 18:35
  1. Continue with your current work on toeb/cmakepp repo. Whatever feature/issue we can help with, refer to your repo, use PRs, etc. Again, let's decouple bii completely from cmakepp

  2. Enter on biicode/biicode repo and share your thoughts there. The code is at biicode/client and biicode/client repos. Feel free to discuss any existing feature (please be critic with our work!), suggest new ideas, etc. Even you will be able to implement your own features (That depends on your python skills only, and the time you have to learn how bii works under the hood)

  3. Since bii runs on top of the build system, it has many information regarding dependencies that you doesn't have at the cmake level. For example, in a CMakeList.txt you cannot "look down" and see who is depending on you, but bii knows perfectly the complete dependency graph of the project. Consider what this kind of information can do for cmakepp features. We first should think about how the API between bii and the cmake side should look like (Again, ask biis about how bii works).