From owner-freebsd-embedded@FreeBSD.ORG Thu Dec 1 08:00:17 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA261106564A for ; Thu, 1 Dec 2011 08:00:17 +0000 (UTC) (envelope-from gonzo@hq.bluezbox.com) Received: from hq.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id 874388FC1B for ; Thu, 1 Dec 2011 08:00:17 +0000 (UTC) Received: from [24.87.53.93] (helo=[192.168.1.116]) by hq.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1RW1Z0-000OLL-Pk; Thu, 01 Dec 2011 00:00:15 -0800 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Oleksandr Tymoshenko In-Reply-To: <96407605-79A9-4AE3-AC2F-13BD97943153@lassitu.de> Date: Thu, 1 Dec 2011 00:00:13 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <447CC818-CEA3-46B9-A15F-E0FA737B0EB4@bluezbox.com> References: <4ED6FD47.6050704@bluezbox.com> <96407605-79A9-4AE3-AC2F-13BD97943153@lassitu.de> To: Stefan Bethke X-Mailer: Apple Mail (2.1084) Sender: gonzo@hq.bluezbox.com X-Spam-Level: ---- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: > >> - Package builder works only on installed port. > > Have you looked at pkgng yet? The wiki page says it can create a package from a separate directory tree. No, not yet. By "Package builder" I meant package-building targets of ports Makefiles. pkg_create can work on directory tree + setof pre-generated files. It's just that at the moment we use "pkg_create -b" to create package archive. [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Cc: freebsd-embedded@freebsd.org Subject: Re: Ports cross-compilation X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2011 08:00:18 -0000 >=20 >> - Package builder works only on installed port. >=20 > Have you looked at pkgng yet? The wiki page says it can create a = package from a separate directory tree. No, not yet. By "Package builder" I meant package-building=20 targets of ports Makefiles. pkg_create can work on directory=20 tree + setof pre-generated files. It's just that at the moment=20 we use "pkg_create -b" to create package archive. >> - Makefile for cross-compilable port should be split into three = parts: >> common, native, cross. It's not clear who should maintain cross part >> though. >=20 > =46rom many previous discussions, people are reluctant to add files to = all ports because of the filesystem and VCS bloat that causes. Also, = considering the number of ports there are in the tree, and how well = maintained many of the lesser ones are, any solution that requires no or = very little changes to each port would stand a much bigger chance of = being implemented successfully. As I told - getting all ports cross-compilable is impossible.=20 We're talking about most-used in embedded environment ports. I'd say=20 it's a couple of hundreds. So we need modify only these ports and only=20= if it's really required. Simple ports like converters/base64 will not=20 require modification at all.=20=