From: Ben Dougall <bend@freenet.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: embedding gcc?
Date: Tue, 10 Dec 2002 06:18:00 -0000 [thread overview]
Message-ID: <3C3CD96A-0C4A-11D7-BD32-0030653F9ECE@freenet.co.uk> (raw)
In-Reply-To: <3DF54E34.29414786@centropolisfx.com>
Gokhan,
> GCC seems to be actually too big for your scripting system needs to be
> distributed easily.
Size isn't an issue that effects embedding or not embedding. If my app
requires GCC, whether it's embedded or not, will still result in the
same total download size – the difference would be one download and
install, or two separate downloads and installs.
> In fact make sure to read the license agreement, you might not be able
> to do this legally, I mean sell the freely distributed software with
> your software bundle as if you did something new. I believe GCC has to
> be distributed in its own package, NOT in such bits and pieces for
> profiteering...
As I understand that sort of license, so long as you keep the source
code open it's fine – you can do what ever the hell you want with it.
If you're mingling your code with their code, that would mean your own
code would need to be open source too.
But what I want to know about the technical side of this. How,
technically could I go about this? Any pointers as to where or how to
start? I'm also thinking there must have been a previous project that
needed to include GCC in some way and would be very interested to know
if anyone knows of such a thing?
Thanks, Ben.
next prev parent reply other threads:[~2002-12-10 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1039456162.9884.ezmlm@gcc.gnu.org>
2002-12-09 12:28 ` Ben Dougall
2002-12-09 18:13 ` Gokhan Kisacikoglu
2002-12-10 6:18 ` Ben Dougall [this message]
[not found] <583E84A77A2FCB4F967E6CD9B0CA4AF71BD028@nt-server.kreuter>
2002-12-11 8:37 ` Ben Dougall
2002-12-11 9:54 ` Buddy Lott
2002-12-07 4:19 Ben Dougall
2002-12-07 5:02 ` bjorn rohde jensen
2002-12-08 11:59 ` Andrea 'fwyzard' Bocci
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=3C3CD96A-0C4A-11D7-BD32-0030653F9ECE@freenet.co.uk \
--to=bend@freenet.co.uk \
--cc=gcc-help@gcc.gnu.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).