search

Manu343726 / Turbo

C++11 metaprogramming library
MIT License
111 stars 14 forks source link

What happens to the CMakeLists.txt files ? #2

Open canercandan opened 10 years ago

canercandan commented 10 years ago

Except an obsolete version of the Makefile file in the root of the project that had been generated by CMake, there is no CMakeLists.txt, did you remove them by mistake ?

Manu343726 commented 10 years ago

The project was refactored to be used with the biicode dependency management tool, which is a file-based dependencies manager for C and C++. The project was rearranged on three blocks (A block is the unit of code sharing on biicode) one for the main library (turbo_core), one for the library utils (turbo_utils), and one for compile-time computing (turbo_computing). You can see them here.

biicode uses cmake to resolve the dependencies and build the blocks, thats why you are seeing cmake output folders on the project. Each block has its own CMakeLists.txt for block building and deps configuration. The spurious and outdated makefile at the root directory is the makefile used by netbeans, which is the IDE I usually use for C++ development.

I know I should configure the .gitignore correctly to hide all that garbage files, but at this time I have no enough time. Sorry for the mistakes, and thanks a lot for pointing the problems out.

canercandan commented 10 years ago

Thanks for your answer, it's a bit confusing to me. When i saw the cmake files as a regular user of cmake i thought the project was using it. As you also mentioned i think you should remove all the generated output files as well as we obviously doing for binary files i use one and only one building system to remove ambiguity. Le 1 oct. 2014 11:39, "Manu343726" notifications@github.com a écrit :

The project was refactored to be used with the biicode https://www.biicode.com/ dependency management tool, which is a file-based dependencies manager for C and C++. The project was rearranged on three blocks (A block is the unit of code sharing on biicode) one for the main library (turbo_core), one for the library utils (turbo_utils), and one for compile-time computing (turbo_computing). You can see them here https://www.biicode.com/search?q=turbo_core.

biicode uses cmake to resolve the dependencies and build the blocks, thats why you are seeing cmake output folders on the project. Each block has its own CMakeLists.txt for block building and deps configuration. The spurious and outdated makefile at the root directory is the makefiles used by netbeans, which is the IDE I usually use for C++ development.

I know I should configure the .gitignore correctly to hide all that garbage files, but at this time I have no enough time. Sorry for the mistakes, and thanks a lot for pointing the problems out.

— Reply to this email directly or view it on GitHub https://github.com/Manu343726/Turbo/issues/2#issuecomment-57440465.

Manu343726 commented 9 years ago

Now biicode has a simple layout setup which is not intrusive within your project (No blocks/ deps/, etc folders are required), maybe it's time to go back to the good old src/ layout.