Hello,
I am thinking about a better source layout structure, and the best
solution I have come up is something like this:
.
|-- apps
| `-- announcement
| |-- Announcement.cpp
| |-- Announcement.h
| |-- doc
| | `-- announcement.txt
| `-- etc
|-- codecs
| |-- g711
| |-- gsm
| `-- ilbc
|-- components
| |-- diameter_client
| |-- session_timer
| |-- stats
| |-- wav
| `-- xmlrpc2di
|-- core
| |-- amci
| | `-- amci.h
| `-- sems.cpp
|-- doc
| |-- COMPILING
| |-- COPYING
| `-- doxyref.h
`-- examples
|-- announce_auth
| `-- doc
|-- myannounceapp
`-- myconfigurableapp
(here with some example files only).
As Peter suggested some time back, 'examples/tutorial' have collapsed
into 'examples', the readme file goes into the app's directory (doc/
subdir) and the modules from core/plug-in are properly sorted in.
The advantage is that it is easier to find things; the disadvantage is
that patches from older versions/branches are little harder to merge.
Any comments, suggestions?
thanks
Stefan
--
Stefan Sayer
VoIP Services
[EMAIL PROTECTED]
www.iptego.com
IPTEGO GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
