This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin gcc mingw python development environment configuration
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Matt Thomas <iMattThomas at zoho dot com>, cygwin at cygwin dot com
- Date: Thu, 29 Jan 2015 05:34:37 +0300
- Subject: Re: Cygwin gcc mingw python development environment configuration
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20150129T011932-259 at post dot gmane dot org>
- Reply-to: cygwin at cygwin dot com
Greetings, Matt Thomas!
> I need to find references describing methods to configure:
> - Cygwin gcc environment
> - the Cygwin version of MingGW environment
> - gcc or mingw configurations for python compilations
> My questions are:
> - how to include all needed gcc source paths (of many)
> - how to include all needed library paths
> - do the ar as nm and other tools need to be specified in a configuration?
These are very generic questions, not related to Cygwin per se.
Grab first available book on GCC and read the answers from there.
> - how to include gcc/mingw options when needed for python setup.py situations
I don't know, what you mean here, but I suppose the answer is the same.
Cygwin aims to provide POSIX compatible(as much as possible within operating
system restrictions) execution environment.
This is NOT an emulation, but a compatible API and a set of tools.
Some caveats exist, as with any compatibility layer, but your mileage may
vary. Depends on the nature of your applications, you may never face them.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 29.01.2015, <05:27>
Sorry for my terrible english...
--
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