From: Chris Packham <judge.packham@gmail.com>
To: Jason Carrete <jasoncarrete5@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: Config portability
Date: Sat, 3 Feb 2024 12:43:57 +1300 [thread overview]
Message-ID: <CAFOYHZDXZw8RVucEe9xUhqPKirCMR+dViqoQdafZcQAbjE8+Hw@mail.gmail.com> (raw)
In-Reply-To: <5df2449f-916a-4023-94a4-18d17a82f2f6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Yes they should be portable. Running ct-ng upgrade config on the 2nd
machine will also help.
On Sat, 3 Feb 2024, 12:14 pm Jason Carrete via crossgcc, <
crossgcc@sourceware.org> wrote:
> Hi,
>
> After creating and saving a configuration with `ct-ng menuconfig`, is
> the generated ".config" file portable? By portable, I mean can I copy
> the generated config file to a different machine with possibly different
> packages installed and build a toolchain all the same?
>
> Thanks,
>
> Jason
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
prev parent reply other threads:[~2024-02-02 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 23:13 Jason Carrete
2024-02-02 23:43 ` Tommy Murphy
2024-02-02 23:43 ` Chris Packham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFOYHZDXZw8RVucEe9xUhqPKirCMR+dViqoQdafZcQAbjE8+Hw@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=jasoncarrete5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).