On 6/21/2012 1:21 PM, Douglas Gregor wrote:> > On Jun 20, 2012, at 5:13 PM, Nick Lewycky <nlewycky at google.com > <mailto:nlewycky at google.com>> wrote: > >> Is there anybody who is certain that our autoconf dependency needs to >> stay around? Are there developers stuck on systems that don't have a >> recent enough cmake in their most recent release, or maybe are using >> some features from configure+make that the cmake build system doesn't >> implement? >> >> If nobody pipes up, I might actually try actually removing it! > > I think this is premature, although I consider it a worthy goal. Right > now, the only motivation we have for removing "configure+make" is that > we don't like having two build systems, but that's not good enough. > > Some things that CMake needs to do well for it to become the only way > to build LLVM/Clang: > - Optionally build and install compiler-rt > - Optionally build and install libc++ > - Ease-to-use cross-compilation support > - Documentation to make it easy to understand how to do the above > - LLDB? > - LLVM testsuite support > > And some value-add that might make CMake motivating for others: > - Easy bootstrap > - Build packages/installersI decided to try recently to do one of my builds with cmake instead of configure. The problem I hit is before I even try compiling in the first place: cmake /src/llvm --help produces an extremely useless list of options, so it's impossible to figure out how to configure it with cmake without looking up online. Compare this to /src/llvm/configure --help, where I can see what the default build will look like and also how I can tweak it for what I want. Even the online documentation is kind of crappy in this regard: e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build in the first place. I'm sure most people who do a lot of cmake know these settings by the back of their hand, but if you're like me and totally clueless when it comes to cmake, it's downright confusing. -- Joshua Cranmer News submodule owner DXR coauthor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120622/2bd6cc05/attachment.html>
22.06.2012, 19:36, "Joshua Cranmer" <pidgeot18 at gmail.com>:> I decided to try recently to do one of my builds with cmake instead of configure. The problem I hit is before I even try compiling in the first place: cmake /src/llvm --help produces an extremely useless list of options, so it's impossible to figure out how to configure it with cmake without looking up online. Compare this to /src/llvm/configure --help, where I can see what the default build will look like and also how I can tweak it for what I want. Even the online documentation is kind of crappy in this regard: e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build in the first place. I'm sure most people who do a lot of cmake know these settings by the back of their hand, but if you're like me and totally clueless when it comes to cmake, it's downright confusing.Well, you can use ccmake to navigate back and forth through available options, their descriptions and values -- Regards, Konstantin
2012/6/23 Joshua Cranmer <pidgeot18 at gmail.com>:> I decided to try recently to do one of my builds with cmake instead of > configure. The problem I hit is before I even try compiling in the first > place: cmake /src/llvm --help produces an extremely useless list of options, > so it's impossible to figure out how to configure it with cmake without > looking up online. Compare this to /src/llvm/configure --help, where I can > see what the default build will look like and also how I can tweak it for > what I want. Even the online documentation is kind of crappy in this regard: > e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build > in the first place. I'm sure most people who do a lot of cmake know these > settings by the back of their hand, but if you're like me and totally > clueless when it comes to cmake, it's downright confusing.ccmake will help you. After generating makefiles, "make edit_cache" will show you options. ...Takumi
On Fri, Jun 22, 2012 at 10:51 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote:> 2012/6/23 Joshua Cranmer <pidgeot18 at gmail.com>: >> I decided to try recently to do one of my builds with cmake instead of >> configure. The problem I hit is before I even try compiling in the first >> place: cmake /src/llvm --help produces an extremely useless list of options, >> so it's impossible to figure out how to configure it with cmake without >> looking up online. Compare this to /src/llvm/configure --help, where I can >> see what the default build will look like and also how I can tweak it for >> what I want. Even the online documentation is kind of crappy in this regard: >> e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build >> in the first place. I'm sure most people who do a lot of cmake know these >> settings by the back of their hand, but if you're like me and totally >> clueless when it comes to cmake, it's downright confusing. > > ccmake will help you. > After generating makefiles, "make edit_cache" will show you options. > > ...Takumi > _______________________________________________ > cfe-dev mailing list > cfe-dev at cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-devFor those of you that are GUI inclined rather than stuck in a command prompt terminal all the time, cmake-gui is the prettier sister to ccmake. ;-) Using cmake-gui also shows all the options. Hovering over a variable name gives you a tooltip with the documentation string for the variable. HTH, David C.
On Jun 22, 2012 9:36 AM, "Konstantin Tokarev" <annulen at yandex.ru> wrote:> > > 22.06.2012, 19:36, "Joshua Cranmer" <pidgeot18 at gmail.com>: > > I decided to try recently to do one of my builds with cmake instead ofconfigure. The problem I hit is before I even try compiling in the first place: cmake /src/llvm --help produces an extremely useless list of options, so it's impossible to figure out how to configure it with cmake without looking up online. Compare this to /src/llvm/configure --help, where I can see what the default build will look like and also how I can tweak it for what I want. Even the online documentation is kind of crappy in this regard: e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build in the first place. I'm sure most people who do a lot of cmake know these settings by the back of their hand, but if you're like me and totally clueless when it comes to cmake, it's downright confusing.> > Well, you can use ccmake to navigate back and forth through availableoptions, their descriptions and values>The two guis really aren't a good substitute for a helpful command line interface. They miss newbies who expect --help to work on all programs. They help moderate-experience people who need to browse the options. They get in the way of experienced people who want to write scripts that select a set of options without blocking changes in other defaults. And the guis are irrelevant to experts. Jeffrey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120623/1f561a9d/attachment.html>