From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from hbe.hbelightingsystems.com ([213.239.196.253]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RLcT5-0002fz-0T for ptxdist@pengutronix.de; Wed, 02 Nov 2011 16:11:08 +0100 Received: from localhost (localhost [127.0.0.1]) by hbe.hbelightingsystems.com (Postfix) with ESMTP id 60C571E8002 for ; Wed, 2 Nov 2011 16:11:06 +0100 (CET) Received: from hbe.hbelightingsystems.com ([127.0.0.1]) by localhost (hbe.hbelightingsystems.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 9GDLIart054g for ; Wed, 2 Nov 2011 16:11:05 +0100 (CET) Received: from [192.168.1.4] (ip51ce2bef.speed.planet.nl [81.206.43.239]) (Authenticated sender: erwin@hbelightingsystems.com) by hbe.hbelightingsystems.com (Postfix) with ESMTP id 98C9D1E8001 for ; Wed, 2 Nov 2011 16:11:05 +0100 (CET) Message-ID: <4EB15D97.2050905@erwinrol.com> Date: Wed, 02 Nov 2011 16:11:19 +0100 From: Erwin Rol MIME-Version: 1.0 Subject: [ptxdist] Application Development on Ptxdist based OS's Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist Hey all, a while back I asked if it was possible to split an ptxdist build in two parts, one for the (stable) OS and one for the application. On that question I got some interesting answers that made me wonder; How do others do their application development on ptxdist? From origin Ptxdist is a distribution building tool, so it assumes all applications are finished and combines all parts in a running distribution. And it does a great job, I really can't complain about that. But what if the applications are still in development, they need to be edited, cross-compiled, debugged. And there is where Ptxdist is not so great, at least that's my experience. So how do other people do that ? I read some ppl just don't use Ptxdist at all and just compile their applications in a different way and "install" them on the finished Ptxdist OS. But that duplicates the whole cross-chain stuff, like compiler, libraries and headers. I have seen other build systems that seem to export some "API" for use by applications developers. Maybe something like that can be done with Ptxdist too, for example exporting the sysroot-target directory and use that to build applications. Anny other people with wild ideas and nice custom Ptxdist enhancements that they want to share ? - Erwin -- ptxdist mailing list ptxdist@pengutronix.de