Boost logo

Boost-Build :

Subject: [Boost-build] [RFC] output events
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-02-18 05:20:44


Hi,

I've checked in, on a branch, a patch that makes Python port emit JSON-formatted message describing what is being built, like so:

{"properties": {"runtime-link": "shared", "main-target-type": "EXE", "hardcode-dll-paths": "true", "host-os": "linux", "user- interface":
"console", "stdlib": "native", "toolset-gcc:version": "4.8", "warnings-as-errors": "off", "symlink-location": "project-relative",
"exception-handling": "on", "pch": "on", "toolset": "gcc", "include": "util/foo/include", "runtime-debugging": "on", "profiling": "off",
"warnings": "on", "dll-path": "/home/ghost/Sources/boost/tools/build/example/libraries/util/foo/bin/gcc-4.8/debug", "inlining": "off",
"variant": "debug", "target-os": "linux", "link": "shared", "rtti": "on", "xdll-path":
"/home/ghost/Sources/boost/tools/build/example/libraries/util/foo/bin/gcc-4.8/debug", "extern-c-nothrow": "off", "debug-symbols": "on",
"install-dependencies": "off", "threading": "single", "optimization": "off", "asynch-exceptions": "on", "os": "linux2"}, "action-name":
"gcc.compile.c++", "targets": ["app/bin/gcc-4.8/debug/app.o"], "sources": ["app/app.cpp"], "token": 140050619569144, "type": "event",
"event": "build-action-started"}

{"output": "app/app.cpp: In function \u2018int main()\u2019:\napp/app.cpp:14:9: warning: unused variable \u2018x\u2019 [-Wunused-variable]\n
     int x;\n ^\n", "token": 140050619569144, "type": "event", "event": "build-action-output", "stream": 0}

{"exit-status": 0, "token": 140050619569144, "type": "event", "event": "build-action-finished"}

The ultimate goal of this is to make it more easy for an IDE to see what's happening - in particular, some time ago Mateusz was asking for
a way to discover include paths that Boost.Build uses, and there was no good answer.

The patch is at:

        https://github.com/boostorg/build/commit/f7aaa9539ff5cb2577916f5bbe0d9609e101f854

It's not final, but I though that before I get too carried away, I'd give everybody a chance to comment.

-- 
Vladimir Prus
http://vladimirprus.com

Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk