Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT Monthly Call
  • From: William Riley <william.riley@xxxxxxxxxxx>
  • Date: Tue, 17 Oct 2023 22:19:18 +0000
  • Accept-language: en-US, en-GB
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=RBU3dY8XwrsXAmaHI3rMMS569AKrGaBuXCE/NDnN/38=; b=PcDaodltH1dJYWhSIW6xxo96OgrQwrE0WzPm77zaQRvvTDROMJfJn3XeMiYYmL2FtEIyICZYI1cj/TtFzVglwvFiScRUjXhsPW1KbsZh9SY58jkN7KMOP6Aaf8/U4a2fIH9Vi7LuMZqnBj1ybKk5eqNvtHT9vmCaYieKJ34c0Lt+KIwU3KHGjizSyWJBV/UWjt0NSHofWn9SuXXhOr86siZbrjKkKyUqkmqkGBIdkvul6y0gq3cUR7gcDaISJVYmUgQNMypjekJXciwg5YkmTtRLD+uMAWYSK+WxUW7piF9+rtgpg6W0F328If5B/h/WC/3HKyXuMDFoycdDjthoJw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=j6qd0cZskYVIX5llQDLm9dMh1dxA8QSQAlQahEjLpObqtIvhzuu8DIb0lhS8dF98fm7JMeeyCNI0qSg3DIVJMuxwuyQ8XDKxufTpT5mGaDaONnsvJfiEBuP3AhprlU0DU+4+CczhEnXifHfN0C3WEbIOi2cp8sAeyT54J0LMBEvyRsK4Y2G0cnfKSrl6hDRne/t8PieAhX+itTiG+Fcm6jnHbIzv0SjEFqNhoR87beYLZ1UKo+Jsm/bXn79VJYb81ShQ7lVN3VF0ivxbqCJLV12BB9O5+hh7ZI+AzbHnQ2UOLwwsNosCqbtGNJaoXNSf7N4Rhh/IdMcs6nVnLNEQQQ==
  • Delivered-to: cdt-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHZ+9l0Ch7v/UFrLE+wM836MVWNN7BE2oKAgAf7UQCAAcC2ZQ==
  • Thread-topic: [cdt-dev] CDT Monthly Call

Hi Martin

What we (Renesas) are looking at is generating compile-commands.json based on the managed build data for a project.

We are not planning to implement a cmake generator for managed build. Just the json file for existing MBS make & internal builder projects.


From: cdt-dev <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Martin Weber via cdt-dev <cdt-dev@xxxxxxxxxxx>
Sent: Monday, October 16, 2023 9:27 pm
To: cdt-dev@xxxxxxxxxxx <cdt-dev@xxxxxxxxxxx>
Cc: Martin Weber <fifteenknots505@xxxxxxxxx>
Subject: Re: [cdt-dev] CDT Monthly Call
Am Mittwoch, 11. Oktober 2023, 19:33:53 CEST schrieb Jonah Graham via cdt-dev:
> Hello folks,
> Thanks for coming to the call today. I enjoyed the call and getting to talk

OK, I admit I should not have missed that call.

> to you all! Here are the minutes of the meeting:
>       - Renesas is looking to restart the work of compile_commands.json for
>       Managed Build project in the coming weeks

Huh, MBS is not dead? OTOH, CDT core build seem to be not really alive:-)

Parsing the compile_commands.json file for better support of the indexer is
already part of CDT in class

If Renesas is willing to throw in man-power for better indexer support and
cmake support by MBS, they might want to save afford.
- My MBS-based cmake4eclipse plugin shows how to integrate the
CompileCommandsJsonParser.class into MBS for indexer support.
- Renesas could decide to become co-maintainers of cmake4eclipse (or adopt its
parser for CDT).

Anyway, IMHO the problems with MBS are:
- It is an experiment to generate build scripts based on stuff edited in a
- Its GUI (and default makefile-build-script-generator) allows users to
specify to build *one* artifact per project only. Gives top user-experience
for a hello-world project, but if your project is 'Compiler with its
accompinying runtime libs' it gets cumbersome.
- MBS theoretically allows vendors to integrate a build-script-generator that
gets its configuration from a file but users will still be be confused by
project property tabs that have no effect (e.g. *project artifact* settings)

Cd wrttn wtht vwls s mch trsr.

cdt-dev mailing list

Renesas Electronics Europe GmbH
Registered Office: Arcadiastrasse 10
DE-40472 Duesseldorf
Commercial Registry: Duesseldorf, HRB 3708
Managing Director: Carsten Jauch
VAT-No.: DE 14978647
Tax-ID-No: 105/5839/1793

Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

Back to the top