search for: kitwar

...ar. I encountered a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using TO_NATIVE_PATH, however CMake has a known bug ( http://public.kitware.com/Bug/print_bug_page.php?bug_id=5939 ) where TO_NATIVE_PATH does not replace slashes by backslashes when the MinGW Makefiles generator is used. The attached patch provides a workaround. Considering that the bug has been open since 2007 it is unlikely that kitware will fix this anytime soon. Reg...

I have this project that I can't see how to boil down into a cut down illustration of the problem as it requires a large 3rd party library (ITK www.itk.org), and the problem is actually triggered in that library. But here is the problem: If you compile ITK and the program, it will segfault in _Unwind_resume at the end of a class method. If you build with GCC (4.6.1 in this case) the program

It is with great sadness that I must tell everyone CMake’s Ninja generator is non-deterministic (https://public.kitware.com/Bug/view.php?id=15968 <https://public.kitware.com/Bug/view.php?id=15968>). I’m not sure if this impacts all versions of CMake, but it certainly impacts all the recent releases. You might ask why this matters? Sadly the non-determinism *does* impact determinism in the final builds. I hav...

...a bug in the CMake build while using MinGW (non-MSYS, > non-CYGWIN) where the LTO_export fails with a “The syntax of the > command is incorrect” error. This error was previously fixed for > Windows in general using TO_NATIVE_PATH, however CMake has a known bug > ( > http://public.kitware.com/Bug/print_bug_page.php?bug_id=5939 ) where > TO_NATIVE_PATH does not replace slashes by backslashes when the MinGW > Makefiles generator is used. The attached patch provides a workaround. > Considering that the bug has been open since 2007 it is unlikely that > kitware will fix...

...is targeted at Linux distributions which want to use the same compiler flags for multiple packages. If you want to change the default build type to something else when CMAKE_BUILD_TYPE is empty, make sure that you do that when $ENV{CFLAGS} and $ENV{CXXFLAGS} are not set. There is a blog entry at Kitware https://blog.kitware.com/cmake-and-the-default-build-type/ on this topic. Unfortunately it doesn't address the CFLAGS, CXXFLAGS issue. I guess one can combine the both and have an optimal solution. Cheers, Cristian. -------------- next part -------------- An HTML attachment was scrubbed... U...

...PILER_RT_INSTALL_PATH=lib${LLVM_LIBDIR_SUFFIX}/clang/${CLANG_VERSION} # -DCOMPILER_RT_INCLUDE_TESTS=ON INSTALL_COMMAND "" ) add_dependencies(compiler-rt clang clang++ llvm-config) 1) Looks like "DEPENDS" option is just broken - docs here ( http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html) state that you can pass CMake targets there, but if I uncomment that line, I get errors like: CMake Error at /usr/local/share/cmake-2.8/Modules/ExternalProject.cmake:720 (message): External project "clang" has no stamp_dir Call...

...is targeted at Linux distributions which want to use the same compiler flags for multiple packages. If you want to change the default build type to something else when CMAKE_BUILD_TYPE is empty, make sure that you do that when $ENV{CFLAGS} and $ENV{CXXFLAGS} are not set. There is a blog entry at Kitware https://blog.kitware.com/cmake-and-the-default-build-type/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.kitware.com%2Fcmake-and-the-default-build-type%2F&data=02%7C01%7C%7C0fdff823fe65421696db08d6be4f8a76%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636905646161553...

On 29 June 2015 at 07:16, Brad King <brad.king at kitware.com> wrote: > On 06/27/2015 04:17 AM, Dan Liew wrote: >> Second, the LLVM CMake files (LLVMConfig.cmake and LLVMExports.cmake) >> are not relocatable (they contain absolute paths which are based on >> the install prefix). So even if the first issue is fixed we still have &g...

The current behavior is to not specify any toolchain and invoke CMake without additional arguments for configuring the NATIVE portion of the build. However, CMake will actually set the CC, CXX, and FC environment variables to full paths of the compilers in the CMAKE_{C,CXX,Fortran}_COMPILER CMake variables inside the CMake process. This results in those variables being propagated to any

On Thu, Feb 6, 2014 at 7:57 PM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > > Le 6 févr. 2014 à 16:20, Brad King <brad.king at kitware.com> a écrit : > > > On 02/06/2014 08:12 AM, Alexey Samsonov wrote: > >> Please note that it makes a lot of sense to built compiler-rt (and > sanitizers) with just-built > >> Clang. In fact, even though we should support building it with another > compilers (gcc...

This is useful for developer who uses multicore builder. https://cmake.org/cmake/help/v3.9/release/3.9.html#other-changes - The Ninja <https://cmake.org/cmake/help/v3.9/generator/Ninja.html#generator:Ninja> generator has loosened the dependencies of object compilation. Object compilation now depends only on custom targets and custom commands associated with libraries on

> > Replicating ExternalProject would be a lot of work... > One approach commonly used with CMake modules that change frequently upstream is for the project to keep a local copy and have a check in place to use CMake's version if new enough. For instance, in llvm's source tree: cmake/modules/ExternalProject.cmake: if(CMAKE_VERSION VERSION_LESS "3.5.1")

..., we bump the CMake version to whatever version of CMake is 12 months old. > > > > This is simple, straightforward, and it gives a full year of old CMakes being supported. If we did this right now, this would take us to CMake 3.14.0, released around March 14th, 2019 (https://github.com/Kitware/CMake/releases/tag/v3.14.0 <https://github.com/Kitware/CMake/releases/tag/v3.14.0>). I believe the expectation should be that recent CMakes are upgraded using some package manager or download from the site -- we can't really expect the CMake version to be the one provided by the system,...

...or files named " -m64 ... ") but checking the relevant build command in build.ninja at least shows me that the relevant path is indeed getting added via set_target_compile_flags: the path is now part of one of these quoted strings. On Feb 12, 2014, at 11:01 AM, Brad King <brad.king at kitware.com> wrote: > On 02/12/2014 02:04 AM, Seth Cantrell wrote: >>> set(DARWIN_iossim_CFLAGS >>> -mios-simulator-version-min=7.0 -isysroot ${IOSSIM_SDK_DIR}) >> >> where IOSSIM_SDK_DIR is the path including spaces and parens. > > It looks like the _CFLAG...

...ions in distro LTS releases. We have > been *way* too conservative already, waiting this long. > > Downloading and building a local copy of cmake is trivial. You don't even > need to install it. Anyone who is developing and building LLVM can > definitely manage it. Not only that, kitware even has an official apt > repository -- you can install a deb if installing that seems easier for you > (https://apt.kitware.com/). > > > On Thu, Jul 16, 2020 at 8:05 PM Jessica Clarke via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On 30 Jun 2020, at 16:...

On Mon, Feb 24, 2014 at 6:05 PM, Brad King <brad.king at kitware.com> wrote: > On 02/24/2014 08:53 AM, Alexey Samsonov wrote: > > On Fri, Feb 21, 2014 at 9:03 PM, Brad King wrote: > > Just "build" should be sufficient because the generated build system > > in compiler-rt knows how to re-run CMake if any of the inputs h...

On 20 July 2015 at 09:00, Brad King <brad.king at kitware.com> wrote: > On 07/17/2015 02:44 PM, Rafael Espíndola wrote: >> Setting CMAKE_CXX_CREATE_STATIC_LIBRARY works on OS X and linux, but >> on windows I still see a call to "lld-link2 /lib..." when >> CMAKE_CXX_CREATE_STATIC_LIBRARY is set to use llvm-lib. > >...

> On Feb 25, 2016, at 7:49 AM, Brad King <brad.king at kitware.com> wrote: > > On 02/19/2016 10:35 AM, Ben Langmuir wrote: >>> On Feb 19, 2016, at 7:16 AM, Brad King wrote: >>> [snip] >>>> __NSConstantString and __NSConstantString_tag are now exposed. >>> To clarify, this is not so much about the appearance of...

Hello List, I'm not enterelly sure that I'm on the rist place to ask this question, sorry if not. The question is simple, *how to test simply a ssh tunnel ?* I just want to make sure the the tunnel i'm opening is letting information goes through it without problem, and I want to avoid any other point of failure when testing. for example let's say I run ssh -L

On Mon, Feb 24, 2014 at 6:57 PM, Brad King <brad.king at kitware.com> wrote: > On 02/24/2014 09:44 AM, Alexey Samsonov wrote: > > ExternalProject_Add_Step(compiler-rt force-rebuild > > DEPENDERS build > [snip] > > doesn't work for Ninja. > > What version of CMake did you use for this test? Also 2.8.10? > Yes, 2.8...