(venv) D:\code\VeighNa_master>pip install vnpy_ctp
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting vnpy_ctp
Using cached https://pypi.tuna.tsinghua.edu.cn/packages/af/a2/e9f650a5953eafd290fd5cb6fe755357401e8b8839d33df1c876c2f22e4b/vnpy_ctp-6.6.9.0.tar.gz (12.4 MB)
Preparing metadata (setup.py) ... done
Requirement already satisfied: importlib_metadata in d:\code\veighna_master\venv\lib\site-packages (from vnpy_ctp) (4.12.0)
Requirement already satisfied: zipp>=0.5 in d:\code\veighna_master\venv\lib\site-packages (from importlib_metadata->vnpy_ctp) (3.17.0)
Building wheels for collected packages: vnpy_ctp
Building wheel for vnpy_ctp (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [590 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-38
creating build\lib.win-amd64-cpython-38\vnpy_ctp
copying vnpy_ctp__init.py -> build\lib.win-amd64-cpython-38\vnpy_ctp
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api
copying vnpy_ctp\api\ctp_constant.py -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
copying vnpy_ctp\api\init.py -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
creating build\lib.win-amd64-cpython-38\vnpy_ctp\gateway
copying vnpy_ctp\gateway\ctp_gateway.py -> build\lib.win-amd64-cpython-38\vnpy_ctp\gateway
copying vnpy_ctp\gateway\init__.py -> build\lib.win-amd64-cpython-38\vnpy_ctp\gateway
running egg_info
writing vnpy_ctp.egg-info\PKG-INFO
writing dependency_links to vnpy_ctp.egg-info\dependency_links.txt
writing requirements to vnpy_ctp.egg-info\requires.txt
writing top-level names to vnpy_ctp.egg-info\top_level.txt
reading manifest file 'vnpy_ctp.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.pyd' under directory 'vnpy_ctp'
adding license file 'LICENSE'
writing manifest file 'vnpy_ctp.egg-info\SOURCES.txt'
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.vnctp.vnctpmd' is absent from the packages configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.vnctp.vnctpmd' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.vnctp.vnctpmd' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.vnctp.vnctpmd' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.vnctp.vnctpmd' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.vnctp.vnctptd' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.vnctp.vnctptd' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.vnctp.vnctptd' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.vnctp.vnctptd' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.vnctp.vnctptd' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.generator' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.generator' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.generator' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.generator' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.generator' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.ctp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.ctp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.ctp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.ctp' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.ctp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.mac.ctp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.mac.ctp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.mac.ctp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.mac.ctp' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.mac.ctp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.mac.pybind11' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.mac.pybind11' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.mac.pybind11' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.mac.pybind11' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.mac.pybind11' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.mac.pybind11.detail' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.mac.pybind11.detail' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.mac.pybind11.detail' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.mac.pybind11.detail' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.mac.pybind11.detail' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.pybind11' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.pybind11' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.pybind11' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.pybind11' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.pybind11' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.include.pybind11.detail' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.include.pybind11.detail' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.include.pybind11.detail' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.include.pybind11.detail' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.include.pybind11.detail' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.libs' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.libs' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.libs' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.libs' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.libs' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
d:\code\veighna_master\venv\lib\site-packages\setuptools\command\build_py.py:204: _Warning: Package 'vnpy_ctp.api.vnctp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_ctp.api.vnctp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'vnpy_ctp.api.vnctp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'vnpy_ctp.api.vnctp' to be distributed and are
already explicitly excluding 'vnpy_ctp.api.vnctp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctpmd\vnctpmd.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\vnctp\vnctptd\vnctptd.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\libthostmduserapi_se.so -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
copying vnpy_ctp\api\libthosttraderapi_se.so -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
copying vnpy_ctp\api\thostmduserapi_se.dll -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
copying vnpy_ctp\api\thosttraderapi_se.dll -> build\lib.win-amd64-cpython-38\vnpy_ctp\api
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_header_define.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_header_function.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_header_on.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_header_process.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_function.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_module.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_on.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_process.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_switch.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_md_source_task.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_header_define.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_header_function.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_header_on.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_header_process.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_function.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_module.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_on.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_process.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_switch.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
copying vnpy_ctp\api\generator\ctp_td_source_task.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\generator
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\ctp
copying vnpy_ctp\api\include\ctp\ThostFtdcMdApi.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\ctp
copying vnpy_ctp\api\include\ctp\ThostFtdcTraderApi.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\ctp
copying vnpy_ctp\api\include\ctp\ThostFtdcUserApiDataType.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\ctp
copying vnpy_ctp\api\include\ctp\ThostFtdcUserApiStruct.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\ctp
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\ctp
copying vnpy_ctp\api\include\mac\ctp\ThostFtdcMdApi.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\ctp
copying vnpy_ctp\api\include\mac\ctp\ThostFtdcTraderApi.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\ctp
copying vnpy_ctp\api\include\mac\ctp\ThostFtdcUserApiDataType.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\ctp
copying vnpy_ctp\api\include\mac\ctp\ThostFtdcUserApiStruct.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\ctp
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\attr.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\buffer_info.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\cast.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\chrono.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\common.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\complex.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\eigen.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\embed.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\eval.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\functional.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\iostream.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\numpy.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\operators.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\options.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\pybind11.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\pytypes.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\stl.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
copying vnpy_ctp\api\include\mac\pybind11\stl_bind.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\class.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\common.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\descr.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\init.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\internals.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
copying vnpy_ctp\api\include\mac\pybind11\detail\typeid.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\mac\pybind11\detail
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\attr.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\buffer_info.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\cast.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\chrono.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\common.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\complex.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\eigen.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\embed.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\eval.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\functional.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\iostream.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\numpy.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\operators.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\options.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\pybind11.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\pytypes.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\stl.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
copying vnpy_ctp\api\include\pybind11\stl_bind.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\class.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\common.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\descr.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\init.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\internals.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
copying vnpy_ctp\api\include\pybind11\detail\typeid.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\include\pybind11\detail
creating build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\libcomunicationkey.a -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\libcrypto.a -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\libssl.a -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\libthostmduserapi_se.a -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\libthosttraderapi_se.a -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\thostmduserapi_se.lib -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\libs\thosttraderapi_se.lib -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\libs
copying vnpy_ctp\api\vnctp\vnctp.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp
copying vnpy_ctp\api\vnctp\vnctpmd\dllmain.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctpmd\stdafx.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctpmd\stdafx.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctpmd\targetver.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctpmd\vnctpmd.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctpmd
copying vnpy_ctp\api\vnctp\vnctptd\dllmain.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\vnctp\vnctptd\stdafx.cpp -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\vnctp\vnctptd\stdafx.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\vnctp\vnctptd\targetver.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
copying vnpy_ctp\api\vnctp\vnctptd\vnctptd.h -> build\lib.win-amd64-cpython-38\vnpy_ctp\api\vnctp\vnctptd
running build_ext
building 'vnpy_ctp.api.vnctptd' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for vnpy_ctp
Running setup.py clean for vnpy_ctp
Failed to build vnpy_ctp
ERROR: Could not build wheels for vnpy_ctp, which is required to install pyproject.toml-based projects
