command-line build: output to stdout instead of log ?

Question

fooling around w/ building our stuff from the osx command-line. i would love to get Unity's build output (and my own buildscript logging) into stdout instead of the unity log. it's much easier to grep it, capture it, etc that way.

the only t$$anonymous$$ng i've come up with is somet$$anonymous$$ng like t$$anonymous$$s in bash: <unity app> <options> & sleep .25 && tail -f <unity log> but it's pretty inelegant and it moves the unity build into a background thread where it can be unclear if it's still living or dead, etc.

Answer 1

Answer by iomac · Mar 24, 2017 at 03:29 AM

T$$anonymous$$nk t$$anonymous$$s was answered in another thread. Apparently adding '-logfile' to the build arguments (no argument) will cause all the logging to be written to STDOUT. (link below)

Redirecting Build Output to Console for Automated Builds

Add comment · Share

Answer 2

Answer by $$anonymous$$ · Aug 05, 2016 at 07:36 AM

I agree. We need to automate our build, but right now it's difficult to catch when build has completed, since Unity returns immediately and starts build in another process. Such behavior makes any type of automation a pain.

Add comment · Share

command-line build: output to stdout instead of log ?

2 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions