source code layout and organization

Steve Lime Steve.Lime at DNR.STATE.MN.US
Tue May 29 11:40:40 EDT 2007

I'd be very interested in code cleanup, but like Frank stuffing things into directories
doesn't seem that beneficial. I guarantee there are grey areas, for example, where 
do you put something like mapgml.c, ogc or formats?

I'd be more interested in a structure like:

      include/  (?)

So at least after a build the binaries are separated from the source code. All the configuration
files, READMEs and HISTORY.txt would live in the top level directory.

As for code clean-up, besides those already mentioned. 1) The msObj definition is a mess in 
maptemplate.h (I think I created a bug for that already) and 2)  mapimagemap.c has a lot of
leftovers from it's original coding.


>>> On 5/29/2007 at 8:14 AM, in message
<2576812186CDD411BF1500508B6DCE9511B30E9D at>,
"Kralidis,Tom [Burlington]" <Tom.Kralidis at EC.GC.CA> wrote:
> Hi,
> Does anyone have comments w.r.t. the organization of the codebase into
> something more palatable?  For example:
> mapserver/
>  etc/
>  core/
>  formats/
>  mapscript/
>  ogc/
>  tests/
>  util/
> This would be much easier now that MapServer is svn'd.
> This would also provide the opportunity to do a once over against files
> in the codebase (i.e. mapprojhack.c might deserve a more appropriate
> filename, or using mapmygis.c when MapServer can use OGR for VRT style
> and spatial connections).
> Any comments?
> ..Tom

More information about the mapserver-dev mailing list