Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

batchbuild issues with backticked commands

<< < (9/9)

tiwag:

--- Quote from: Takeshi Miya on October 18, 2006, 11:45:00 pm ---In short, sending long messages to stderr and one-liners to stdout is what you suggest and what gcc does, for instance?

--- End quote ---

yes

maybe just "wx-config ERROR: 01 : error description ..." to stdout, this will then be seen in the buildlog,
the long text to stderr

you can test, what wx-config does on linux ?

brgds, tiwag

tiwag:
thread title changed, batchbuild isn't broken  :)

mandrav:
Regarding the envvars plugin, rev.3109 contains the fix.
As part of an optimization implemented some time ago, only the compiler plugin was allowed to load in batch-build mode. Rev.3109 adds control over this by adding a checklist of plugins to load in batch build options (Settings->Compiler&debugger->Batch builds). This is the master list for batch-build mode, i.e. for a plugin to be loaded in this mode it must be checked in that list and enabled in the plugin management dialog.
Defaults to only loading the compiler plugin.

As you can understand, it is no longer necessary to even create a separate profile/personality for batch builds, since usually you create a different profile only to disable most of the plugins ;).

I haven't tested this so if you can test it you 'd be doing me a favour :).

tiwag:

--- Quote from: mandrav on October 19, 2006, 10:28:46 am ---I haven't tested this so if you can test it you 'd be doing me a favour :).

--- End quote ---
it's working fine, thanks !


--- Quote from: mandrav on October 19, 2006, 10:28:46 am ---As you can understand, it is no longer necessary to even create a separate profile/personality for batch builds, since usually you create a different profile only to disable most of the plugins ;)
--- End quote ---
in general you are right, but it's not entirely true,
my differences (beside the plugins) betweeen development and batch-build profiles are additionally

                        devel               batchbuild
compiler logging        full                short   
dual monitor setup      main screen         secondary screen


brgds, tiwag

takeshimiya:

--- Quote from: tiwag on October 19, 2006, 12:22:01 am ---maybe just "wx-config ERROR: 01 : error description ..." to stdout, this will then be seen in the buildlog,
the long text to stderr

--- End quote ---

Fixed all in Rev.21 :)
* Removed all back-ticks characters from explanatory messages to prevent self-referencing back-ticks.
* Now explanatory messages are printed to stderr and one-line message errors are printed to stdout
   with the format "wx-config Error: description".

Navigation

[0] Message Index

[*] Previous page

Go to full version