As I've mentioned before, I'm currently working on making Freeseer
installable on Windows via an install script. The script should download the dependencies, install them, configure some environment variables and download and install freeseer itself. Thus, the user should do as few manual work as possible.
Since the script manipulates environment variables, it should be run with administrator privileges. By default, a batch script executed with administrator privileges is run on directory C:\Windows\System32. We'll use some relative paths on the script, so it's important to keep our current directory. To do that, the lines below should be put on the beginning of the script:
@cd /d "%~dp0"
After that, it's time to download the dependencies. Windows doesn't have nice native ways to download files via command-line, so the approach used here is to use a compiled version of wget
, which can be downloaded here
. It should be in the same folder of the script. The folder should look like as shown on the Figure 1.
|Figure 1 - Script folder.|
The dependencies can be on .exe or .msi extensions. Each one should be treated differently. Dependencies with .exe extensions are called directly, while the ones with .msi extensions are called using msiexec command. There's a wizard for each dependency. The user should just accept any license agreements that might occur and choose the default options.
|Figure 2 - Downloading dependencies|
|Figure 3 - Installing dependencies|
Then, it's necessary to change the environment variable Path
to include Python and Gstreamer. To do that, I used a VBScript
that appends Python and Gstreamer locations to Path
. There are some dependencies (feedparser, pygtk and yapsi) downloaded via easy_install.
Gstreamer uses the bindings for Python 2.6 by default. The next step is to put the correct files on the correct folders so Gstreamer can use Python 2.7. The script moves Python 2.7 bindings to Gstreamer's main folder (the one that we set in the environment variables before, remember?) and copies Gstreamer's site-packages folder to Python's site-packages folder.
The final step is, of course, install Freeseer itself. I hosted Freeseer installer here
, because I was facing authentication problems while trying to wget it from GitHub's page
|Figure 4 - Freeseer installation|
Finally, we can run freeseer:
|Figure 5 - Freeseer running|