Why build large projects by creating files and not visual studio assemblies?
I've been looking into build via makefiles and wondered if we can add multiple projects in visual studio as well, and then why we still prefer to use build via makefiles ....
Searched about this but couldn't find a clear answer.
Some of the things I've found is that with makefiles we can allocate a compiler for each module, etc.
If you know that, please tell me why we shouldn't use visual studio to create large projects and not to create files?
thank
source to share
My team uses makefiles to guide the automatic builds . Since most of our software is set to automatically build after 180 seconds of silence (after the last registration), the automated build agent uses a makefile to build it. Other software that is not under automated builds (typically at an earlier stage of development and under the direction of a single engineer) can be built safely from Visual Studio. But in a large team, this condition usually changes as the software matures, and we convert it into automated builds.
It is a high performing form of continuous integration .
In our case, it has less to do with the size of the project and more depends on the size of the team and the maturity of the project. VS built prototypes for one engineer; multi-engineer projects and mature software are in the process of being automated.
source to share