| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I3f40a533a0762175dffda5df3bf79b6b4843cf33
|
|
Change-Id: Ic81a31d738bedcd6a35eb42d365dacc2af7ebe93
|
|
Change-Id: I9df137849a628089eb03b714d5f61e8d4084be17
|
|
so --enable-symbols gets -g in here with -O2
for gcc always add -fno-strict-aliasing
Change-Id: I8d673ebaf26d5afdcc5ae5de626cc7f32ffd6835
|
|
Change-Id: I930aacad47780a085ef8eec7f3b7fc6600528afb
|
|
ExternalProject usually involve a configure and a make
step that produce a bunch of output usually irrelevant
including a large number of warning and other mess.
now that everything is pretty much in tail_build
these output get interleaved with useful output from
the build of the product and actually drown them in a logorrhea
of messy noise.
This store the output of external modules in a log file
and only print them as a whole if the module failed do build.
on a non-verbose build.
Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647
Reviewed-on: https://gerrit.libreoffice.org/2304
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
|
|
Change-Id: I0f57a5a3f9d4f710715a478439e87409378f151e
|
|
We need to pass the location of the icu build root for the BUILD platform with
the --with-cross-build option when configuring icu for cross-compilation (to
the HOST platform). I.e. we always need to build it for the BUILD
platform. Surely this could be done in a more elegant way, but I got lost in
the mess, and just hacked it in the cross-toolset rule in Makefile.in.
Change-Id: Ia5e9d13d01067c6dded1fdc86c56f8f39aae6bc8
|
|
Change-Id: Id7d8bc05b1393cc2bae4a531c8a47f62df24b1d6
Reviewed-on: https://gerrit.libreoffice.org/1488
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
|
