[sr-dev] Restructuring source code tree for v5.0
Daniel-Constantin Mierla
miconda at gmail.com
Mon Dec 5 11:25:39 CET 2016
On 05/12/2016 10:26, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The result will look like:
>>
>> /Makefile (only-forwarding make commands to various subdirs)
>> /README|INSTAL|LICENSE|...
>> /src/Makefile* (build makefiles)
>> /src/main.c (main c file to generate the binary)
> Why not also place main.c in core/?
>
Most of the projects I have seen start with the main file of the
application (main.c, main.java, index.php, ...) in the root of src
folder and then group other files in subfolders. It is an intuitive way
to start navigating the source code, not having to "guess" in which
subfolders to look for main.c
Main reason for me: for the simplified version I found for upgrading the
build system (make file dependecies), this is the easy way. Afterwards,
one can jump in and do further work to upgrade makefiles and relocate
main.c.
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
More information about the sr-dev
mailing list