Single folder source vs. foldered

[Baker]

[mh]

I prefer a single folder for everything. Relative paths for include files, having to move things around to keep stuff organised and so on becomes messy otherwise; there is a point at which the semblance of "organisation" actually becomes overhead and burden.

But I'm not religious on the matter; it's just the way I like to work and I do it for reasons that are right for me. Others may prefer different for reasons that are right for them, and that's cool.

[andrewj]

I just reorganised my Quake2 port to use a single folder, instead of the multiple folders of the original code. That's because I'm using Linux and command-line tools (ls and grep) are more convienent to use with a single folder.

The Quake2 arrangement was decent though, worthy of copying if you were to go the other way and multi-folderize the Quake code.

Oh yeah, if you want portable code then you should use / instead of \ in #include filenames

[Spike]

if your filenames carry some sort of prefix for their area of the engine, then it doesn't really make any difference at all.
the annoying thing with fte's code layout is that server things are no longer server only (due to csqc) and gl things are no longer gl only (due to d3d/general format support in servers). a lot of files ought to be renamed/moved in fte.
tbh, if it can be considered a separate and individual project/module, it should have a different directory, otherwise not.
obviously fte violate that. :)
but yeah, keep your libs and project files separate from the source and you're slightly better off next time visual stupio decides to delete all your files because they look like they ought to be temporary files anyway, despite being named foo.c
die msvc, die.
but yeah, independant modules, independant dirs, otherwise you find you need to use -r when using grep, and that's just extra typing

[frag.machine]

It's good to have some way to quickly identify a subsystem into the project (say, audio or network). As commented, folders may add burden when using tools like grep or diff, so maybe the use of a name prefix (sys_*, snd_*, net_*, etc) sounds like a better idea. OTOH may be wise to keep a different folder for third party libraries and their headers so you can easily handle your own code apart from the dependencies (specially in the case of cross platform projects).

[mh]

I've actually changed tack a little and have come to like organising code into subsystems within the IDE itself, but they don't necessarily need to correspond to folders in the filesystem. Don't need grep when I've got Ctrl-Shift-F (and Ctrl-Shift-H).

[Baker]

[Sajt]

An annoying thing about MSVC is that it puts all compiled .obj files in the same output directory. So if you have renderer_sw/world.c and renderer_gl/world.c, one will end up overwriting the other in Debug/world.c and the build will fail. This really (really) annoys me, and I'm not sure how to fix it other than manually specify an .obj path for every single source file in the project, which is silly.

[Baker]

[Feared]

[Sajt]

[qbism]

[Spike]

[Feared]

[mh]