News in this version:
- Solve some limitations of walkthrough mode (fdo#81425)
- Multisampling (better rendering quality, mainly at the edges)
- Better error handling (no crash in case of invalid input file)
Change-Id: I46fdf56b00476614487fbcc04178e43e33a01794
Reviewed-on: https://gerrit.libreoffice.org/11179
Reviewed-by: Zolnai Tamás <tamas.zolnai@collabora.com>
Tested-by: Zolnai Tamás <tamas.zolnai@collabora.com>
In general glTF shader files does not contain version
directives and in some case it make shader compiler
using GLSL 1.1 which leads to that the shader compiler
fails.
So we need to append the choosen version number which is
GLSL 1.3 in case of libgltf, but this also means that
from that point OpenGL 3.0 is the new reuirements since
GLSL 1.3 is available only from that version.
Change-Id: Ic4382266432ea474aeb3e603b32a998b9aeed280
Here only handle precision. Using precision unconditionally
causing problems when shader source is compiled with GLSL 1.2.
The #version dircetives can be added by the glTF parser.
For example libgltf implementation:
https://gerrit.libreoffice.org/gitweb?p=libgltf.git;a=commit;
h=e4544a8b5ca8470a96bf28c6ccdb7461e78ca293
Change-Id: I934cdfa8651a8787fbcd476cea9892bf7e89dd11
That's why it was worked in some case, when OpenGL ES is
available then it is the default and not the GLSL 1.1.
Change-Id: I60d545e76115396433df8dc300bc13935099c776
It seems under linux we need to specify the version number
explicitly, because otherwise shader compiler will use GLSL 1.1
and will fail. Base line is GLSL 1.3 or OpenGL ES 3.0.
Change-Id: Ie143275ade8d6989fda055ab96943b25ef220e9d
There is only a single libmwaw switch to enable both "noopt + symbols"
and "debug messages", and we enable that switch in debug builds.
Backport upstream patch to avoid a debug message during type detection.
Change-Id: I53440ceed90529e3db7c9d91c788c7a3b2723eb1
I noticed in the debugger that this code tried to load a freebl dylib, but
after then making it link to the freebl entry point statically, I no longer
see it being entered. Huh, confusing. Making NSS work on iOS to the extent we
need is a pain.
Change-Id: Iafc3785752587c38566441f566e187859022733e
(hopefully, the various ccc script variants do not include code that would
unintentionally fail the script with -e)
Change-Id: Ia04291983d99a8cf5a74e6a0078e179c17a93f2b
Let's hope that the various static archives that get built by the NSS
build machinery contain what an iOS app that needs NSS services
requires. I patch out the construction of any dylibs and executables
in nss. We don't use any dylibs on iOS anyway, and of course don't
need any NSS executables either.
Change-Id: Ic977c6e3d6c4e953202e78f8e08c4e61f6c9cb1b
Otherwise those external projects will fail, because with only VS2013 installed
there is no ToolsVersion 4.0 (which is set inside the VC projects files).
http://msdn.microsoft.com/en-us/library/bb383985.aspx
Change-Id: I144ba1ef95372226ebadb082e3a78155cca316fd
instdir/LibreOfficeDev.app/Contents/MacOS/libCbc.3.dylib -> libCbc.3.8.8.dylib
(which does not exist)
See also: 9f339a89453808b917177a3ee675a76385758902
Change-Id: I398d649c2e918b496c9b92364189da4796682653
Reviewed-on: https://gerrit.libreoffice.org/10614
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>
For whatever reason the tinderboxes still try to regenerate the
autotools based files, even after applying the generated file
change after the template changes.
These patches aren't needed, as the original problem is the CPPFLAGS
environment visibility, so we drop them.
Change-Id: Idb5caf662c997221337416686313101ad2193e40
The libgltf configure.ac script changes the autotools user variables
CFLAGS and CXXFLAGS, which is not allowed and can overwrite user
settings (which it does for the -D_GLIBCXX_DEBUG flag).
So this moves the special compile settings to seperate variables and
passes them to AM_CXXFLAGS and AM_CPPFLAGS, so the library actually
gets compiled with libstdc++ debug objects.
Change-Id: I00989f5fb629a6aac43ee5a2eb287b0491a3b86d
