osmocom
/
libosmocore
mirror of https://gerrit.osmocom.org/libosmocore
11
0
Fork 0
Code Issues Releases Wiki Activity

Update doxygen main page for libosmo{core,gsm,vty} 

We should link to project homepage as well as put the library into the
wider Osmocom context.

Change-Id: I07ca57ecef0f36c87c9ebacc1e1507c217bdb25b
This commit is contained in:
Harald Welte 2017-06-12 15:40:52 +02:00
parent 2f984ea194
commit 7165880ac2
3 changed files with 36 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/application.c
View File

@ -34,6 +34,12 @@
* generic plugin interface, statistics counters, memory allocator,
* socket abstraction, message buffers, etc.
* \n\n
* libosmocodec is developed as part of the Osmocom (Open Source Mobile
* Communications) project, a community-based, collaborative development
* project to create Free and Open Source implementations of mobile
* communications systems. For more information about Osmocom, please
* see https://osmocom.org/
*
* Please note that C language projects inside Osmocom are typically
* single-threaded event-loop state machine designs. As such,
* routines in libosmocore are not thread-safe. If you must use them in
@ -53,6 +59,13 @@
* FITNESS FOR A PARTICULAR PURPOSE.
* \n\n
*
* \section sec_tracker Homepage + Issue Tracker
* The libosmocore project home page can be found at
* https://osmocom.org/projects/libosmocore
*
* An Issue Tracker can be found at
* https://osmocom.org/projects/libosmocore/issues
*
* \section sec_contact Contact and Support
* Community-based support is available at the OpenBSC mailing list
* <http://lists.osmocom.org/mailman/listinfo/openbsc>\n

13
src/gsm/gsm_utils.c
View File

@ -41,6 +41,12 @@
* routines in libosmogsm are not thread-safe. If you must use them in
* a multi-threaded context, you have to add your own locking.
*
* libosmogsm is developed as part of the Osmocom (Open Source Mobile
* Communications) project, a community-based, collaborative development
* project to create Free and Open Source implementations of mobile
* communications systems. For more information about Osmocom, please
* see https://osmocom.org/
*
* \section sec_copyright Copyright and License
* Copyright © 2008-2011 - Harald Welte, Holger Freyther and contributors\n
* All rights reserved. \n\n
@ -55,6 +61,13 @@
* FITNESS FOR A PARTICULAR PURPOSE.
* \n\n
*
* \section sec_tracker Homepage + Issue Tracker
* libosmogsm is distributed as part of libosmocore and shares its
* project page at http://osmocom.org/projects/libosmocore
*
* An Issue Tracker can be found at
* https://osmocom.org/projects/libosmocore/issues
*
* \section sec_contact Contact and Support
* Community-based support is available at the OpenBSC mailing list
* <http://lists.osmocom.org/mailman/listinfo/openbsc>\n

10
src/vty/vty.c
View File

@ -14,6 +14,12 @@
* routines in libosmovty are not thread-safe. If you must use them in
* a multi-threaded context, you have to add your own locking.
*
* libosmocovty is developed as part of the Osmocom (Open Source Mobile
* Communications) project, a community-based, collaborative development
* project to create Free and Open Source implementations of mobile
* communications systems. For more information about Osmocom, please
* see https://osmocom.org/
*
* \section sec_copyright Copyright and License
* Copyright © 1997-2007 - Kuninhiro Ishiguro\n
* Copyright © 2008-2011 - Harald Welte, Holger Freyther and contributors\n
@ -29,6 +35,10 @@
* FITNESS FOR A PARTICULAR PURPOSE.
* \n\n
*
* \section sec_tracker Homepage + Issue Tracker
* libosmovty is distributed as part of libosmocore and shares its
* project page at http://osmocom.org/projects/libosmocore
*
* \section sec_contact Contact and Support
* Community-based support is available at the OpenBSC mailing list
* <http://lists.osmocom.org/mailman/listinfo/openbsc>\n