linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
	Nathan Field <ndf@ghs.com>
Subject: Re: Cross Compiler running under Win32
Date: Thu, 27 Nov 2003 09:16:19 -0800	[thread overview]
Message-ID: <3FC63163.8020304@kegel.com> (raw)
In-Reply-To: <3FC5CF65.1060109@imc-berlin.de>


Steven Scholz wrote:
> I think Cygwin is much too much overhead for just compiling a small
> application.
> I was told that I could take just the GCC package from Cygwin without
> installing all of it.
>
> "licensing fee for cygwin" ???
> So it's not free?

It is free, if you obey the GPL, and distribute source code.
Otherwise, you can get a commercial license.

> Could we just take the GCC package and the DLL and distribute it
> together with our software and install it on our costumers Windows PCs?
> We have to be able to generate and (cross-)compile code on our costumers
> PCs that is than transfered to our devices and executed.

Yes.  However, this is complicated by the fact that if the
user already has cygwin installed, its cygwin DLL may conflict
with yours.   It's not a trivial problem to address.
If you're willing to keep your package up to date with
the latest Cygwin all the time, it's probably managable;
in case of conflict, the user can update both Cygwin
and your tools and get things working again.

We actually did some of that at Ixia, and I have the scars to prove it :-)
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-27 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 13:55 Cross Compiler running under Win32 Steven Scholz
2003-11-26 18:52 ` Nathan Field
2003-11-27  3:19 ` Dan Kegel
2003-11-27 10:18   ` Steven Scholz
2003-11-27 17:16     ` Dan Kegel [this message]
2003-12-01 18:26 ` Mark A. Greer

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=3FC63163.8020304@kegel.com \
    --to=dank@kegel.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ndf@ghs.com \
    --cc=steven.scholz@imc-berlin.de \
    /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 NNTP newsgroup(s).