In which we make OpenCV play nice with Anaconda under Windows and roll libjpeg-turbo in along the way.
You may have noticed, if you have been reading my blog, that I like to prototype in Python. I find Python to be almost as fun as Lisp when it comes to building up a solution without knowing exactly what the solution is going to look like. The reason I typically start in Python is the wealth of libraries; however, managing a Python install can become a real pain. Thanks to the people over at Continuum Analytics, you can be spared most of it.
Continuum Analytics produces a fantastic distribution known as Anaconda (or Miniconda depending on the route you choose). I won't go into all the reasons I think you should give it a try, but if you program in Python, you should check them out. The only shortcoming I have come across is the Windows build does not include OpenCV, but we will remedy that today. Along the way, I will also show you how to build OpenCV against libjpeg-turbo for better jpeg performance.
Things you will need:
- CMake: Used to generate makefiles/solutions to build OpenCV.
- Visual Studio: This article is geared towards VS, but you should be able to follow roughly the same steps for other compilers.
- OpenCV: The reason for this excursion. I downloaded the self extracting Windows package. You can just grab the source if you like.
- libjpeg-turbo: An optimized crossplatform library for working with jpegs.
- Anaconda (or Miniconda): My (and soon to be yours) favorite Python distribution.
Make sure your versions match, i.e. if you install 64 bit Anaconda, install the 64 bit version of libjpeg-turbo and build OpenCV for 64 bits.
If you use Miniconda to make your default Python installation Python 3 (as I have done) you will need to make a Python 2 environment. Please see here.
To the Bat Cave!
- Run the self extracting OpenCV archive if necessary, and extract OpenCV to a place you will remember, e.g. C:\OpenCV
- Run the installer for libjpeg-turbo
- If your default Python install is Python 3
- Right click on the cmake/bin directory while holding down Shift
- Click "Open command window here"
- Activate your Python 2 environment with
- Launch cmake-gui (from the command prompt in step 3 if necessary)
- Set "Where is the source code:" to the path in step 1
- Set "Where to build the binaries:" to where you normally build libs, e.g. C:\Libs\OpenCV
- Click Configure and wait for it to complete
- Check the Advanced checkbox
- Locate the option BUILD_JPEG and uncheck it
- Click the Add Entry button and add
- Name: JPEG_LIBRARY
- Type: FILEPATH
- Value: path to the static libjpeg-turbo64 e.g. C:/libjpeg-turbo64/lib/jpeg-static.lib
- Click the Add Entry button and add
- Name: JPEG_INCLUDE_DIR
- Type: PATH
- Value: path to the libjpeg-turbo64 include e.g. C:/libjpeg-turbo64/include
- If you see a message in the Configure output that says PYTHON_INCLUDE_DIR and/or PYTHON_LIBRARY are not found, you will need to set them by hand by clicking in the Value column and entering the path. On my system (Windows 8.1 Pro) these are C:/Users/lemoneer/Miniconda3/envs/python-2/include and C:/Users/lemoneer/Miniconda3/envs/python-2/libs/python27.lib respectively.
- Click Configure again and wait for it to complete
- Verify all is well in the output of Configure
- Click Generate
- Open the generated solution file in your build directory from step 6
- Change the build to Release
- Build the Solution
- Expand CMakeTargets in the Solution Explorer
- Right click on INSTALL
- Click Build
- Once the build is complete, update your path to include the OpenCV dlls
- You may Clean the Build at the solution level to remove intermediate files you do not need (this wont affect the install).
It is worth nothing that there are other build options worth considering like building the examples. Enable/disable to your heart's content then click Configure followed by Generate and Build.
If all goes well, you will have OpenCV dlls you can use from C/C++ as well as from your Python 2 environment.
In which we assemble a portable, Emacs based LISP development environment under Windows. This being good for the soul.
For Carlos, happy birthday. You will come to understand... they all do.
For Josh, you were right about Lisp.
Before we begin, let me say if you are new to Lisp, you should check out Quicklisp. Quicklisp provides a convenient way to setup and maintain a Lisp development environment with a large set of libraries. However, if you would like a portable Lisp development environment and/or would like to have more control over (or a better understanding of) your Emacs based setup, please read on.
What you will need:
- The latest version of Emacs for Windows. Download the zip.
- The latest CVS snapshot of SLIME. Download the tar archive.
- One or more of the following Lisp implementations:
- CCL: Checkout the latest release version from SVN.
- ECL: You will have to compile from source.
- Par Edit: helps **keep parentheses balanced**
And we are off!
- Extract Emacs to a location of your choice, e.g. emacs-24.3 (tip include the version in the directory names so you can tell which version you are running.)
- Create a directory named 'home' in the root of your emacs directory, e.g. emacs-24.3/home
- Create a directory named 'bin' in the root of 'home', e.g. emacs-24.3/home/bin
- Deploy Lisp implementation(s)
Create the file site-start.el in site-lisp in the root of your Emacs directory, e.g. emacs-24.3/, and insert the code below. This allows us to set the ‘HOME’ environment variable when we launch Emacs.
- Extract to a directory in bin, e.g. emacs-24.3/home/bin/clisp-2.49
- Compile from source and install to a directory in bin, e.g. emacs-24.3/home/bin/ecl-13.5.1
- Checkout from SVN to a directory in bin, e.g. emacs-24.3/home/bin/ccl
- Tip: keep CCL up to date between version releases with SVN's update command.
- Modify ccl/level-1/linux-files.lisp line 939
#+windows-target to set HOME from the 'HOME' environment variable. This allows us to control where CCL writes files reducing debris and making it portable.
;; Matthew Witherwax (lemoneer) 01MAY2013
;; Modified the Windows target to use the value of the HOME environment
;; variable if it exists; otherwise, it falls back to the OS user database.
;; This allows CCL to be run portably under Windows without leaving debris
(dolist (k '(#||"HOME"||# "USERPROFILE"))
(with-native-utf-16-cstrs ((key k))
(let* ((p (#__wgetenv key)))
(unless (%null-ptr-p p)
(return (get-foreign-namestring p)))))))
; remove etc from the path
(substring data-directory 0
(- (length data-directory) 4)))
; create appened home/
(defvar home-dir (concat %~dp0 "home/"))
(setenv "HOME" home-dir)
Extract the latest slime csv snapshot to site-lisp, e.g. emacs-24.3/site-lisp/slime-2013-12-12
Optional: Copy paredit to /lisp in the root of your Emacs directory, e.g. emacs-24.3/lisp
Launch Emacs by double clicking runemacs.exe in the bin directory of the Emacs directory, e.g. emacs-24.3/bin, and type
C-x C-f ~/.emacs to open the Emacs config file. Insert the following:
Create a batch file called runslime.bat and insert the following command. This will allow us to launch Emacs with slime and your default Lisp running.
;;; Add slime
(add-to-list 'load-path "~/site-lisp/slime-2013-12-12") ;or wherever you put it
;;; CCL Note that if you save a heap image, the character
;;; encoding specified on the command line will be preserved,
;;; and you won't have to specify the -K utf-8 any more.
;; SLIME and CLISP will complain about a missing temp directory without this
(setq temporary-file-directory (expand-file-name "~/temp"))
;; Path to clisp full so we can build the call
(setq path-clisp (expand-file-name "~/bin/clisp-2.49/full/"))
;;; Configure available Lisp
;;; Leave out the one(s) you did not install
(ccl (,(expand-file-name "~/bin/ccl/wx86cl64.exe") "-K utf-8"))
(clisp (,(replace-regexp-in-string "@" path-clisp "@lisp.exe")
,(replace-regexp-in-string "@" path-clisp "-B@")
,(replace-regexp-in-string "@" path-clisp "-M@lispinit.mem")
(ecl (,(expand-file-name "~/bin/ecl-13.5.1/ecl.exe")))))
;;; setup slime
(setq slime-net-coding-system 'utf-8-unix)
;;; setup paredit if you installed it
(autoload 'paredit-mode "paredit"
"Minor mode for pseudo-structurally editing Lisp code." t)
(add-hook 'emacs-lisp-mode-hook (lambda () (paredit-mode +1)))
(add-hook 'lisp-mode-hook (lambda () (paredit-mode +1)))
(add-hook 'lisp-interaction-mode-hook (lambda () (paredit-mode +1)))
(add-hook 'scheme-mode-hook (lambda () (paredit-mode +1)))
;;; This is disabled to stop paredit from running in the REPL
;;; Feel free to uncomment this to turn it back on
;;;; (add-hook 'slime-repl-mode-hook (lambda () (paredit-mode +1)))
;;;; ;; Stop SLIME's REPL from grabbing DEL,
;;;; ;; which is annoying when backspacing over a '('
;;;; (defun override-slime-repl-bindings-with-paredit ()
;;;; (define-key slime-repl-mode-map
;;;; (read-kbd-macro paredit-backward-delete-key) nil))
;;;; (add-hook 'slime-repl-mode-hook 'override-slime-repl-bindings-with-paredit)
;;; bonus split the screen in to two side by side windows
(defun 2-windows-vertical-to-horizontal ()
(= (length (window-list)) 2) ; only split if there are 2 windows
(window-combined-p)) ; and they are vertical
(add-hook 'emacs-startup-hook '2-windows-vertical-to-horizontal)
(add-to-list 'default-frame-alist '(left . 0))
(add-to-list 'default-frame-alist '(top . 0))
If you followed all the steps, when you run runslime.bat, you should see something like this
Take this REPL, brother, and may it serve you well.