equal
deleted
inserted
replaced
6 ================================================ |
6 ================================================ |
7 |
7 |
8 Setting up a Windows development environment is not too complicated |
8 Setting up a Windows development environment is not too complicated |
9 but it requires a series of small steps. |
9 but it requires a series of small steps. |
10 |
10 |
11 We proposed an example of a typical |cubicweb| installation on Windows |
11 We propose an example of a typical |cubicweb| installation on Windows |
12 from sources. We assume everything goes into ``C:\\`` and for any |
12 from sources. We assume everything goes into ``C:\\`` and for any |
13 package, without version specification, "the latest is |
13 package, without version specification, "the latest is |
14 the greatest". |
14 the greatest". |
15 |
15 |
16 Take into the mind that adjusting the installation drive should be |
16 Mind that adjusting the installation drive should be straightforward. |
17 straightforward. |
|
18 |
17 |
19 |
18 |
20 |
19 |
21 Install the required elements |
20 Install the required elements |
22 ----------------------------- |
21 ----------------------------- |
102 (`Home page <http://www.vectrace.com/mercurialeclipse/>`_). |
101 (`Home page <http://www.vectrace.com/mercurialeclipse/>`_). |
103 |
102 |
104 Getting the sources |
103 Getting the sources |
105 ------------------- |
104 ------------------- |
106 |
105 |
107 There are tow ways to get the sources of |cubicweb| and its |
106 There are two ways to get the sources of |cubicweb| and its |
108 :ref:`cubes <AvailableCubes>`: |
107 :ref:`cubes <AvailableCubes>`: |
109 |
108 |
110 * download the latest release (:ref:`SourceInstallation`) |
109 * download the latest release (:ref:`SourceInstallation`) |
111 * get the development version using Mercurial |
110 * get the development version using Mercurial |
112 (:ref:`MercurialInstallation`) |
111 (:ref:`MercurialInstallation`) |
151 win32svc install |
150 win32svc install |
152 |
151 |
153 Then start the service with:: |
152 Then start the service with:: |
154 |
153 |
155 net start cubicweb-my_instance |
154 net start cubicweb-my_instance |
|
155 |
|
156 In case this does not work, you should be able to see error reports in |
|
157 the application log, using the windows event log viewer. |