On Wed, Jun 15, 2016 at 5:19 AM, Peter Dimov
Rene Rivera wrote:
I've implemented a script to check for most of the library directory structure and integration requirements. The script runs as an additional CI job, currently in Travis. Here's one of those jobs < https://travis-ci.org/boostorg/boost/jobs/137506433>. At the moment it reports 17 libraries as having errors.
This
1564 libs/smart_ptr: warning: file found; Found extra files in [project-root]/include/boost directory.
can't be fixed - it will break all code depending on these headers.
Yeah.. Just ignore the warning for now then :-) I'll see about adding a way to document expected check warnings (and hence to avoid reporting them). This
1562 libs/smart_ptr: error: directory not found; Missing [project-root]/build directory. The [project-root]/build directory is required for libraries that have a [project-root]/src directory.
is a bit of a problem as smart_ptr is header-only and requires no building, so no build/, but it has optional source files in src/. I could rename src/ to something else, I suppose.
Hmm, interesting. What are the source files for? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail