From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: Platform Dependent Code Date: Sat, 21 Jun 2008 09:17:20 +0530 Message-ID: References: <20080620101747.BMG51159@expms4.cites.uiuc.edu> <8763s3elhj.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1214020058 11325 80.91.229.12 (21 Jun 2008 03:47:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Jun 2008 03:47:38 +0000 (UTC) To: jsestri2@uiuc.edu, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 21 05:48:22 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K9u5N-0004yT-AE for ged-emacs-devel@m.gmane.org; Sat, 21 Jun 2008 05:48:21 +0200 Original-Received: from localhost ([127.0.0.1]:38565 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K9u4Y-0001I6-Ay for ged-emacs-devel@m.gmane.org; Fri, 20 Jun 2008 23:47:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K9u4S-0001GD-Rh for emacs-devel@gnu.org; Fri, 20 Jun 2008 23:47:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K9u4R-0001Ek-CQ for emacs-devel@gnu.org; Fri, 20 Jun 2008 23:47:24 -0400 Original-Received: from [199.232.76.173] (port=42162 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K9u4R-0001Ed-97 for emacs-devel@gnu.org; Fri, 20 Jun 2008 23:47:23 -0400 Original-Received: from ti-out-0910.google.com ([209.85.142.188]:58068) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K9u4Q-0003cj-R2 for emacs-devel@gnu.org; Fri, 20 Jun 2008 23:47:23 -0400 Original-Received: by ti-out-0910.google.com with SMTP id u5so676542tia.10 for ; Fri, 20 Jun 2008 20:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=eMS9i25UKwf4Kvdok9HJlXNNJhj/Yzb7Q/20A+rQzJI=; b=tlnejX2LoeR/JsUXEq8a9qLGxXzCOGsQK5QhhwDDu+n138LdkNYHK9C3VyTF5IaAcP CQ3rppZPrxTNfPZx+FnZ/ulS53u2LIjHOwMJs8T8Cu63hQE+nusCXniDbIe3/y6PrtRC 7u5OrC5fAbBRmQB34bxeSNzva7VXTBuqwLLoc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IfuOB5MYCMHMni+AcEdAYJDAoDiCjxi7BGJQ5HtO0ms2SdQwoR9Y7cty0eK0bghQmn CZDLWvnSW9IMqT4z4Cag3h56FmT1aGb8VkqotESpVKp/HVvjPoINIKh14Rsch/49y2Sr OIOYjBiFsKeqX/pB5L2JphxGnrDk3nXmJo7dI= Original-Received: by 10.110.84.2 with SMTP id h2mr3480365tib.45.1214020040606; Fri, 20 Jun 2008 20:47:20 -0700 (PDT) Original-Received: by 10.110.46.18 with HTTP; Fri, 20 Jun 2008 20:47:20 -0700 (PDT) In-Reply-To: <8763s3elhj.fsf@stupidchicken.com> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:99580 Archived-At: Hello, On Sat, Jun 21, 2008 at 4:56 AM, Chong Yidong wrote: > writes: > >> How much of emacs is platform dependent code? I am wondering how much >> code has to be replaced if you wanted to port emacs to a new platform >> essentially: How much of emacs is native c code / libraries and how >> much is done through lisp code? > > Almost all the platform-dependent code is in C and concerns > terminal/window system communications. See the w32* and mac* files in > the source tree for an example. The rest of the work is a matter of > juggling compilation switches, identifying system call names, etc. > > (If you provide some information about what platform you are interested > in, maybe someone could be more helpful.) I feel the most complicated would be the generating the emacs executable by dumping a process with elisp code loaded (bootstrapping). I remember when working in the OpenVMS labs, on Itanium platform, that was the only missing piece in getting a full blown working emacs. -dhruva -- Contents reflect my personal views only!