From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Maksim Kislyakov Newsgroups: gmane.emacs.devel Subject: Re: Why does Emacs's source tar archive contain *.elc files? Date: Wed, 17 Jul 2024 16:56:55 +0300 Message-ID: <8369b687-fdfe-443e-8861-e2fe4f90e487@kmaksim.dev> References: <141f27f6-9e8e-49dc-a0f3-ecbf882f2f14@kmaksim.dev> <86a5iggnv1.fsf@gnu.org> 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="7230"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 17 18:04:20 2024 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 1sU78d-0001cJ-Ps for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Jul 2024 18:04:19 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sU77X-0000K9-I1; Wed, 17 Jul 2024 12:03:12 -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 1sU59V-0006ov-9K for emacs-devel@gnu.org; Wed, 17 Jul 2024 09:57:07 -0400 Original-Received: from smtpout5.timeweb.ru ([92.53.116.15]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sU59S-0007Xl-F3; Wed, 17 Jul 2024 09:57:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kmaksim.dev ; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=BEs7RJRD/0DNF+PtVzdrL6y7IuOJPwQ7Se06v7ovOTk=; b=orXbypCPw7DWv5Awzb9xR6ZS4N YQ/fTiHm3Pqd2u6zMbtgSskHuduLI2rHpPUQTSP/vvbyEYAF7jrwtCrRNU5Yrlmr+MFIuhvoNZ+lg LbOpIBHagxHFUlETH/juzmEg12EETLa39/Jwi7SQIJNSc9pF8KpF0IGxbWgHoIDGGTng=; Original-Received: from [37.235.192.120] (helo=[172.16.0.2]) by smtp.timeweb.ru with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from ) id 1sU59L-0005ut-G8; Wed, 17 Jul 2024 16:56:55 +0300 Content-Language: en-US, ru In-Reply-To: <86a5iggnv1.fsf@gnu.org> Received-SPF: pass client-ip=92.53.116.15; envelope-from=mail@kmaksim.dev; helo=smtpout5.timeweb.ru X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Wed, 17 Jul 2024 12:02:51 -0400 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:321756 Archived-At: Thank you for your answer! On 17.07.2024 16:16, Eli Zaretskii wrote: >> Date: Wed, 17 Jul 2024 15:45:48 +0300 >> From: Maksim Kislyakov >> >>  I was playing around compiling Emacs from sources. At some point, I >> have found out that '*.tar' files with Emacs sources contain '*.elc' files. >> >> As far as I understand, 'elc' is byte-compiled version of 'el' file. > Yes. > >> - Why does the tar archive contain compiled sources? That seems strange. >> Source code archive (which you use to compile program) contains compiled >> code. > For the same reason the tarball includes other generated files: Info > manuals, the configure script, the few generated *.el files, the > configure script, etc.: it makes the build faster and requires fewer > development tools to be installed on the user's machine. > > The actual line between the files that are provided in the release > tarballs and those which don't is NOT whether they are "compiled" in > some sense, but rather whether they are architecture-dependent or not. > The results of compiling *.c files are architecture-dependent, and > likewise the *.eln files produced by native compilation of Lisp code. > So we don't include those architecture-dependent files in the source > tarballs. > >> - Also, what will happen if I apply some patch before compiling Emacs? >> 'el' file's modification time will be newer that corresponding 'elc' >> file's modification time. > If you modify some of the *.el files, then the "make" command will > recompile them and produce updated *.elc files. Similarly with the > *texi source files of the Info manuals, and other generated files > which come with the tarball.