Skip to content

Commit 1923ba4

Browse files
committed
Add travis build badge to README
1 parent 1d0a548 commit 1923ba4

File tree

1 file changed

+7
-19
lines changed

1 file changed

+7
-19
lines changed

README.md

Lines changed: 7 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,21 +2,11 @@
22

33
Autowiring is an [inversion-of-control](http://en.wikipedia.org/wiki/Inversion_of_control) framework for C++11. It provides a declarative way to manage resources through [dependency injection](http://en.wikipedia.org/wiki/Dependency_injection). Instead of explicitly instantiating dependencies, simply declare what you need and Autowiring will manage object creation and wiring.
44

5-
# Platform Support
5+
# Build [![Build Status](https://travis-ci.org/leapmotion/autowiring.png)](https://travis-ci.org/leapmotion/autowiring)
66

7-
While Autowiring is written using C++11 features, it supports linking the non-C++11 STL. The `C++11/` directory provides [boost](http://www.boost.org/) shims for missing C++11 library features.
7+
Autowiring project structure is specified with [CMake](http://www.cmake.org/). Simply point CMake to the root project directory and generate your desired project file. While Autowiring is written using C++11 features, it supports linking the non-C++11 STL. The `C++11/` directory provides [boost](http://www.boost.org/) shims for missing C++11 library features.
88

9-
Supported Compilers:
10-
* Clang
11-
* GCC
12-
* VS2012+
13-
14-
# Build and Install Locally
15-
16-
Autowiring project structure is specified with [CMake](http://www.cmake.org/). Simply point CMake to the root project directory and generate your desired project file.
17-
18-
Mac
19-
----
9+
### Mac
2010

2111
Mac dependencies are installed with [port](http://guide.macports.org/) or [brew](http://brew.sh/). If you have port installed, this will build the project:
2212

@@ -28,8 +18,7 @@ Mac dependencies are installed with [port](http://guide.macports.org/) or [brew]
2818
make test
2919
sudo make install
3020

31-
Unix
32-
----
21+
### Unix
3322

3423
The commands for Unix are different depending on what package manager you're using. Ubuntu's package manager is apt-get, OpenSUSE uses zypper, and
3524
CentOS systems use yum. The major apparent difference to the user will be that the package to install has a different name. For Ubuntu, do this:
@@ -42,8 +31,7 @@ CentOS systems use yum. The major apparent difference to the user will be that
4231
make test
4332
sudo make install
4433

45-
Windows
46-
----
34+
### Windows
4735

4836
Unfortunately, Windows doesn't have any sort of nifty package manager, and this requires that you download and install the boost dependency by hand. Once
4937
you've followed the instructions for installing boost as indicated [here](http://www.boost.org/doc/libs/1_55_0/doc/html/bbv2/installation.html) you will
@@ -59,11 +47,11 @@ At this point, you'll have a solution file in your root directory called "Autowi
5947
target then Autowiring will be installed on your system. As with the other platforms, CMake will be able to find autowiring when it's installed this way
6048
via the [find_package](http://www.cmake.org/cmake/help/v3.0/command/find_package.html) command.
6149

62-
# Build the installer
50+
# Install
6351

6452
Autowiring uses CPack, which knows how to use rpm/deb/wix/dragndrop, and will target the correct version depending on which system you're on. To build
6553
the installer on Windows, you must first download the [wix toolset](http://wixtoolset.org/). Other CMake installations on the current system will be able
6654
to find Autowiring once the package is installed by this means.
6755

6856
Generally speaking, there is not really much reason to build an installer yourself unless you're testing out the bleeding edge. The
69-
[releases page](https://github.com/leapmotion/autowiring/releases) lists the officially supported Autowiring releases.
57+
[releases page](https://github.com/leapmotion/autowiring/releases) lists the officially supported Autowiring releases.

0 commit comments

Comments
 (0)