From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 24 May 2023 13:28:44 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q1mfd-00CDWN-9x for lore@lore.pengutronix.de; Wed, 24 May 2023 13:28:44 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1q1mfb-0005P4-5i; Wed, 24 May 2023 13:28:43 +0200 Received: from h2.cmg1.smtp.forpsi.com ([81.2.195.163]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q1mfJ-0005Ov-Gm for ptxdist@pengutronix.de; Wed, 24 May 2023 13:28:26 +0200 Received: from lenoch ([91.218.190.200]) by cmgsmtp with ESMTPSA id 1mfGqUcHDPm6C1mfHqIW0o; Wed, 24 May 2023 13:28:24 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=triops.cz; s=f2019; t=1684927704; bh=68uWs0TgQ5Ta9PnBiz+9wSyXYeYQ/jbQOoymlq2Migw=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=SUhMzM9ZXGSLnCb+zp7+inqbK/uXpAleCo1ndyJGacUmXnQYo09ykO+j1SCYWuRxc uQ2yafTsS5YZLMTCFVz6n7EWsQ5o/lghnNf1qtay5MqhPW1A2piQWGjdcCLGA+13wP H0vMiCbhBH6jCzG5DkgenlW+aixq1lbTeKGWFA7DTjzvVqersZexJ1OLfy/hCR+50G YV204OPigAhJHHTcZdydBLpEK7yznfbpQfOzbza0a+2BZT+HbsJrUL3dUSSsrJOh4C dhxgce0Cj1LQaZlOpBA2AAmrrxMa+q+pw3FphYd3GfTTXYl3D0uyoB7P0lPYy6YLnj xJktWfBqK2l4g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=triops.cz; s=f2019; t=1684927704; bh=68uWs0TgQ5Ta9PnBiz+9wSyXYeYQ/jbQOoymlq2Migw=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=SUhMzM9ZXGSLnCb+zp7+inqbK/uXpAleCo1ndyJGacUmXnQYo09ykO+j1SCYWuRxc uQ2yafTsS5YZLMTCFVz6n7EWsQ5o/lghnNf1qtay5MqhPW1A2piQWGjdcCLGA+13wP H0vMiCbhBH6jCzG5DkgenlW+aixq1lbTeKGWFA7DTjzvVqersZexJ1OLfy/hCR+50G YV204OPigAhJHHTcZdydBLpEK7yznfbpQfOzbza0a+2BZT+HbsJrUL3dUSSsrJOh4C dhxgce0Cj1LQaZlOpBA2AAmrrxMa+q+pw3FphYd3GfTTXYl3D0uyoB7P0lPYy6YLnj xJktWfBqK2l4g== Date: Wed, 24 May 2023 13:28:22 +0200 From: Ladislav Michl To: ptxdist@pengutronix.de Message-ID: References: <1978845.jS2lH9ieRG@ada> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1978845.jS2lH9ieRG@ada> X-CMAE-Envelope: MS4wfJzSYg5BrTrGLgJsG7ICjphXMIef3dhskIPqQd2yko2oZ11iE7HTqIFkrQZr59abTjcDcFBPr7Ze7URkoVsEe/ILIiGxZWqzinvCTJMOLwOlsida0LO6 v5ng3lH+LisqRuKFBkK0neLfnxDyqELzZX7UVY0/fq52WNVi3F9aJwg+22iHYzaz+9wGoBLJUrFalg== X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] ptxdist initial impressions X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: Jookia Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hi there, On Wed, May 24, 2023 at 12:34:21PM +0200, Alexander Dahl wrote: > Hello Jookia, > > as a long term user not affiliated with pengutronix I have some comments which > might help. See below. > > Am Mittwoch, 17. Mai 2023, 18:11:31 CEST schrieb Jookia: > > Hello ptxdist friends, > > > > I spent some time over the past few days trying to use ptxdist and > > documenting all the pain I hit in the process. This isn't a criticism > > more just anecdotal data of my experience. Hopefully it's useful to > > smooth down some rough edges. > > > > I'm going to write this up in a psuedo-markdown format in sections, > > sorry if that breaks anyone's workflow. > > > > > > Documentation > > ------------- > > > > First up: Documentation is quite good aside from the 'Getting a working > > environment' section. I will be focusing on this today since I think it's > > probably the most critical problem with ptxdist at the moment: I expect > > that by the end of following this chapter I should have a bootable image > > of some kind and commands for using it, such as with qemu. > > > > The first issue is that I'm told to downloaded files, but I'm not linked > > to them, quoting: > > > > ptxdist-2023.05.0.tar.bz2 > > OSELAS.BSP-Pengutronix-Example.tar.bz2 (or a similar source) > > ptxdist-2019.09.0.tar.bz2 > > OSELAS.Toolchain-2019.09.1.tar.bz2 > > > > The OSELAS website is linked as ptxdist.org that doesn't mention OSELAS > > at all. There is a link to the toolchain but it's a different version. > > I managed to find a BSP for 'Generic' but it's 9 years old. > > +1 > > That has to be improved. There's no easy accessible single platform example > BSP to get your feet wet, and DistroKit is nice for supporting some quite > common SBCs, but is already quite complicated. would something like this be sufficient? diff --git a/doc/environment.rst b/doc/environment.rst index 18aecec4e..670f86a48 100644 --- a/doc/environment.rst +++ b/doc/environment.rst @@ -17,10 +17,13 @@ components which are available to the public). In order to build |ptxdistBSPName|, the following source archives have to be available on the development host: - * ptxdist-|ptxdistVendorVersion|.tar.bz2 + * `ptxdist-|ptxdistVendorVersion|.tar.bz2 `_ * |ptxdistBSPName|.tar.bz2 (or a similar source) - * ptxdist-|oselasTCNVendorptxdistversion|.tar.bz2 - * OSELAS.Toolchain-|oselasTCNVendorVersion|.tar.bz2 + +Additionally, those source archives are needed to build toolchain: + + * `OSELAS.Toolchain-|oselasTCNVendorVersion|.tar.bz2 `_ + * `ptxdist-|oselasTCNVendorptxdistversion|.tar.bz2 `_ Main Parts of PTXdist ~~~~~~~~~~~~~~~~~~~~~ > What's also lacking: some template or documentation on how to start from > scratch without deriving your work from pre existing BSPs. I tried that > lately and put the steps online: > > https://gist.github.com/LeSpocky/31af75ab63bc6f35fd71d53f06b5a50e > > I dropped that link in IRC, but I got no clear signal if that's something to > put into the official ptxdist documentation? I'm hereby sending a clear signal to maintainers that I'd like to see something like that in the documentation ;-) > > The documentation says having a BSP is optional, but there's no > > instructions on how to work without one. It's probably not even a good > > idea to mention this, perhaps ptxdist should provide a skeleton project? > > > > I get the distinct impression the right solution here is to use > > DistroKit as the starter BSP. This isn't mentioned anywhere in the > > documentation but is something I found out about on IRC. > > > > I'm also not a fan of suggesting installing ptxdist. It seems strange to > > lock yourself to a repository of packages that you will need to tweak > > and fix. I would like to see more support for running it in tree. > > Maybe this is some kind of misunderstanding. You would never touch the > distributed/installed ptxdist, but "overwrite" things by placing package rules > with the same name in your BSP. For example if you need a version bump for > libfoo, you could copy /usr/local/lib/ptxdist-2100.01.0/rules/libfoo.make to > your BSP at rules/libfoo.make and adapt it to your needs. or you can even put that into post/ rules in case just upgrading package is sufficient (no configure, etc. changes)