Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
From: Jeff Coffler <Jeff.Coffler@microsoft.com.INVALID>
To: "dev@mesos.apache.org" <dev@mesos.apache.org>
Subject: RE: [E] Re: The state of cmake
Thread-Topic: [E] Re: The state of cmake
Thread-Index: AQHS6uIDyWixneddUkiO56nFeo2LHaIv75xRgAAHQrCAAAcEAIABBLwAgAAHkpA=
Date: Thu, 22 Jun 2017 15:56:51 +0000
Message-ID: <MWHPR21MB0159C77C2482760795DC58EF97DB0@MWHPR21MB0159.namprd21.prod.outlook.com>
References: <D5707297.1B59B%aaron.wood@one.verizon.com>
 <MWHPR21MB01736EB9A2DE52BD78CA2EE8C4DA0@MWHPR21MB0173.namprd21.prod.outlook.com>
 <MWHPR21MB01593D3F6C0F658C87F19AF097DA0@MWHPR21MB0159.namprd21.prod.outlook.com>
 <CAGxaGb1jc1aS2qFXYhqx=uiHXgjFW26uHah=8Th8NSfNmLM-cw@mail.gmail.com>
 <D571559E.1B5A8%aaron.wood@one.verizon.com>
In-Reply-To: <D571559E.1B5A8%aaron.wood@one.verizon.com>
Accept-Language: en-US
Content-Language: en-US
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Ref=https://api.informationprotection.azure.com/api/72f988bf-86f1-41af-91ab-2d7cd011db47;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetBy=jeffcof@microsoft.com;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2017-06-22T08:56:50.3779712-07:00;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure
 Information Protection;
 MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic;
 Sensitivity=General
authentication-results: mesos.apache.org; dkim=none (message not signed)
 header.d=none;mesos.apache.org; dmarc=none action=none
 header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:1::64a]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;MWHPR21MB0509;7:0poIGQUmFCgVeM4qbHnHn0P8jW1c7YreJYLJGWpf3cESr0ezTmDs1de1gOmVyQPYoKXSIpfgck/i0hGq3IoXnfmCPyxk+BDvtCOGzIQaKQg3wGTxLUR8zm3KEkiO/8TsvnhmA7Q3tZ8JS92+bTUxSj8eYiTlEgYTOmnNdyAS7Qgnzt2bXtk6I7/ONxOiYH9l6orzaj56LRd4U2FvorJ2AHFOLHyUU0NR3RvgZXrwt2Cm/NC89DMqRDNT1zGxSRqUSLnrk7Hys96WgFTVbVRTIy+ZXlr40JFajEJw9sgf6aBUU00LA1dJZlDzqxg9aRFBbFDy00o3t+Ezli2bo8cQ2THq/I8OaWD1RwIIb8s8gZt0RueAImAShD7pr2cm5OoEH4VaTA5oOeQxPvYzGjCYpNnoY57Pg42FFLjEq5WvsurZ2TKNSHDzOOToZKRw5fvr0axXo+aSpO3i1iNgnVxFz1XWvZa8Y7ykZIVZphm/W44vyRXjHHIXwb93+JNMZhMUYMlqvUcvoV/hKRwYr40EixurfhoxjXLttSXB79qpP65mjVY+gehdsEQnX43H1vgTVZCCsm4J/S1prnX1Mq3Yln63fgxpze5NgjqoXcQiPh5a4rL7on6p18/F8E4rnXiPdSRfV4Va61Mp+9b2Mc/tgN94GYBk3NMBhzF3meDzMjSpsfoc5Yn2SNZHPUI/PeqN9PQiXKCuT4AFOhsc5su1nk37S6XqSUsEQxzq83Vwd7p4xjKCg20XCQpTSlxF/Z81rrpk/Qv0ZIRuDhIfBCIIy2AuUKdnPjTLWrKuhYZ9B/P5R2P20UTOnAcff2RJ0VWg
x-ms-office365-filtering-correlation-id: 4e1cb491-f7ba-43e5-eeba-08d4b9874c85
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(300000500055)(300135000095)(300000501055)(300135300095)(22001)(300000502055)(300135100095)(2017030254075)(300000503055)(300135400095)(48565401081)(201703131423075)(201703031133081)(300000504055)(300135200095)(300000505055)(300135600095)(300000506048)(300135500095);SRVR:MWHPR21MB0509;
x-ms-traffictypediagnostic: MWHPR21MB0509:
x-microsoft-antispam-prvs: <MWHPR21MB0509284483F19429823F765697DB0@MWHPR21MB0509.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(189930954265078)(788757137089)(219752817060721)(154440410675630);
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123560025)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095);SRVR:MWHPR21MB0509;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:MWHPR21MB0509;
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(39850400002)(39450400003)(39860400002)(39410400002)(39400400002)(377454003)(24454002)(13464003)(53754006)(478600001)(77096006)(189998001)(72206003)(99286003)(25786009)(74316002)(33656002)(53936002)(229853002)(55016002)(2351001)(305945005)(5005710100001)(6246003)(5660300001)(10090500001)(9686003)(86362001)(575784001)(7736002)(54356999)(8676002)(76176999)(6306002)(3280700002)(10290500003)(122556002)(81166006)(2501003)(7696004)(53546010)(8936002)(6116002)(6916009)(2950100002)(50986999)(3660700001)(1730700003)(5640700003)(110136004)(93886004)(38730400002)(14454004)(2900100001)(2906002)(6506006)(102836003)(6436002);DIR:OUT;SFP:1102;SCL:1;SRVR:MWHPR21MB0509;H:MWHPR21MB0159.namprd21.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2017 15:56:52.0220
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0509
archived-at: Thu, 22 Jun 2017 15:57:06 -0000

Thanks Aaron. Do keep in touch if you have any issues or find any problems.

I use the cmake system routinely (daily) to build both Linux and Windows, a=
nd it works for us. I know others are using cmake too, but that said, it is=
 very new. If you have any problems or issues, we'd love to hear about it!

/Jeff

-----Original Message-----
From: Wood, Aaron [mailto:aaron.wood@verizon.com]=20
Sent: Thursday, June 22, 2017 8:28 AM
To: dev@mesos.apache.org
Subject: Re: [E] Re: The state of cmake

Thanks for the info everyone. I think this might be good enough for us to m=
ove forward with since we don=B9t need python/java bindings and we're doing=
 our own packaging/release anyway.
It might be nice to compile an exhaustive list of the differences between t=
he two since there might be small differences that most people might not be=
 aware of. For example, we=B9d like to apply some hardening that=B9s alread=
y built into the auto tools side. We can apply it manually via cmake flags =
for now so it=B9s not a huge deal that it=B9s not yet built into the cmake =
system.

Also, I=B9ll help improve upon the cmake system as much as I can going forw=
ard. We=B9ll switch over to it sometime this month and contribute patches i=
f anything comes up :)

Thanks,
Aaron

On 6/21/17, 7:55 PM, "Joseph Wu" <joseph@mesosphere.io> wrote:

>Here's the earlier email which has the feature comparison:
>
>https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Furldef
>ense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__lists.apache.org_thre&da
>ta=3D02%7C01%7CJeff.Coffler%40microsoft.com%7C0866d0b62c4c41ee661808d4b98
>46cd8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636337425797116263&s
>data=3DW9EK1VdNuHjc28EpiD%2F9pDMMudA4DhGEgYFVzq%2B5NKk%3D&reserved=3D0
>ad.html_527a29b45c52a042c122c96754804983b1447b7409ffec3d635b7143-40-253
>Cde=20
>v.mesos.apache.org-253E&d=3DDwIBaQ&c=3DudBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6_=
_
>0Po=20
>mBTQ&r=3DOf4_2lOwuO41tqndIfzTuDYukljy48QGHOjPpLG5Ikg&m=3DtIOFEs3nvAbyrLpDd=
Q
>9tT=20
>Kuxp5VhX6z8CQCst_-pDLE&s=3D0H1X-xMm47jKQK8V25a60ZtbR3vHm83i7BK3sqnij2c&e=
=3D
>
>The list is still accurate, except that precompiled headers are no=20
>longer "upcoming".
>
>On Wed, Jun 21, 2017 at 4:42 PM, Jeff Coffler <=20
>Jeff.Coffler@microsoft.com.invalid> wrote:
>
>> Hi Aaron,
>>
>> I'd like to expand on what Andy said:
>>
>> If you want cross-platform development, then cmake is the only way to=20
>>go.
>> For example, if you want to build on Windows, you MUST use cmake. We =20
>>anticipate, over time, that cmake will replace the autotools build (we=20
>>do  not want to maintain two build systems). The cmake system is also=20
>>much more  expandable (for example, while this hasn't been done on=20
>>Linux, Windows had  dramatic speed improvements through the use of=20
>>precompiled headers - if  someone was inclined to spend the time on=20
>>Linux, I imagine similar speed  improvements are possible). Note, by=20
>>the way, that ReviewBot runs on  Windows; if you break the Windows=20
>>build, you need to fix it prior to  committing changes.
>>
>> I would say: If you don't care about Java or Python bindings, and=20
>>you're  doing development (i.e. you don't need an installable=20
>>package), then cmake  is a fine way to go. But if you need something=20
>>that only autotools does  today, then you don't really have a choice.=20
>>Regardless, when you commit a  change, you need to be sure that both=20
>>build systems work properly.
>>
>> Note that cmake is compatible with ccache. Also, FWIW, cmake also=20
>>gives  you very nice "percentage done" notifications on Linux (i.e.=20
>>85% done, or  whatever), which is super nice to know how far along you=20
>>are. That's a very  cool feature that I just love.
>>
>> I agree that we sorely need a concise list of features that are missing.
>> We need to understand what's missing, and judge how often missing=20
>>features  are used, in order to "fully bake" the cmake build system in=20
>>Mesos.
>>
>> /Jeff
>>
>> -----Original Message-----
>> From: Andy Schwartzmeyer [mailto:andschwa@microsoft.com.INVALID]
>> Sent: Wednesday, June 21, 2017 4:12 PM
>> To: dev@mesos.apache.org
>> Subject: RE: The state of cmake
>>
>> Hi Aaron,
>>
>> The biggest difference right now is that the Java and Python bindings=20
>>are  not built whatsoever with the CMake build system. We also do not=20
>>have an  install target, so the CMake output is kind of stuck in=20
>>"developer mode"
>> and it won't generate an installable package.
>>
>> I probably would not yet recommend the CMake build system for=20
>> production use.
>>
>> As far as what features are missing, I'm not aware of a concise list,=20
>>but  agree this is needed. Perhaps Joseph knows of one. If one does=20
>>not exist at  all, perhaps it's time we audit the issues and do a=20
>>comparison of the two  build systems as they stand now to generate=20
>>this list.
>>
>> Cheers,
>>
>> Andy
>>
>> From: Wood, Aaron<mailto:aaron.wood@verizon.com>
>> Sent: Wednesday, June 21, 2017 4:00 PM
>> To: dev<mailto:dev@mesos.apache.org>
>> Subject: The state of cmake
>>
>> Hi all,
>>
>> I'm curious as to what the current state of came is on Linux. I=20
>>noticed  that some features that are present in the autotools build=20
>>are not yet in  cmake. Also, the output from a successful cmake build=20
>>looks a bit different  as far as the number of libraries that are=20
>>produced and the number of  symlinks created.
>>
>> While the output of a cmake build does seem to work fine on Linux, is =20
>>there anything to be aware of that would cause issues for a production =20
>>release? Is there a list of features somewhere that are in autotools=20
>>but  not yet in cmake? Does anyone think it is an exceptionally bad=20
>>idea to use  the current cmake system to produce binaries for=20
>>production use?
>>
>> Thanks!
>> -Aaron
>>
>>