Eli Friedman
2009-Aug-09 21:36 UTC
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
On Sun, Aug 9, 2009 at 1:04 PM, Óscar Fuentes<ofv at wanadoo.es> wrote:> Eli Friedman <eli.friedman at gmail.com> writes: > >> On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >>> I think most LLVM users on Windows are interested on X86 only. This >>> saves a lot of time on the build process and creates smaller >>> executables. Anyways, it they want all targets, it is simply a matter of >>> passing -DLLVM_TARGETS_TO_BUILD=all on the cmake command line. >> >> I don't see any reason why that argument applies to people building >> with MSVC, but not people on other platforms. > > Another reason is that by limiting the build to X86, there is a > smaller probability of a build failure with a toolset which is not > checked on a day-by-day basis, as msvc is.MSVC *is* continuously checked; see http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone who breaks the MSVC build will get a nastygram from buildbot. -Eli
Benjamin Kramer
2009-Aug-09 22:29 UTC
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
Am 09.08.09 23:36, schrieb Eli Friedman:> > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. >Please note that the MSVC buildbot only builds the X86 target at the moment. I don't know why though.
Óscar Fuentes
2009-Aug-09 22:35 UTC
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
Eli Friedman <eli.friedman at gmail.com> writes:> MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot.This is new news for me. If the developer who broke the msvc build receives a nastygram, would he urged to fix it when he has no msvc compiler and probably no Windows machine either? The "don't break the build" mantra applies to *nix only. No LLVM developer will be bashed for breaking the msvc build. Which is understandable: the pain of multiple compiler C++ support is too much for mere mortals. Anyways, that buildbot only checks one msvc compiler (right?). It is not infrequent a broken build on some compiler version for a long time. -- Óscar
Daniel Dunbar
2009-Aug-09 22:42 UTC
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
On Sun, Aug 9, 2009 at 3:29 PM, Benjamin Kramer<benny.kra at googlemail.com> wrote:> Am 09.08.09 23:36, schrieb Eli Friedman: >> >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone >> who breaks the MSVC build will get a nastygram from buildbot.Technically it doesn't send nastygrams either, all though so far we've done a good job of noticing when it breaks.> > Please note that the MSVC buildbot only builds the X86 target at the moment. > I don't know why though.Because my Win32 box is super slow. :) It made more sense when I was ironing out kinks, now that it works its probably worth switching it back. The big problem with the windows builder is that it doesn't run any tests, so while it makes sure things build, it doesn't make sure they work (as well as they do). - Daniel> _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Daniel Dunbar
2009-Aug-09 22:48 UTC
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
On Sun, Aug 9, 2009 at 3:35 PM, Óscar Fuentes<ofv at wanadoo.es> wrote:> Eli Friedman <eli.friedman at gmail.com> writes: > >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone >> who breaks the MSVC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer who broke the msvc build receives a nastygram, would he > urged to fix it when he has no msvc compiler and probably no Windows > machine either? The "don't break the build" mantra applies to *nix > only. No LLVM developer will be bashed for breaking the msvc build. > Which is understandable: the pain of multiple compiler C++ support is > too much for mere mortals.It is frequently possible to unbreak the build just from reading the log. In practice this isn't that different from Darwin vs Linux, except that MSVC likes to break more often. :)> Anyways, that buildbot only checks one msvc compiler (right?). It is not > infrequent a broken build on some compiler version for a long time.Right. If we get developers who care about MSVC (and want to do something about it) they are welcome to fix this. - Daniel> -- > Óscar > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Possibly Parallel Threads
- [LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
- [LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
- [LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
- [LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
- [LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw