public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Some first questions.
Date: Tue, 29 Oct 2013 18:13:00 -0000	[thread overview]
Message-ID: <20131029173940.GA5229@ednor.casa.cgf.cx> (raw)
In-Reply-To: <001001ced4c3$41168830$c3439890$@org>

On Tue, Oct 29, 2013 at 05:23:50PM +0100, Gert Koefoed Andersen wrote:
>Hello list.
>
>I have some first questions for cygwin works on windows 7 by compile sources
>I normally just fine compile on my linux systems but not like to compile
>well and by cygwin.
>The sources I trying to compile is been packed on linux with tar archiwing
>program so I can get the sources over to windows 7 and cygwin.
>
>So it is then this then.
>1. where is the best place to unpack the sources for compile by cygwin.

That isn't really a question that is answerable.  Make a directory and
extract the files to it.  No one can tell you the name of a directory to
use.

You can create a directory in your home directory or, e.g., create a
/usr/src/foo directory and extract files there.  It's entirely up to
you.

>   My windows cygwin is installed on c:\cygwin and by installing cygwin is
>the cygwin download sources been put at k:\cygwinsrc.
>2. if the extra sources is best to be places at k:\cygwin, then is it then
>best to handle them for cygwin ?

Cygwin doesn't use paths like c:\cygwin.  If your cygwin installation is
c:\cygwin then that means that is your root directory: /.  k:/cygwin
would be referenced, by Cygwin, as /cygdrive/k/cygwin.  It's ok if you
want to put files there but you should use the Cygwin method for referencing
this location.

>3. Then is it that - the sources have makefiles .cyg and other compilers +
>some main configs like Makefile and huskymak.cfg.
>When I have copied the file makefile.cyg to makefile.cfg and then have this
>file in the main home dir for example - \...\husky\smapi\ and then is got in
>to \smapi source dir and then run make to compile the sources for smapi goes
>it fine to I getting a error of gcc -mno-cygwin and then error 2 of it not
>can find some file it should make and when I checking out for the file is it
>where it should be by not compile to make a .o files for more compile
>finish.

-mno-cygwin is an ancient option that is no longer supported (it only
took me 10 years or so to get rid of it).  If you are building binaries
which don't use Cygwin then you should use a mingw compiler, installed
from setup.exe.  Or, you should just be using MinGW directly from
mingw.org.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-10-29 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 17:15 Gert Koefoed Andersen
2013-10-29 18:13 ` Christopher Faylor [this message]
2013-10-30  7:05 ` Andrey Repin
2013-11-03 19:05 ` D. Boland
2013-11-04 10:02   ` SV: " Gert Koefoed Andersen
2013-11-04 17:03     ` D. Boland
2013-11-08 17:04       ` D. Boland
2013-11-08 18:03         ` SV: " Gert Koefoed Andersen
2013-11-09  9:12           ` D. Boland

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=20131029173940.GA5229@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.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).