From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Aw: Re: Strange errors with gcc and top, even after rebaseall
Date: Sun, 27 Aug 2017 13:43:00 -0000 [thread overview]
Message-ID: <97f2158f-94d0-66e7-f506-4cdc367a8929@gmail.com> (raw)
In-Reply-To: <trinity-7b987106-f557-41b8-870b-b254245f3676-1503784312569@3c-app-webde-bap64>
On 8/26/2017 5:51 PM, nobodyO@web.de wrote:
> Hi,
>
>> I guess I don't understand why you thoink you'd need two installations
>> for two build environments.Â
> Â
> I have installed one Cygwin installation package from department A, for
> building software a, and another from department B and which has some
> tools which were developed here, for building software b.
>
You only need one Cygwin install and the self developed tools reside
within that install; I'll call Cygwin and your tools (TOOLS). Your
source for each department is separated by projects.
You set your PATH to point to your TOOLS. You change to a project
directory and issue the project build command (MAKE). Once the project
is successfully built you create a package to deliver (MAKE package).
There may be reasons to have multiple environments of Cygwin but those
environments must be totally separate and the reasons should only be if
there are differences in the Cygwin environment that are required for a
specific job. What you've presented doesn't appear to be a required reason.
--
cyg Simple
--
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
next prev parent reply other threads:[~2017-08-27 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 21:39 nobodyO
2017-08-24 2:16 ` cyg Simple
2017-08-24 7:16 ` Aw: " nobodyO
2017-08-24 11:16 ` Eliot Moss
2017-08-25 19:07 ` nobodyO
2017-08-26 3:50 ` Andrey Repin
2017-08-26 17:16 ` Achim Gratz
2017-08-26 21:51 ` Aw: " nobodyO
2017-08-27 13:43 ` cyg Simple [this message]
2017-08-29 2:49 ` Kaz Kylheku
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=97f2158f-94d0-66e7-f506-4cdc367a8929@gmail.com \
--to=cygsimple@gmail.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).