From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Augustin_Ch=c3=a9neau_=28BTuin=29?= Newsgroups: gmane.emacs.devel Subject: Re: [PROPOSAL] Builder, a build system integration for Emacs Date: Sun, 21 May 2023 21:33:00 +0200 Message-ID: <3f68f4bc-d426-0bcc-1329-674c12b29386@mailo.com> References: <95980ffc-86e7-ad54-4a20-539d8c6ea5d0@mailo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5726"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Cc: emacs-devel@gnu.org To: Jim Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 21 21:34:02 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q0ooc-0001H3-6Z for ged-emacs-devel@m.gmane-mx.org; Sun, 21 May 2023 21:34:02 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q0onk-0005lU-Od; Sun, 21 May 2023 15:33:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q0oni-0005ji-Lj for emacs-devel@gnu.org; Sun, 21 May 2023 15:33:06 -0400 Original-Received: from msg-1.mailo.com ([213.182.54.11]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q0ong-00068a-Lj for emacs-devel@gnu.org; Sun, 21 May 2023 15:33:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1684697581; bh=/I8ZGK6YnfaEz40j9GpH9V/XKZeKy3baH/7WC5Sne+g=; h=X-EA-Auth:Message-ID:Date:MIME-Version:Subject:To:References:From: Cc:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=g+MIZE43gjG459Ge5pUWCZ0VgVEYi4h9Qp/4ONxRg3ufaZNw6gpa3PBUP1F7lXy9T FSpHpOojvw/ltIWZRRacB+sYulR89QrgYox/Zmo/0uVxhvCOETv0eGcu6gnU737Ybt 5+6Z47paIatIQ/WN6vpZuo/+2rpi47wK/xKGuoOM= Original-Received: by b221-2.in.mailobj.net [192.168.90.22] with ESMTP via ip-20.mailobj.net [213.182.54.20] Sun, 21 May 2023 21:33:00 +0200 (CEST) X-EA-Auth: 84bQO7ET3rosiP+06TQF1e8MD/L8bM7cnO6iMRFtnn91s08dU5P945BlfhetnC/xNSLse01IBpSTU8e+eJIfrLAXnBZxatAG Content-Language: fr, en-US In-Reply-To: Received-SPF: pass client-ip=213.182.54.11; envelope-from=btuin@mailo.com; helo=msg-1.mailo.com X-Spam_score_int: -21 X-Spam_score: -2.2 X-Spam_bar: -- X-Spam_report: (-2.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.098, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306254 Archived-At: Le 21/05/2023 à 19:24, Jim Porter a écrit : > This loos interesting. I've actually been working (though not much > lately) on a similar project by the name of "taco" (Tool Aware > COmpilation[1]): https://github.com/jimporter/taco > Nice, thanks for letting me know! > I haven't had time to look over your project in detail, but I see a few > main differences. The biggest one is that taco divides the build process > into mostly-independent stages. For example, an Autotools project uses > three stages: preconfigure (generate "configure" from "configure.ac"), > configure (generate "Makefile" from "configure"), and build (run the > Makefile). This way, other build configurators that generate Makefiles > can just piggyback on the "Make" builder for the actual compilation. > Interestingly I already thought about chaining build systems, but I wasn't sure how to implement it. Unfortunately the main drawback of your method is that you can't easily switch between a debug or release mode (if I understood your code correctly). Also, what if an intermediate step is used in two different context, both with different next step? I thought of something with a list of targets names, but I'll need to think more deeply. Currently you could achieve the same manually, but I agree it's not very convenient.