X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=ni9x/GnEne1yU4EGidla4ynwaF1HiCbgDLDnqbnvLxU
	ngcoZrC+0H5OHoaGZFvdz4AYKYwcGXjx5WML1tjMxSD2RyqJWfnkqARHr32dcRD1
	x9Br44F7PzlRkezx+GGORglv15mUE5xGtbH67TFoPTxhiDFoDqIXREN6t2CtVqGk
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=dFH/xo6qz8lBduNEx+rtHSRI+JA=; b=NI/5U+jiEePMt68V7
	tFpWPJ8buweqLHZRcBXV9jeVdgpf2lrvwDrEpsIB9CgVHh0qUf0LpyrTfLsXRIGv
	VuqlxnFFPmPjeUgjAqbmRfdp3b05rZkmgpL+VDy8Vsv+q6hFmBLMRLlEuRlAHQov
	0K4pez08H9iPo9eEww3mTN+prY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_LX autolearn=ham version=3.3.1
Message-ID: <51B6AAD4.6070209@tlinx.org>
Date: Mon, 10 Jun 2013 21:43:00 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: GCC and symlink are incompatibility on 64-bit windows
References: <CALsFeoxG1mM4g7ftUvRbANLFC0EWwGiwQ51ZRZRJcDXU1McwVw AT mail DOT gmail DOT com>	<20130611025401 DOT GA5553 AT ednor DOT casa DOT cgf DOT cx> <CALsFeoxDSZ7OFszf-a9YDJ2vWOx2jJPy+LPQUZyvrwtVObiVVg AT mail DOT gmail DOT com>
In-Reply-To: <CALsFeoxDSZ7OFszf-a9YDJ2vWOx2jJPy+LPQUZyvrwtVObiVVg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Lu Sheng wrote:
> how can I use cygwin tools, if I want to compile the object file in
> cygwin and invoke it in windows python?
----
If you compile under cygwin, you are designing it to run under posix (linux
like environment) -- not under windows.

If you want it to run under window you need to use windows
tools.

It might compile under the mingw tools -- which are gnu tools adapted to windows.

But they don't support a linux-like environment -- so if the program you want to run
uses posix/linux features it won't work unless you rewrite the portions
that use linux to do some equivalent thing in windows (i.e. it's not a trivial 
task).

Looking at the lxml website -- there is no windows port or support.

If you want to run it you need to run it on a posix-compatible or linux
compatible platform.

Windows isn't either.

It might run under cygwin -- as it is a posix compatible platform -- you might
ask someone on whatever mailing lists the lxml people hve.

There is a python that runs under cygwin as well.  I.e. if your concern was
to run it on python that ran on your windows 'box', then you can run the cygwin
version of python on your windows box -- but if you need to run the windows
version of python, you  have a long road ahead of you to get this workign.




--
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