Pavel Janík wrote:
>> Actually I think, the output should per default look like:
>>
>> compiling module/source/bla.cxx
>> compiling module/source/foo.cxx
>> linking module/unxlngi6.pro/lib/libgr.so
>
> Looks good. I'd like to see an option to do build this way at least. But
> sometimes both method
Philipp Lohmann wrote:
Hi,
to clean up the mess left by CWS headaburemove I will move all headers
left in vcl/inc to vcl/inc/vcl. This can be safely ignored by everybody
who does not change vcl code or at least not one of the headers
involved. Those who do the latter in their CWS please take car
hi!
in SRC680_m218 adding a fallback function to each shared library, just
stating that there is no description, was removed.
also generating component_getDescriptionFunc from a description.xml file
was removed too as it was unused for years.
tschau...
ause
Hi,
to clean up the mess left by CWS headaburemove I will move all headers
left in vcl/inc to vcl/inc/vcl. This can be safely ignored by everybody
who does not change vcl code or at least not one of the headers
involved. Those who do the latter in their CWS please take care that
when resyncing to
Hi Werner,
from where do you get the office installation? I remember that we have
had problems with distro builds of OpenOffice where the bootstrap
mechanism doesn't work because of some magic system integration stuff
of the distros. But i thought that these problems was solved at least
for
Actually I think, the output should per default look like:
compiling module/source/bla.cxx
compiling module/source/foo.cxx
linking module/unxlngi6.pro/lib/libgr.so
Looks good. I'd like to see an option to do build this way at least.
But sometimes both methods are good.
I upload full build l
Caolan,
Caolan McNamara wrote:
FWIW, I build with
build build-flags -- other-dmake-flags -s
I am going to try that ...
where the -s suppresses a goodly part of the output.
Actually I think, the output should per default look like:
compiling module/source/bla.cxx
compiling module/source/foo
Hi Stephan,
Stephan Bergmann wrote:
Undecided. For example, echoing of compiler command lines could be
helpful when a CWS owner tries to track down why a tinderbox built
broke, to see whether it is an issue of the tinderbox build environment
or an issue of the CWS...
It actually should be e
On Fri, 2007-06-15 at 12:19 +0100, Caolan McNamara wrote:
> FWYi, it *seems* that OOo's gtk theming and cairo 1.4.8 don't play well
> together causing:
>
> X-Error: RenderBadPicture (invalid Picture parameter)
> Major opcode: 154
> Minor opcode: 7
> Resource ID: 0x3800597
