To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=84497


User mmeeks changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'kr,rene,rt'              |'kr,mh,rene,rt'
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Tue Dec 18 15:35:43 +0000 
2007 -------
> I think providing the command line in case of an error is quite helpful

Sure - it's also not difficult at all - but it is esthetically challenging -
consequently, it's necessary to get release-engineering to comment on the style
of makefile rule they would prefer. I propose:

$(OBJ)$/%.obj : %.cpp
maps to:
OBJ_OBJ_CPP = $(QUIET_BUILD) $(CAPTURE_COMMAND) $(CXX) $(ACT_PCH_SWITCHES)
$(CFLAGS) $(INCLUDE) $(CFLAGSCXX) $(CFLAGSCXXSLO) $(CFLAGSSLO) $(CDEFS)
$(CDEFSSLO) $(CDEFSMT) $(!eq,$(EXCEPTIONSFILES),$(subst,$@, $(EXCEPTIONSFILES))
$(LOCAL_EXCEPTIONS_FLAGS) $(GLOBAL_EXCEPTIONS_FLAGS)) $(CFLAGSAPPEND)
$(CFLAGSOUTOBJ) $(SLO)$/$*.o $(CFLAGSINCXX)$(PWD)$/$*.cxx $(CAPTURE_OUTPUT)

...
        @$(OBJ_OBJ_CPP) || echo "Failed command $(OBJ_OBJ_CPP)"

or somesuch ? - the problem being that there is already a fair amount of command
duplication out there, or, even use some form of this pattern to try to reduce
the rampant (presumably fragile) cut & paste in rules.mk.

Either way - there are now ~4 questions wrt. "how to do this" for releng, as I
say, it seems conceptually easy to do, albeit some amount of typing, but this is
not our code to maintain, so proceeding without input seems pointless:

Martin ? Heiner ?


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to