From owner-freebsd-libh Mon Aug 12 13:41: 1 2002 Delivered-To: freebsd-libh@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60A437B400 for ; Mon, 12 Aug 2002 13:40:58 -0700 (PDT) Received: from postal.sdsc.edu (postal.sdsc.edu [132.249.20.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372CE43E65 for ; Mon, 12 Aug 2002 13:40:58 -0700 (PDT) (envelope-from okumoto@SDSC.EDU) Received: from multivac.sdsc.edu (IDENT:oDEUStiGjqF8oXMGR/2/fBVgpRTF/vYI@multivac.sdsc.edu [132.249.20.57]) by postal.sdsc.edu (8.11.6/8.11.6/server/44) with ESMTP id g7CKeq120337; Mon, 12 Aug 2002 13:40:52 -0700 (PDT) Received: by multivac (8.11.6+Sun/1.11-SolarisClient) id g7CKeon14134; Mon, 12 Aug 2002 13:40:50 -0700 (PDT) To: Antoine Beaupre Subject: Re: libh changes that I would like to get comments on. References: <5988A99A-AE04-11D6-BD85-0050E4A0BB3F@anarcat.ath.cx> Cc: freebsd-libh@FreeBSD.ORG From: Max Okumoto In-Reply-To: Antoine Beaupre's message of "Mon, 12 Aug 2002 11:01:15 -0400" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: 12 Aug 2002 13:40:50 -0700 Message-ID: Lines: 57 Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Antoine Beaupre writes: > >> One quick note: the new system doesn't seem to build multiple back > >> ends as the old one did (none, text, graphics, text+graphics). This is > >> mandatory. We need a text-only backend for the floppies. > > > > I will look into static linking. With swig it shouldn't > > be that hard. I had assumed that if we used dynamic > > linking the over all system would be smaller. > > Yes. But you need to link with pretty big libraries. libc is the first > that comes to mind: > > -r--r--r-- 1 root wheel 579412 Jun 11 00:18 /usr/lib/libc.so.4 > > That's just too much for a floppy, especially when there's a lot of code > in there that is simply not used. > > > From my understanding we only need one static binary, and that would > > be the 'text only' version. (Unless you are building tcl without > > dynamic loading built in.) If the system running libh has graphic > > the Qt module can be loaded in dynamically. > > Well, I see it a little differently. I think we should be able to link > anything we want statically, simply by setting NOSHARED=yes somewhere. > > It's a different issue than with *what* (qt, tvision, nothing) to link, > IMHO. I really like the idea of choosing what gets compiled in and what > doesn't, and the new build system shouldn't loose that. I've just checked and its not much more effort to build the staticly like stuff. > > The old system (hsystem) and Swig are equivalent. They both take > > in a description of the C++ interfaces and create wrappers functions > > that can be called from the tcl interpreters. [stuff deleted] > This is really nice. And I guess it means that libh won't have to be > linked with SWIG itself. SWIG is just used in the build, right? > Right. There is alot less stuff that gets linked in compared to the old scheme. Alot of the Pointer stuff goes away. > Okay. Please provide a roadmap of how this change will have to go, which > files will have to be merge/removed, from which branch, and which > repo-copies will have to be done, I'll try to tackle this ASAP. I will write up a roadmap in a seperate email. Thanks for taking the time to looking this work. Max Okumoto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message