DCL directory tree structure

Owned by David Harms
Last updated: Apr 26, 2013Version comment

The DCL directory tree structure looks like this (with the possibility of later additions:

This directory structure is designed to serve the purposes of the DCL, not necessarily to mimic the Clarion approach in every detail.

.git

The .git directory (which you may not see as it's hidden) contains your local Git DCL repository.

bin

The bin directory contains DevRoadmapsClarion.DLL, which is automatically copied from the build directory.

You won't see any "win" subdirectories, e.g. under bin, lib, libsrc, and template. I thought about putting them in but they seemed like unnecessary clutter since these directories live outside the Clarion directories anyway.

build

The build directory contains the project used to create DevRoadmapsClarion.DLL and DevRoadmapsClarion.LIB.

clariontest

Unit testing is an important part of almost all my class development, so yes, the DCL includes all the source code for the ClarionTest utility. Until recently ClarionTest was an app, but to make it easier to track changes (and avoid unexpected dependencies on templates that may or may not be registered) I've moved it to source code only. There's still a lot of cleaning up to do.

lib

The bin directory contains DevRoadmapsClarion.LIB, which is automatically copied from the build's release or debug directory, whichever has the more recent copy of the file.

libsrc

The libsrc directory contains all of the class and associated source files.

template

The template directory is home to the templates needed to create ClarionTest DLLs.

UnitTests

The UnitTests directory contains ClarionTest.exe and its supporting DLLs. Individual unit test apps are in their respective subdirectories. 

Â