Hi,

I am planning to add RX Toolchain for the Renesas architecture (for RX65N 
board) with reference to the build steps provided in the below URL,
https://gcc-renesas.com/wiki/index.php?title=How_to_build_the_RX_Toolchain_under_Ubuntu_14.04

I checked on the local build time for the container when RX Toolchain is added. 
Build time would be increased to 30 minutes (approx).

I'm new to the docker container setup in the github. Is there any reference 
available for publishing the intermediate container and using it when building?

Does "publish the intermediate container" mean pushing the Dockerfile (with RX 
toolchain) to incubator-nuttx-testing repo?

Best Regards,
Ramya N
________________________________
From: Brennan Ashton <bash...@brennanashton.com>
Sent: 11 August 2020 10:29
To: dev@nuttx.apache.org <dev@nuttx.apache.org>
Subject: Re: Pre-check flow

________________________________
 **This is an external email. Please check the sender’s full email address (not 
just the sender name) and exercise caution before you respond or click any 
embedded link/attachment.**
________________________________

On Mon, Aug 10, 2020, 9:42 PM Xiang Xiao <xiaoxiang781...@gmail.com> wrote:

>
>
> > -----Original Message-----
> > From: Ramya N <ramy...@tataelxsi.co.in.INVALID>
> > Sent: Monday, August 10, 2020 10:42 PM
> > To: dev@nuttx.apache.org
> > Subject: Pre-check flow
> >
> > Hi,
> >
> > 1. In the NuttX Pre-check flow, docker image is built from "Pre-built
> Toolchain" of each architecture. If the pre-built toolchain
> is not
> > available, can we build the toolchain from "Toolchain Source Code" in
> the Dockerfile of incubator-nuttx-testing repo?
> >
>
> I think so, but Brennan can give more input.
>

We can although I would like more details on this. I don't want to give
people horrible build times for the container so it might make sense to
publish the intermediate container as well and use that when building.

Can you share what architecture and compiler you are wanting to add?

--Brennan

>
________________________________
Disclaimer: This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you are not the intended recipient of this message , or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply email and then delete this message and any attachments. If you are not 
the intended recipient, you are hereby notified that any use, dissemination, 
copying, or storage of this message or its attachments is strictly prohibited. 
Email transmission cannot be guaranteed to be secure or error-free, as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. The sender, therefore, does not accept 
liability for any errors, omissions or contaminations in the contents of this 
message which might have occurred as a result of email transmission. If 
verification is required, please request for a hard-copy version.
________________________________

Reply via email to