| Age | Commit message (Collapse) | Author |
|---|
|
... so that hopefully it won't be "cleaned up" and needlessly diverge
from any hypothetical future upstream.
Change-Id: I10503072f618ac6b74bc52d4d59c0d8951bd8d0d
Reviewed-on: https://gerrit.libreoffice.org/23075
Reviewed-by: David Ostrovsky <david@ostrovsky.org>
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I4bdcc848ffcd4084d0f8ed6bf3de59c5feab6dd8
|
|
|
|
"VC_EXTRALEAN can only be used in MFC projects."
(<https://support.microsoft.com/en-us/kb/166474> "How to use VC_EXTRALEAN and
WIN32_LEAN_AND_MEAN to enhance the build process in Visual C++")
So presumably indeed not needed here (as reported by clang-cl).
Change-Id: Id98c6e9e862e716cf5e238623c6ac4ca0603fd63
|
|
There is no obvious authoritative upstream for clew anyway, so it causes
philosophical problems for distros. For a while, we used to use a zip archive
from the "clcc" project on SourceForge that included clew.c and
clew.h. (Before that we also just had clew.c and clew.h in our source repo.)
So, drop the external/clcc module and have clew.c and clew.h in the source
repo again. But this time clew is in a module of its own, not in sc.
This re-introduces "No need to have OpenCL optional at configure-time"
This reverts commit 764836cb00e8e6dfd2ab48e080a166ec90359e01.
Change-Id: I413142f4f9f8399489f9c3e5327132822f07a454
Reviewed-on: https://gerrit.libreoffice.org/13368
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>
|
