Displaying 3 results from an estimated 3 matches for "findzlib".
Did you mean:
findlib
2014 Sep 17
2
[LLVMdev] proposal to avoid zlib dependency.
On 17 September 2014 16:34, Mueller-Roemer, Johannes Sebastian
<Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote:
> I'll have another look tomorrow.
Thanks.
> IMO, it is unnecessary clutter. It will fail if ${ZLIB_LIBRARIES} or ${ZLIB_INCLUDE_DIRS} are used anyways as they will be set to NOTFOUND. Or we go back to a silent-fail solution:
Fair enough. I've never
2016 Sep 01
2
change in CMake variable names breaks existing uses and does not conform to CMake conventions
...would like to discuss if this rename is desirable at all. Sure, in-tree LLVM_INCLUDE_DIR is used everywhere, however not providing an ${NAME}_INCLUDE_DIRS variable goes against CMake conventions. See for example the find scripts included with CMake itself:
https://cmake.org/cmake/help/v3.6/module/FindZLIB.html -> provides ZLIB_INCLUDE_DIRS (and not ZLIB_INCLUDE_DIR) even though it is typically only one directory
And the same holds true for most other Find${NAME}.cmake scripts I had a look at (Boost, Bullet, CUDA, Freetype, XMLRPC, Zlib). I'll admit there are 1 or 2 exceptions (such as OpenG...
2014 Sep 17
6
[LLVMdev] proposal to avoid zlib dependency.
On Tue, Sep 16, 2014 at 7:47 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> IIUC zlib availability is tested and the library used if present. Do you
> mean that LLVM does not use zlib on Windows when the library is present?
Sure, but if there aren't instructions for how to do it easily, then it's
effectively unsupported. There isn't really a canonical way to