ceedling 0.29.1 → 0.30.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA256:
-  metadata.gz: 57518fcd5eccaf61d4bf5b6953233e73bd09043d749c0c17e14bde86a448908c
-  data.tar.gz: ebb08f8cb40fc19ac1808fb5d5670e6323beaf8415681a97c9e0dc0ab37265b6
+SHA1:
+  metadata.gz: fc8dd93e8ebe1a71a578de9872004a69a221ee31
+  data.tar.gz: 5b7bf907d9d7c68e93c71f590ac583b7a5658d60
 SHA512:
-  metadata.gz: 5fc75ecfbd7c086f807fade3847511fc4208102a14ed4d3dd5a7be3302388bf6ac1be38eedcb87ff6c74654979bb9c30750c442a6ee20969209c156b6faabb7c
-  data.tar.gz: c00944a53e45f50e1cf7daca6400f428dce69456c7db3d29092e3641ff577c3aaefc23c347ad5174f88d2766276d3599d11494424c6fe491cd87a72971668e4c
+  metadata.gz: 8c98c9bd8c27304da3d61732f536791caf6cee7e8d92971ec65e1babb660fbd4a8f8111a865a871ae66e7eddf174582013a71aad2ad6ca08a9852d5582c51df4
+  data.tar.gz: 327a4da236d86d0752aae8e655833a9019aad1f06d84ab6d06d62511f96634bb95732692922a06d210f22e0975e1f6dbe11bb97c6e58a638c15c77b0cecbeaf0

data/Gemfile

@@ -1,16 +1,15 @@
-source "http://rubygems.org/"
-
-gem "bundler", ">= 1.3.5"
-gem "rake", ">= 12.2.1"
-
-gem "rspec", "~> 3.8"
-gem "require_all"
-gem "constructor"
-gem "diy"
-gem "rr"
-gem "thor"
-
-#these will be used if present, but ignored otherwise
-#gem "curses"
-#gem "pty",    :platforms => [ :ruby ] #automatically included on *nix platforms
-#gem "popen4", :platforms => [ :mswin ]
+source "http://rubygems.org/"
+
+gem "bundler"
+gem "rake"
+gem "rspec", "~> 3.8"
+gem "require_all"
+gem "constructor"
+gem "diy"
+gem "rr"
+gem "thor"
+
+#these will be used if present, but ignored otherwise
+#gem "curses"
+#gem "pty",    :platforms => [ :ruby ] #automatically included on *nix platforms
+#gem "popen4", :platforms => [ :mswin ]

data/Gemfile.lock

@@ -5,7 +5,7 @@ GEM
     diff-lcs (1.3)
     diy (1.1.2)
       constructor (>= 1.0.0)
-    rake (12.3.2)
+    rake (12.3.3)
     require_all (1.3.3)
     rr (1.1.2)
     rspec (3.8.0)

data/README.md

@@ -1,107 +1,108 @@
-Ceedling - Build/Test System for C Based on Ruby/Rake
-=====================================================
-
-[![Ceedling Build Status](https://api.travis-ci.org/ThrowTheSwitch/Ceedling.png?branch=master)](https://travis-ci.org/ThrowTheSwitch/Ceedling)
-
-Ceedling is a build system for C projects that is something of an extension around Ruby’s Rake (make-ish) build system. Ceedling also makes TDD (Test-Driven Development) in C a breeze by integrating [CMock](https://github.com/throwtheswitch/cmock), [Unity](https://github.com/throwtheswitch/unity), and [CException](https://github.com/throwtheswitch/cexception) -- three other awesome open-source projects you can’t live without if you're creating awesomeness in the C language. Ceedling is also extensible with a handy plugin mechanism.
-
-Usage Documentation
-===================
-
-Documentation and license info exists [in the repo in docs/](docs/CeedlingPacket.md)
-
-Getting Started
-===============
-
-First make sure Ruby is installed on your system (if it's not already). Then, from a command prompt:
-
-    > gem install ceedling
-
-(Alternate Installation for Those Planning to Be Ceedling Developers)
-======================================================================
-
-    > git clone --recursive https://github.com/throwtheswitch/ceedling.git
-    > cd ceedling
-    > bundle install # Ensures you have all RubyGems needed
-    > bundle exec rake # Run all CMock library tests
-
-If bundler isn't installed on your system or you run into problems, you might have to install it:
-
-    > sudo gem install bundler
-
-If you run into trouble running bundler and get messages like this `can't find gem
-bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)`, you may
-need to install a different version of bundler. For this please reference the
-version in the Gemfile.lock. An example based on the current Gemfile.lock is as
-followed:
-
-    > sudo gem install bundler -v 1.16.2
-
-Creating A Project
-==================
-
-Creating a project with Ceedling is easy. Simply tell ceedling the
-name of the project, and it will create a subdirectory called that
-name and fill it with a default directory structure and configuration.
-
-    ceedling new YourNewProjectName
-
-You can add files to your src and test directories and they will
-instantly become part of your test build. Need a different structure?
-You can start to tweak the `project.yml` file immediately with your new
-path or tool requirements.
-
-You can upgrade to the latest version of Ceedling at any time,
-automatically gaining access to the packaged Unity and CMock that
-come with it.
-
-    gem update ceedling
-
-Documentation
-=============
-
-Are you just getting started with Ceedling? Maybe you'd like your
-project to be installed with some of its handy documentation? No problem!
-You can do this when you create a new project.
-
-    ceedling new --docs MyAwesomeProject
-
-Bonding Your Tools And Project
-==============================
-
-Ceedling can deploy all of its guts into the project as well. This
-allows it to be used without having to worry about external dependencies.
-You don't have to worry about Ceedling changing for this particular
-project just because you updated your gems... no need to worry about
-changes in Unity or CMock breaking your build in the future. If you'd like
-to use Ceedling this way, tell it you want a local copy when you create
-your project:
-
-    ceedling new --local YourNewProjectName
-
-This will install all of Unity, CMock, and Ceedling into a new folder
-named `vendor` inside your project `YourNewProjectName`. It will still create
-the simple directory structure for you with `src` and `test` folders.
-
-SCORE!
-
-If you want to force a locally installed version of Ceedling to upgrade
-to match your latest gem later, it's easy! Just issue the following command:
-
-    ceedling upgrade --local YourNewProjectName
-
-Just like the `new` command, it's called from the parent directory of your
-project.
-
-Are you afraid of losing all your local changes when this happens? You can keep
-Ceedling from updating your project file by issuing `no_configs`.
-
-    ceedling upgrade --local --no_configs TheProject
-
-Git Integration
-===============
-
-Are you using Git? You might want to automatically have Ceedling create a
-`gitignore` file for you by adding `--gitignore` to your `new` call.
-
-*HAPPY TESTING!*
+Ceedling - Build/Test System for C Based on Ruby/Rake
+=====================================================
+
+[![Ceedling Build Status](https://api.travis-ci.org/ThrowTheSwitch/Ceedling.png?branch=master)](https://travis-ci.org/ThrowTheSwitch/Ceedling)
+
+Ceedling is a build system for C projects that is something of an extension around Ruby’s Rake (make-ish) build system. Ceedling also makes TDD (Test-Driven Development) in C a breeze by integrating [CMock](https://github.com/throwtheswitch/cmock), [Unity](https://github.com/throwtheswitch/unity), and [CException](https://github.com/throwtheswitch/cexception) -- three other awesome open-source projects you can’t live without if you're creating awesomeness in the C language. Ceedling is also extensible with a handy plugin mechanism.
+
+Usage Documentation
+===================
+
+Documentation and license info exists [in the repo in docs/](docs/CeedlingPacket.md)
+
+Getting Started
+===============
+
+First make sure Ruby is installed on your system (if it's not already). Then, from a command prompt:
+
+    > gem install ceedling
+
+(Alternate Installation for Those Planning to Be Ceedling Developers)
+======================================================================
+
+    > git clone --recursive https://github.com/throwtheswitch/ceedling.git
+    > cd ceedling
+    > bundle install # Ensures you have all RubyGems needed
+    > git submodule update --init --recursive # Updates all submodules
+    > bundle exec rake # Run all Ceedling library tests
+
+If bundler isn't installed on your system or you run into problems, you might have to install it:
+
+    > sudo gem install bundler
+
+If you run into trouble running bundler and get messages like this `can't find gem
+bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)`, you may
+need to install a different version of bundler. For this please reference the
+version in the Gemfile.lock. An example based on the current Gemfile.lock is as
+followed:
+
+    > sudo gem install bundler -v 1.16.2
+
+Creating A Project
+==================
+
+Creating a project with Ceedling is easy. Simply tell ceedling the
+name of the project, and it will create a subdirectory called that
+name and fill it with a default directory structure and configuration.
+
+    ceedling new YourNewProjectName
+
+You can add files to your src and test directories and they will
+instantly become part of your test build. Need a different structure?
+You can start to tweak the `project.yml` file immediately with your new
+path or tool requirements.
+
+You can upgrade to the latest version of Ceedling at any time,
+automatically gaining access to the packaged Unity and CMock that
+come with it.
+
+    gem update ceedling
+
+Documentation
+=============
+
+Are you just getting started with Ceedling? Maybe you'd like your
+project to be installed with some of its handy documentation? No problem!
+You can do this when you create a new project.
+
+    ceedling new --docs MyAwesomeProject
+
+Bonding Your Tools And Project
+==============================
+
+Ceedling can deploy all of its guts into the project as well. This
+allows it to be used without having to worry about external dependencies.
+You don't have to worry about Ceedling changing for this particular
+project just because you updated your gems... no need to worry about
+changes in Unity or CMock breaking your build in the future. If you'd like
+to use Ceedling this way, tell it you want a local copy when you create
+your project:
+
+    ceedling new --local YourNewProjectName
+
+This will install all of Unity, CMock, and Ceedling into a new folder
+named `vendor` inside your project `YourNewProjectName`. It will still create
+the simple directory structure for you with `src` and `test` folders.
+
+SCORE!
+
+If you want to force a locally installed version of Ceedling to upgrade
+to match your latest gem later, it's easy! Just issue the following command:
+
+    ceedling upgrade --local YourNewProjectName
+
+Just like the `new` command, it's called from the parent directory of your
+project.
+
+Are you afraid of losing all your local changes when this happens? You can keep
+Ceedling from updating your project file by issuing `no_configs`.
+
+    ceedling upgrade --local --no_configs TheProject
+
+Git Integration
+===============
+
+Are you using Git? You might want to automatically have Ceedling create a
+`gitignore` file for you by adding `--gitignore` to your `new` call.
+
+*HAPPY TESTING!*

data/Rakefile

@@ -1,11 +1,11 @@
-#!/usr/bin/env rake
-require 'bundler'
-require 'rspec/core/rake_task'
-
-desc "Run all rspecs"
-RSpec::Core::RakeTask.new(:spec) do |t|
-  t.pattern = 'spec/**/*_spec.rb'
-end
-
-task :default => [:spec]
-task :ci => [:spec]
+#!/usr/bin/env rake
+require 'bundler'
+require 'rspec/core/rake_task'
+
+desc "Run all rspecs"
+RSpec::Core::RakeTask.new(:spec) do |t|
+  t.pattern = 'spec/**/*_spec.rb'
+end
+
+task :default => [:spec]
+task :ci => [:spec]

data/assets/ceedling

@@ -1,3 +1,3 @@
-#!/bin/bash
-
-ruby vendor/ceedling/bin/ceedling $*
+#!/bin/bash
+
+ruby vendor/ceedling/bin/ceedling $*

data/assets/default_gitignore

@@ -1,5 +1,5 @@
-build/artifacts
-build/gcov
-build/logs 
-build/temp
-build/test
+build/artifacts
+build/gcov
+build/logs 
+build/temp
+build/test

data/assets/example_file.c

@@ -1,5 +1,5 @@
-#include "example_file.h"
-
-int add_numbers(int a, int b) {
-  return a + b;
-}
+#include "example_file.h"
+
+int add_numbers(int a, int b) {
+  return a + b;
+}

data/assets/example_file.h

@@ -1,6 +1,6 @@
-#ifndef EXAMPLE_FILE_H
-#define EXAMPLE_FILE_H
-
-int add_numbers(int a, int b);
-
-#endif /* EXAMPLE_FILE_H */
+#ifndef EXAMPLE_FILE_H
+#define EXAMPLE_FILE_H
+
+int add_numbers(int a, int b);
+
+#endif /* EXAMPLE_FILE_H */

data/assets/project_as_gem.yml

@@ -1,97 +1,101 @@
----
-
-# Notes:
-# Sample project C code is not presently written to produce a release artifact.
-# As such, release build options are disabled.
-# This sample, therefore, only demonstrates running a collection of unit tests.
-
-:project:
-  :use_exceptions: FALSE
-  :use_test_preprocessor: TRUE
-  :use_auxiliary_dependencies: TRUE
-  :build_root: build
-#  :release_build: TRUE
-  :test_file_prefix: test_
-  :which_ceedling: gem
-  :default_tasks:
-    - test:all
-
-#:test_build:
-#  :use_assembly: TRUE
-
-#:release_build:
-#  :output: MyApp.out
-#  :use_assembly: FALSE
-
-:environment:
-
-:extension:
-  :executable: .out
-
-:paths:
-  :test:
-    - +:test/**
-    - -:test/support
-  :source:
-    - src/**
-  :support:
-    - test/support
-
-:defines:
-  # in order to add common defines:
-  #  1) remove the trailing [] from the :common: section
-  #  2) add entries to the :common: section (e.g. :test: has TEST defined)
-  :common: &common_defines []
-  :test:
-    - *common_defines
-    - TEST
-  :test_preprocess:
-    - *common_defines
-    - TEST
-
-:cmock:
-  :mock_prefix: mock_
-  :when_no_prototypes: :warn
-  :enforce_strict_ordering: TRUE
-  :plugins:
-    - :ignore
-    - :callback
-  :treat_as:
-    uint8:    HEX8
-    uint16:   HEX16
-    uint32:   UINT32
-    int8:     INT8
-    bool:     UINT8
-
-# Add -gcov to the plugins list to make sure of the gcov plugin
-# You will need to have gcov and gcovr both installed to make it work.
-# For more information on these options, see docs in plugins/gcov
-:gcov:
-    :html_report: TRUE
-    :html_report_type: detailed
-    :html_medium_threshold: 75
-    :html_high_threshold: 90
-    :xml_report: FALSE
-
-#:tools:
-# Ceedling defaults to using gcc for compiling, linking, etc.
-# As [:tools] is blank, gcc will be used (so long as it's in your system path)
-# See documentation to configure a given toolchain for use
-
-# LIBRARIES
-# These libraries are automatically injected into the build process. Those specified as
-# common will be used in all types of builds. Otherwise, libraries can be injected in just
-# tests or releases. These options are MERGED with the options in supplemental yaml files.
-:libraries:
-  :placement: :end
-  :flag: "${1}"  # or "-L ${1}" for example
-  :test: []
-  :release: []
-
-:plugins:
-  :load_paths:
-    - "#{Ceedling.load_path}"
-  :enabled:
-    - stdout_pretty_tests_report
-    - module_generator
-...
+---
+
+# Notes:
+# Sample project C code is not presently written to produce a release artifact.
+# As such, release build options are disabled.
+# This sample, therefore, only demonstrates running a collection of unit tests.
+
+:project:
+  :use_exceptions: FALSE
+  :use_test_preprocessor: TRUE
+  :use_auxiliary_dependencies: TRUE
+  :build_root: build
+#  :release_build: TRUE
+  :test_file_prefix: test_
+  :which_ceedling: gem
+  :ceedling_version: '?'
+  :default_tasks:
+    - test:all
+
+#:test_build:
+#  :use_assembly: TRUE
+
+#:release_build:
+#  :output: MyApp.out
+#  :use_assembly: FALSE
+
+:environment:
+
+:extension:
+  :executable: .out
+
+:paths:
+  :test:
+    - +:test/**
+    - -:test/support
+  :source:
+    - src/**
+  :support:
+    - test/support
+  :libraries: []
+
+:defines:
+  # in order to add common defines:
+  #  1) remove the trailing [] from the :common: section
+  #  2) add entries to the :common: section (e.g. :test: has TEST defined)
+  :common: &common_defines []
+  :test:
+    - *common_defines
+    - TEST
+  :test_preprocess:
+    - *common_defines
+    - TEST
+
+:cmock:
+  :mock_prefix: mock_
+  :when_no_prototypes: :warn
+  :enforce_strict_ordering: TRUE
+  :plugins:
+    - :ignore
+    - :callback
+  :treat_as:
+    uint8:    HEX8
+    uint16:   HEX16
+    uint32:   UINT32
+    int8:     INT8
+    bool:     UINT8
+
+# Add -gcov to the plugins list to make sure of the gcov plugin
+# You will need to have gcov and gcovr both installed to make it work.
+# For more information on these options, see docs in plugins/gcov
+:gcov:
+  :reports:
+    - HtmlDetailed
+  :gcovr:
+    :html_medium_threshold: 75
+    :html_high_threshold: 90
+
+#:tools:
+# Ceedling defaults to using gcc for compiling, linking, etc.
+# As [:tools] is blank, gcc will be used (so long as it's in your system path)
+# See documentation to configure a given toolchain for use
+
+# LIBRARIES
+# These libraries are automatically injected into the build process. Those specified as
+# common will be used in all types of builds. Otherwise, libraries can be injected in just
+# tests or releases. These options are MERGED with the options in supplemental yaml files.
+:libraries:
+  :placement: :end
+  :flag: "-l${1}"
+  :path_flag: "-L ${1}"
+  :system: []    # for example, you might list 'm' to grab the math library
+  :test: []
+  :release: []
+
+:plugins:
+  :load_paths:
+    - "#{Ceedling.load_path}"
+  :enabled:
+    - stdout_pretty_tests_report
+    - module_generator
+...