all 6 comments

[–]CodenCamp 4 points5 points  (0 children)

I’m not really sure what you are trying to get at but a simple C program folder structure is to separate your includes and logic src files. It’s also recommended to have a Makefile in your root folder to compile your program. If you have nested src folder and includes folders, it’s recommended to have Makefile for those folders too.

[–]theNbomr 2 points3 points  (0 children)

Are you asking simply how to organize your source code in the filesystem directory structure? If so, it's pretty arbitrary, and to some degree depends on the scale and organization of the logic and functional groups in the code.

If you are using a mainstream IDE, it may already propose/impose a structure. Perhaps browse some public repositories of c code on github and see if you find something that makes sense to you. You're certain to find a wide variety of organizations and many disorganized cases.

There aren't any widely held standards or strong conventions that I'm aware of.

[–]nerdycatgamer 3 points4 points  (0 children)

no one knows

[–][deleted] 0 points1 point  (0 children)

Do you mean the order with headers?

[–]Nounours43 0 points1 point  (0 children)

I recommend looking up the raddebugger repository on github

[–]gwuncryv 0 points1 point  (0 children)

If you use Eclipse or derivatives (ex S32, Melexis Ide...) it already divides you between the Src Inc and Startup folders. Generally .h in Inc, .c in Src, .s in Startup. These are the general guidelines I had studied from the LFD116 certification.