On Tue, May 18, 2010 at 1:01 PM, Anthony Molinaro <
antho...@alumni.caltech.edu> wrote:

>
> No, only maintainers need automake and autoconf, all you need to compile
> from a source distribution is sh, gcc and make.
>
>

> > Cmake generates the makefile so once it is generated no need of it
> anymore.
> > So when delivering the tarball you only have to deliver an already
> generated
> > makefile.
>
> I'm not exactly certain how a pre-generated makefile would work.  Does the
> makefile conform to the bsd or gnu make conventions, how do I know it will
> work on an extremely old SunOS box, or on a windows 7 box.  The only way
> I can see this working is separate tarballs for each platform which would
> make creating new distributions even more slow than it is now.
>
> would be the same as it is , it is a comform makefile. The thing is if you
want to compile with say MSVC you can generate another makefile.

> > Another good feature of cmake is the generation of out of source build.
> We
> > can easily generate the binaries in the directory we want  doing thing
> like
> > :
> >
> > mkdir thrift-build
> > cd thrift-build
> >
> > cmake ../thrift-source
> > make
>
> I'm not sure why you would want this, but you can do this sort of thing
> with
> autotools if you want.  Its more common to want to control where something
> is installed, what features are included in the build, or even to cross
> compile
> for a different architecture.  All things that configure supports.  Also,
> the autotools support DESTDIR which makes packaging as rpms and debs
> extremely easy.
>
> I'll look at the opportunities. This is only for me to get to know thrift
 source code.

> > I will try things out with cmake and thrift. I will try to convert it and
> > see all options available to us.
>
> I still am wondering the same thing David is, seems like users would still
> require that cmake is installed, in other words if they start with a
> tarball
> distribution how do they build install with cmake?
>
> Here's how it works with configure
> % wget 'http:/.../thrift.tar.gz'
> % tar xvfz thrift.tar.gz
> % cd thrift
> % ./configure              # pure sh
> % make                     # should work with any make on system
> % sudo make install        # install location can be altered with --prefix
>                           # added to configure, also can be installed
>                           # under an alternate / with DESTDIR
>
> What does this look like using cmake?
>
> It would look the same (i think). let me test it and I will return to you
with that.

> -Anthony
>
>
> --
Pierre-Alexandre St-Jean

Reply via email to