[haiku-bugs] Re: [Haiku] #8252: [PATCH] Create a "debug" build profile for use with Buildbot
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Tue, 20 Dec 2011 19:00:59 -0000
#8252: [PATCH] Create a "debug" build profile for use with Buildbot
----------------------------+----------------------------
Reporter: umccullough | Owner: bonefish
Type: enhancement | Status: new
Priority: normal | Milestone: R1
Component: Build System | Version: R1/Development
Resolution: | Keywords: buildbot debug
Blocked By: | Blocking:
Has a Patch: 1 | Platform: All
----------------------------+----------------------------
Comment (by bonefish):
Replying to [comment:5 umccullough]:
> Replying to [comment:3 mmadia]:
> > What happens when {{{ jam -q @debug }}} is run with {{{
HAIKU_ADD_ALTERNATIVE_GCC_LIBS ?= 1 ; }}}?
> >
> > Does the alternative_system_libs.zip get compiled with debugging?
>
> In theory, it should work, and they should include debug code I think
(since the variable is set for the directory structure and all targets
compiled from within in)...
I doubt that. The alternative gcc part is built in a sub-jam and besides
the list of optional packages nothing is propagated to it.
I'm undecided whether it is worth having this build profile at all. The
list of DEBUG exceptions could as well be moved to BuildSetup and then the
same effect could be reached by running
{{{
DEBUG=1 HAIKU_IMAGE_NAME=haiku-debug.image HAIKU_IMAGE_SIZE=650 jam @image
}}}
Since I can't think of anyone being interested in building such a debug
image that seems good enough to me.
The BBlockCache fix looks OK and could be applied regardless.
--
Ticket URL: <http://dev.haiku-os.org/ticket/8252#comment:6>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
