search

sashafrey / topicmod

This project had been moved to https://github.com/bigartm/bigartm
Other
0 stars 0 forks source link

Fix INSTALL and PACKAGE part of CMake scripts to produce a valid installation package on Windows #91

Closed sashafrey closed 10 years ago

sashafrey commented 10 years ago

Currently BigARTM does not have an installer. On Windows such installer must contain the following parts:

  1. artm.dll and libzmq-v110-mt-4_0_5.dll
  2. microsoft visual studio redistributable (msvcp110.dll, msvcr110.dll)
  3. python_interface.py and messages_pb2.py
  4. some parts of 3rdparty/protobuf/python folder (as few files as possible, but enough to run "python setup.py build" and "python setup.py install" steps.)
  5. documentation
  6. small test collections and example scripts

All these files should be packed into installer. Ideally the installer should be able to run "python setup.py build" and "python setup.py install" steps. If this is difficult to configure we may ask user to do this manually. The protobuf/python folder must be deployed by installer, because if we ask user to download this separately then he may end up with a different version of Protocol Buffers library, incompatible with messages_pb2.py.

It is OK to require latest Python 2.7.* installed as a prerequisite. Ideally installer should check if Python is present, but this is not essential.

The following tutorial on CMake also has some information about how to setup installer. I've tried it, and it worked very well: http://www.cmake.org/cmake/help/cmake_tutorial.html

This issue is only about creating an installer for Windows. I'm not an experienced Linux user, so I have no idea how similar thing should look like on Linux. Currently I assume it is OK to ask every Linux developer to get source code of BigARTM and compile it on his machine. Please, suggest any other alternatives if you know what would be more convenient for Linux developers!

sashafrey commented 10 years ago

This is now mostly fixed (https://github.com/sashafrey/topicmod/commit/e87ff207c175f3c325a3d83fff53bc25241994ac).

Installer is still not included. I haven't tested the PACKAGE part, but the INSTALL works fairly well. Perhaps this is enough for our purposes - the deployment package will be just an archive with artm.dll.

sashafrey commented 10 years ago

Current install script is good enough for now. BigARTM will be released simply as an archive (no need to install).