[ 
https://issues.apache.org/jira/browse/FLINK-14066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928507#comment-16928507
 ] 

Dian Fu commented on FLINK-14066:
---------------------------------

I mean that for windows support, we need to consider both building and running 
pyflink on windows.
If you want to just build pyflink on windows(do not need to run it on windows), 
then we can firstly fix the build issue. If you also have requirements to run 
pyflink on windows, then we need also add the corresponding window scripts for 
scripts such as pyflink-gateway-server.sh.

> pyflink building failure in master and 1.9.0 version
> ----------------------------------------------------
>
>                 Key: FLINK-14066
>                 URL: https://issues.apache.org/jira/browse/FLINK-14066
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 1.9.0, 1.10.0
>         Environment: windows 10 enterprise x64(mentioned as build 
> environment, not development environment.)
> powershell x64
> flink source master and 1.9.0 version
> jdk-8u202
> maven-3.2.5
>            Reporter: Xu Yang
>            Priority: Blocker
>              Labels: beginner, build
>         Attachments: setup.py
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> ATTENTION: This is a issue about building pyflink, not development.
> During we build pyflink...
> After we have built flink from flink source code, a folder named "target" is 
> generated.
> Then, following the document description, "cd flink-python; python3 setup.py 
> sdist bdist_wheel", error happens.
> Root cause: in the setup.py file, line 75, "FLINK_HOME = 
> os.path.abspath("../build-target")", the program can't found folder 
> "build-target", however, the building of flink generated a folder named 
> "target". So error happens in this way...
>  
> The right way:
> in ../flink-python/setup.py line 75, modify code as following:
> FLINK_HOME = os.path.abspath("../target")



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to