search for: buildtyp

...0.55.1 >> > > >> > > Overall, it looks good, so well done! >> > > >> > > Just a couple of minor things I noted: >> > > >> > > 1. Arch uses a meson wrapper script (arch-meson) that sets: >> > > >> > >   --buildtype plain >> > > >> > > This seems to trigger a bug in meson that results in copious bogus compiler warnings: >> > > >> > > cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] >> > > cc1: warning: ‘-Wformat-extra-args’ igno...

...t; > > > > > > > > > > Just a couple of minor things I noted: > > > > > > > > > > > > > > 1. Arch uses a meson wrapper script (arch-meson) that sets: > > > > > > > > > > > > > >   --buildtype plain > > > > > > > > > > > > > > This seems to trigger a bug in meson that results in copious bogus compiler warnings: > > > > > > > > > > > > > > cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wforma...

...in hacking on it myself, then a release build makes sense. However, I think this is a violation of expectations in that this is overriding a *cmake* variable. It takes control away from the user. cmake probably has something to answer for here, because there's not an explicit "empty" buildtype like e.g. meson's `--buildtype plain`, but only the absense of a value. Perhaps we could find a middle ground. e.g. LLVM_DONT_TWEAK_CMAKES_BUILD_TYPE=ON which would allow fast builds, but also enable us to mess with the cmake default to please new users? > > You mention CI systems, but...

Hi, Just a heads up on my experiences with the new build system. Arch Linux meson-0.55.1 Overall, it looks good, so well done! Just a couple of minor things I noted: 1. Arch uses a meson wrapper script (arch-meson) that sets:   --buildtype plain This seems to trigger a bug in meson that results in copious bogus compiler warnings: cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] cc1: warning: ‘-Wformat-zero-length’ ignored wit...

...eriences with the new build system. >> >> Arch Linux >> meson-0.55.1 >> >> Overall, it looks good, so well done! >> >> Just a couple of minor things I noted: >> >> 1. Arch uses a meson wrapper script (arch-meson) that sets: >> >>   --buildtype plain >> >> This seems to trigger a bug in meson that results in copious bogus compiler warnings: >> >> cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] >> cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] >&...

...wrote: >Hi, > >Just a heads up on my experiences with the new build system. > >Arch Linux >meson-0.55.1 > >Overall, it looks good, so well done! > >Just a couple of minor things I noted: > >1. Arch uses a meson wrapper script (arch-meson) that sets: > >? --buildtype plain > Does this affect the 'meson' available for end users? Or this is just for the packaging system? (I'm not familiar with Arch) If it affects end users, I'd say it's a bug in Arch. >This seems to trigger a bug in meson that results in copious bogus compiler warnin...

...Linux > > > meson-0.55.1 > > > > > > Overall, it looks good, so well done! > > > > > > Just a couple of minor things I noted: > > > > > > 1. Arch uses a meson wrapper script (arch-meson) that sets: > > > > > >   --buildtype plain > > > > > > This seems to trigger a bug in meson that results in copious bogus compiler warnings: > > > > > > cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] > > > cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wfor...

On Tue Nov 17, 2020 at 6:37 PM GMT, Min-Yih Hsu wrote: > Just trying to understand: Are you suggesting a way to have a “-O0” > build without all the debug information? > Exactly.

...und is to simply unset these environment variables before running the native configure step: --- a/cmake/modules/CrossCompile.cmake +++ b/cmake/modules/CrossCompile.cmake @@ -45,6 +45,9 @@ function(llvm_create_cross_target_internal target_name toolchain buildtype) # Propagate LLVM_EXTERNAL_CLANG_SOURCE_DIR so that clang-tblgen can be built set(external_clang_dir "-DLLVM_EXTERNAL_CLANG_SOURCE_DIR=${LLVM_EXTERNAL_CLANG_SOURCE_DIR}") endif() + unset(ENV{ASM}) + unset(ENV{...

.../build/llvm/obj/test/QMTest qmtest -D /home/wanderer/pkg/build/llvm/src/llvm/test run -O /home/wanderer/pkg/build/llvm/src/llvm/test/QMTest/expectations.unknown.qmr -c "srcroot=/home/wanderer/pkg/build/llvm/src/llvm" -c "buildroot=/usr/home/wanderer/pkg/build/llvm/obj" -c "buildtype=Debug" -c "tmpdir=/usr/home/wanderer/pkg/build/llvm/obj/test/tmp" -c "coresize=0" -c "cc=gcc" -c "cxx=g++" -c "llvmgcc=PATH=/usr/home/wanderer/pkg/build/llvm/obj/tools/Debug:/sbin:/bin:/ usr/sbin:/home/wanderer/bin:/home/wanderer/pkg/gcc/bin:/home/...

...i, > > Just a heads up on my experiences with the new build system. > > Arch Linux > meson-0.55.1 > > Overall, it looks good, so well done! > > Just a couple of minor things I noted: > > 1. Arch uses a meson wrapper script (arch-meson) that sets: > > ? --buildtype plain > > This seems to trigger a bug in meson that results in copious bogus compiler warnings: > > cc1: warning: ?-Wformat-y2k? ignored without ?-Wformat? [-Wformat-y2k] > cc1: warning: ?-Wformat-extra-args? ignored without ?-Wformat? [-Wformat-extra-args] > cc1: warning: ?-Wf...

Greetings all, In looking at the API for ActiveRecord::Associations::ClassMethods there doesn''t appear to be a way to rename an association. In doing some refactoring I am replacing one table with two but want to preserve the old associations names, e.g. I want to be able to still say build_type.artifacts instead of having to use the new table name: build_type.build_type_artifacts.

...displays: > ----------------------------------------------- > QMTEST_CLASS_PATH=/home/yue/llvm/test/QMTest qmtest -D > /home/yue/llvm/test run -O /home/yue/llvm/test/QMTest/expectations.qmr > -c "srcroot=/home/yue/llvm" -c "buildroot=/home/yue/llvm" -c > "buildtype=Debug" -c "tmpdir=/home/yue/llvm/test/tmp" -c "coresize=0" -c > "cc=gcc" -c "cxx=g++" -c > "llvmgcc=PATH=/home/yue/llvm/tools/Debug:/home/yue/llvm/tools/Debug:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/yue/bin > /home/yue/cfronte...

.../QMTest > qmtest -D /home/wanderer/pkg/build/llvm/src/llvm/test run -O > /home/wanderer/pkg/build/llvm/src/llvm/test/QMTest/expectations.unknown.qmr > -c "srcroot=/home/wanderer/pkg/build/llvm/src/llvm" -c > "buildroot=/usr/home/wanderer/pkg/build/llvm/obj" -c "buildtype=Debug" -c > "tmpdir=/usr/home/wanderer/pkg/build/llvm/obj/test/tmp" -c "coresize=0" -c > "cc=gcc" -c "cxx=g++" -c > "llvmgcc=PATH=/usr/home/wanderer/pkg/build/llvm/obj/tools/Debug:/sbin:/bin:/ > usr/sbin:/home/wanderer/bin:/home/wandere...

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

Right that I had completely missed, I have added the files and verified that it builds with CMake from the tar on Linux (out of the git repo) I am parsing the package_version file from the tarball if it exists so it should maintain the version info. //Marcus ________________________________ From: Jean-Marc Valin <jmvalin at jmvalin.ca> Sent: Tuesday, April 2, 2019 11:38 To: Marcus