public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Jason Carrete <jasoncarrete5@gmail.com>
To: crossgcc@sourceware.org
Subject: Config portability
Date: Fri, 2 Feb 2024 18:13:23 -0500	[thread overview]
Message-ID: <5df2449f-916a-4023-94a4-18d17a82f2f6@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 304 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2024-02-02 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 23:13 Jason Carrete [this message]
2024-02-02 23:43 ` Tommy Murphy
2024-02-02 23:43 ` Chris Packham

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=5df2449f-916a-4023-94a4-18d17a82f2f6@gmail.com \
    --to=jasoncarrete5@gmail.com \
    --cc=crossgcc@sourceware.org \
    /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).