PyTango and installation for widows

# 6 years ago
Carlos	If anyone uploaded binaries from link above to PyPi… AFAIK, PyPi no longer hosts windows binaries (only sources and wheels)

# 6 years ago
Leonard	Dear Diego, I am sorry I did not manage to reply any earlier, I'm glad you found a solution now. The files you linked actually should make the building step unnecessary for most people/ setups, so trying to make the old Visual Studio projects work seems to be a bad idea to me (as you say they contain lots of broken references, missing file links etc. which had to be fixed). The only things I could add to Jimmys method there I think are some explanations on how I managed to get Boost working and all the paths right, but also this should not be necessary anymore given the above links and the continuous integration in the future (hopefully). After spending several more hours on figuring out what is the current status (and learning a lot about github and appveyor), here are my thoughts: The Visual Studio projects in github.com/tango-controls/pytango seem obsolete and in my opinion might even be deleted. The cmake files in combination with the Appveyor are the current way of compiling things, however I have not used this before so no idea how to do that yourself. Studying the appveyor.yml config file and the job outputs on e.g. https://ci.appveyor.com/project/NexeyaSGara/pytango gives great insight on each step and what libs etc. are required. So in case you do want to compile your own version, you can find all the download links for the required binaries (boost, omniorb etc) in these scripts. However, most of them are hardlinks to Appveyor artifacts from other auto-builds, so they also vanish after 6 months :( In summary, I totally agree that this is very confusing and time consuming, especially for people new to Tango, I will post an issue for PyTango suggesting to make the available binaries more public and to keep major releases longer than that. (Actually, as long as there is a newer version for the same architecture that would be fine, but currently the Appveyor links above do not contain any downloadable artifact at all since last successful build is older than 6 months.) Maybe someone from the maintainer side can comment on this? EDIT: For reference: https://github.com/tango-controls/pytango/issues/218 Edited 6 years ago

# 6 years ago

Leonard

Dear Diego,

I am sorry I did not manage to reply any earlier, I'm glad you found a solution now.
The files you linked actually should make the building step unnecessary for most people/ setups, so trying to make the old Visual Studio projects work seems to be a bad idea to me (as you say they contain lots of broken references, missing file links etc. which had to be fixed).

The only things I could add to Jimmys method there I think are some explanations on how I managed to get Boost working and all the paths right, but also this should not be necessary anymore given the above links and the continuous integration in the future (hopefully).

After spending several more hours on figuring out what is the current status (and learning a lot about github and appveyor), here are my thoughts:
The Visual Studio projects in github.com/tango-controls/pytango seem obsolete and in my opinion might even be deleted.
The cmake files in combination with the Appveyor are the current way of compiling things, however I have not used this before so no idea how to do that yourself. Studying the appveyor.yml config file and the job outputs on e.g. https://ci.appveyor.com/project/NexeyaSGara/pytango gives great insight on each step and what libs etc. are required.
So in case you do want to compile your own version, you can find all the download links for the required binaries (boost, omniorb etc) in these scripts. However, most of them are hardlinks to Appveyor artifacts from other auto-builds, so they also vanish after 6 months :(

In summary, I totally agree that this is very confusing and time consuming, especially for people new to Tango, I will post an issue for PyTango suggesting to make the available binaries more public and to keep major releases longer than that. (Actually, as long as there is a newer version for the same architecture that would be fine, but currently the Appveyor links above do not contain any downloadable artifact at all since last successful build is older than 6 months.)

Maybe someone from the maintainer side can comment on this?

EDIT: For reference:
https://github.com/tango-controls/pytango/issues/218

Edited 6 years ago

# 6 years ago
Jimmy	Hi, I agree to Leonard, currently we should use cmake to build pytango, thanks to NexeyaSGara's work (CMakeLists.txt from https://github.com/NexeyaSGara/pytango/tree/NexeyaSGara-windows-ci), i had used this CMakeLists.txt (needed some edit based on your environment ) to make PyTango-9.2.4 with cppTango-9.3.1 on Windows10 + VS2013 + Python37, it could successfully make (generated pytango-9.2.4.win-amd64-py3.7.msi), but i have no time to install and test this msi file currently. If you want to use old Visual Studio projects to make pytango-9.2.4, you can edit win\PyTango_VS14\PyTango.vcxproj and win\PyTango_VS14\PyTango.props as i said in http://www.tango-controls.org/community/forum/c/development/python/pytango-921-installer-for-python3-on-windows/?page=1 firstly, then you must continue to edit win\PyTango_VS14\PyTango.vcxproj file to add three source file in second <ItemGroup>…</ItemGroup> section: `<ClCompile Include="..\..\ext\devintr_change_event_data.cpp" /> <ClCompile Include="..\..\ext\pipe_event_data.cpp" /> <ClCompile Include="..\..\ext\server\fwdAttr.cpp" />` Then in vs2013 IDE open PyTango.sln, select "py35_bopyshared_tangoshared_release x64" target to build and install. I remember i builded PyTango-9.2.4 with tango-9.2.2 on Windows10 + VS2013 + Python27 succefully by this method, but this dynamic link method can't build with cppTango-9.3.1. maybe Edited 6 years ago

# 6 years ago

Jimmy

Hi,

I agree to Leonard, currently we should use cmake to build pytango, thanks to NexeyaSGara's work (CMakeLists.txt from https://github.com/NexeyaSGara/pytango/tree/NexeyaSGara-windows-ci), i had used this CMakeLists.txt (needed some edit based on your environment ) to make PyTango-9.2.4 with cppTango-9.3.1 on Windows10 + VS2013 + Python37, it could successfully make (generated pytango-9.2.4.win-amd64-py3.7.msi), but i have no time to install and test this msi file currently.

If you want to use old Visual Studio projects to make pytango-9.2.4, you can edit win\PyTango_VS14\PyTango.vcxproj and win\PyTango_VS14\PyTango.props as i said in http://www.tango-controls.org/community/forum/c/development/python/pytango-921-installer-for-python3-on-windows/?page=1 firstly, then you must continue to edit win\PyTango_VS14\PyTango.vcxproj file to add three source file in second <ItemGroup>…</ItemGroup> section:

    <ClCompile Include="..\..\ext\devintr_change_event_data.cpp" />
    <ClCompile Include="..\..\ext\pipe_event_data.cpp" />
    <ClCompile Include="..\..\ext\server\fwdAttr.cpp" />

Then in vs2013 IDE open PyTango.sln, select "py35_bopyshared_tangoshared_release x64" target to build and install.
I remember i builded PyTango-9.2.4 with tango-9.2.2 on Windows10 + VS2013 + Python27 succefully by this method, but this dynamic link method can't build with cppTango-9.3.1. maybe smile

Edited 6 years ago

# 6 years ago
Carlos	Regarding the short-lived (6months) artifacts in appveyor, one (cheap) possibility is having appveyor automatically deploy them as github releases.