1 files changed, 31 insertions, 0 deletions
diff --git a/devel/cmockery/DETAILS b/devel/cmockery/DETAILS
new file mode 100755
index 0000000000..f8dcd31081
--- /dev/null
+++ b/devel/cmockery/DETAILS
@@ -0,0 +1,31 @@
+           SPELL=cmockery
+         VERSION=0.1.2
+          SOURCE="${SPELL}-${VERSION}.tar.gz"
+   SOURCE_URL[0]=https://${SPELL}.googlecode.com/files/${SOURCE}
+     SOURCE_HASH=sha512:b58723a98ed321fce4d3d1d4ba4c29e7272a19c7e103c5f1437002ddbf11c0a19b19c3d0c3ae5447748013214599123c74b383412e2cead95c4f317859037415
+SOURCE_DIRECTORY="${BUILD_DIRECTORY}/${SPELL}-${VERSION}"
+        WEB_SITE="https://code.google.com/p/cmockery/"
+      LICENSE[0]="Apache2"
+         ENTERED=20141123
+        KEYWORDS=""
+           SHORT="Lightweight Unit Test library for C"
+cat << EOF
+There are a variety of C unit testing frameworks available however many of
+them are fairly complex and require the latest compiler technology. Some
+development requires the use of old compilers which makes it difficult to
+use some unit testing frameworks. In addition many unit testing frameworks
+assume the code being tested is an application or module that is targeted
+to the same platform that will ultimately execute the test. Because of
+this assumption many frameworks require the inclusion of standard C library
+headers in the code module being tested which may collide with the custom
+or incomplete implementation of the C library utilized by the code under test.
+
+Cmockery only requires a test application is linked with the standard C
+library which minimizes conflicts with standard C library headers. Also,
+Cmockery tries to avoid the use of some of the newer features of C compilers.
+
+This results in Cmockery being a relatively small library that can be used
+to test a variety of exotic code. If a developer wishes to simply test an
+application with the latest compiler then other unit testing frameworks may
+be preferable.
+EOF