From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Patrick Williams <patrick@stwcx.xyz>, Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
OpenBMC Patches <openbmc-patches@stwcx.xyz>
Subject: Re: [PATCH ipmi-fru-parser] RFC: use cmake.
Date: Fri, 11 Mar 2016 14:55:32 +1100 [thread overview]
Message-ID: <87y49p7jnv.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y49tb8u9.fsf@linux.vnet.ibm.com>
Stewart Smith <stewart@linux.vnet.ibm.com> writes:
> Patrick Williams <patrick@stwcx.xyz> writes:
>> On Mon, Mar 07, 2016 at 02:30:51PM +1030, Joel Stanley wrote:
>>> On Fri, Mar 4, 2016 at 9:00 AM, OpenBMC Patches
>>> <openbmc-patches@stwcx.xyz> wrote:
>>> > From: Patrick Williams <patrick@stwcx.xyz>
>>> >
>>> > There was a previous proposal to consider autotools (see
>>> > openbmc/ipmi-fru-parser#7). This is an alternative implementation
>>> > using cmake.
>>>
>>> I'm not a fan of autotools; I have not chosen to use it on small
>>> projects in the past.
>>>
>>> That said, I have stopped working on projects due to cmake's
>>> downsides. It's overly complex, and no clear way to implement rules,
>>> making it hard for newbies and experienced developers alike.
>>
>> Can you elaborate on this? I honestly don't have much experience with
>> CMake but from the little I have played with it it seems 5x easier than
>> makefiles (which autotools still use via Makefile.am).
>
> Some getting started bits are easier in CMake, that's true. But CMake
> misses a few important things:
Tridge on CMake:
https://lists.samba.org/archive/samba-technical/2010-February/069670.html
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2016-03-11 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:30 [PATCH ipmi-fru-parser] RFC: use cmake. (DO NOT MERGE) OpenBMC Patches
2016-03-03 22:30 ` [PATCH ipmi-fru-parser] RFC: use cmake OpenBMC Patches
2016-03-07 4:00 ` Joel Stanley
2016-03-08 2:53 ` Patrick Williams
2016-03-08 9:46 ` Stewart Smith
2016-03-11 3:55 ` Stewart Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y49p7jnv.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc-patches@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.