From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from lnx503.hrz.tu-darmstadt.de ([130.83.156.232])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <tim01@vlsi.informatik.tu-darmstadt.de>)
	id 1SRW5D-0007Gr-MU
	for ptxdist@pengutronix.de; Tue, 08 May 2012 00:07:08 +0200
Received: from mailserver3.hrz.tu-darmstadt.de (lnx504.hrz.tu-darmstadt.de
	[130.83.156.233])
	by lnx503.hrz.tu-darmstadt.de (8.14.4/8.14.4/HRZ/PMX) with ESMTP id
	q47M76Gu029685
	for <ptxdist@pengutronix.de>; Tue, 8 May 2012 00:07:07 +0200
	(envelope-from tim01@vlsi.informatik.tu-darmstadt.de)
Received: from [213.157.5.239] (helo=hydra.localnet)
	by mailserver3.hrz.tu-darmstadt.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69) (envelope-from <tim01@vlsi.informatik.tu-darmstadt.de>)
	id 1SRW5C-0002HC-M5
	for ptxdist@pengutronix.de; Tue, 08 May 2012 00:07:06 +0200
From: Tim Sander <tim01@vlsi.informatik.tu-darmstadt.de>
Date: Tue, 8 May 2012 00:07:05 +0200
References: <CAM7q1L=y5D2N0oBLVdNCKhQ8C0ANgwHZ5YPK6JsgZ1QG5mf=Mw@mail.gmail.com>
In-Reply-To: <CAM7q1L=y5D2N0oBLVdNCKhQ8C0ANgwHZ5YPK6JsgZ1QG5mf=Mw@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <201205080007.05151.tim01@vlsi.informatik.tu-darmstadt.de>
Subject: Re: [ptxdist] Generate Developer SDK from Ptxdist
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

Hi Jeff
> I'm looking to see if anyone else is using Ptxdist to generate an SDK along
> with the BSP.  We are supporting Qt in our BSP and I would like to create a
> stand alone developer workstation for our target.  I see there is a host-qt
> built with the BSP but it's configured differently than the target - which
> obviously makes sense.  For my use case, would it make sense to override
> the host-qt install to mirror that of target except for the windowing (QWS
> vs X11)?  Or would you suggest building the host-qt outside of ptxdist?  My
> goal is to build a developer VM image so a developer can compile and test
> the application on x86 and then just cross compile the app for target
> deployment.  I already was able to assemble the cross compiled Qt libs from
> ptxdist and I can cross compile an app using Qt Creator.  I am just trying
> to determine the best way to handle the host Qt libs.
> 
> Any feedback or suggestions are much appreciated.
I have just used the packaging of our distribution and created a meta package 
to pull in the toolchain, qt and some other dependencies. 

As far as i know host-qt does not support host tools but only cross compiling, 
so i went for the easier way and installed the qt devel packages from the 
distribution. To build a meta package in debian/ubuntu you can use equivs and 
just add all your dependencies in there. For creating the repository i used 
reprepo. Thats all debian stuff don't have much experience with building 
packages and repositories for rpm based distros.

Hope this helps
Tim

-- 
ptxdist mailing list
ptxdist@pengutronix.de