7
100%
master: 100%

Ran 01 Jul 2018 10:49AM UTC

Files 23

Run time 1s

Badge

Embed ▾

Committed 01 Jul 2018 10:44AM UTC coverage: 100.0%. Remained the same

Job # COMPILER=g++-7 CXXFLAGS="-O0 --coverage -fno-inline -fno-inline-small-functions -fno-default-inline"

Build Type

Pull #107

travis-ci

Committed by

web-flow

Commit Message

Allow export of used Family template instantiation

Identifiers for components and co are generated via template
instantiation. If you have two separate compilation units like a library
and an application using this library which pass a Registry around you
really want to have both use the same identifier or you are in for a lot
of undefined behavior fun.

Using the same compiler (version) for both is a good first step, but you
will also need the template instantiation symbols to have public
visibility in the library so that the application can use them instead
of generating its own instances (with different Identifiers).

On Windows symbols are by default hidden in dlls, on Linux the default
tends to be public, but is easily changed by -fvisibility=hidden and
recommended for a respectable library.

Note that you don't need nor possibly want to export the Family
instances in a library if EnTT isn't part of your public interface.

Pull Request Pull Request #107: Allow export of used Family template instantiation for shared libraries

Coverage Stats

1670 of 1670 relevant lines covered (100.0%)

180.8 hits per line

skypjack / entt / 564 / 7
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 564.7 (COMPILER=g++-7 CXXFLAGS="-O0 --coverage -fno-inline -fno-inline-small-functions -fno-default-inline")

skypjack / entt / 564 / 7 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 564.7 (COMPILER=g++-7 CXXFLAGS="-O0 --coverage -fno-inline -fno-inline-small-functions -fno-default-inline")

skypjack / entt / 564 / 7
100%
master: 100%

README BADGES
x