Setting up a Windows development environment is not too complicated but it requires a series of small steps.
We propose an example of a typical CubicWeb installation on Windows from sources. We assume everything goes into C:\\ and for any package, without version specification, “the latest is the greatest”.
Mind that adjusting the installation drive should be straightforward.
CubicWeb requires some base elements that must be installed to run correctly. So, first of all, you must install them :
We recommend you to install the following elements. They are not mandatory but they activate very interesting features in CubicWeb:
Other elements will activate more features once installed. Take a look at Installation dependencies.
Some additional tools could be useful to develop cubes with the framework.
There are two ways to get the sources of CubicWeb and its cubes:
You will need some convenience environment variables once all is set up. These variables are settable through the GUI by getting at the System properties window (by righ-clicking on My Computer -> properties).
In the advanced tab, there is an Environment variables button. Click on it. That opens a small window allowing edition of user-related and system-wide variables.
We will consider only user variables. First, the PATH variable. Assuming you are logged as user Jane, add the following paths, separated by semi-colons:
C:\Documents and Settings\Jane\My Documents\Python\cubicweb\cubicweb\bin C:\Program Files\Graphviz2.24\bin
The PYTHONPATH variable should also contain:
C:\Documents and Settings\Jane\My Documents\Python\cubicweb\
From now, on a fresh cmd shell, you should be able to type:
... and get a meaningful output.
This currently assumes that the instances configurations is located at C:\\etc\\cubicweb.d. For a cube ‘my_instance’, you will find C:\\etc\\cubicweb.d\\my_instance\\win32svc.py.
Now, register your instance as a windows service with:
Then start the service with:
net start cubicweb-my_instance
In case this does not work, you should be able to see error reports in the application log, using the windows event log viewer.