Setup of Development Environment for Windows: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
Line 46: Line 46:
*** get the latest Windows version from http://dev.mysql.com/downloads/mysql/. It is called MySQL Community Server. The MSI essential package works fine for me.
*** get the latest Windows version from http://dev.mysql.com/downloads/mysql/. It is called MySQL Community Server. The MSI essential package works fine for me.


== Optional ==
= Optional Software =
The following pieces of software are only required when you want to build releases of OpenPetra:
* For the editing YAML files we use Notepad++, which has syntax highlighting.
* Poedit (for translation, generating the .mo file from the .po file): http://www.poedit.net/download.php
** [http://notepad-plus-plus.org/download Download Notepad++]
* Inno Setup 5 for building setup files: http://www.jrsoftware.org/isdl.php
** Once the software is installed, it needs to be set up once to accept our file extension, '.yaml', in addition to the one is built in, '.yml' for the syntax highlighting to work:
*** Menu 'Settings' -> 'Style Configurator'. Select 'YAML' in the 'Language' list and enter 'yaml' in the 'User ext.' field. Choose 'Save & Close'. (You might need to close and re-open any .yaml file that you already have open to get the syntax highlighting working.)
* The following pieces of software are only required when you want to build releases of OpenPetra:
** Poedit (for translation, generating the .mo file from the .po file): http://www.poedit.net/download.php
** Inno Setup 5 for building setup files: http://www.jrsoftware.org/isdl.php


= Get the source code =
= Get the source code =

Revision as of 09:47, 5 July 2010

Required software

Microsoft .Net

  • Microsoft .Net 3.5 Redistributable and the SDK (we only use .Net 2.0 for OpenPetra, but SharpDevelop requires .Net 3.5)

SharpDevelop 3.x

TortoiseGit

This works fine on Windows, although it is still work in progress...

It requires "Git on Windows" http://code.google.com/p/msysgit/; be careful: use the official git installer from that site, eg. Git-1.6.3.2-preview20090608.exe, not the fullinstaller or other packages.

We recommend to use plink.exe from PuTTY, not OpenSSH. You have that choice in the TortoiseGit installer.

You also might want to have a look at Git Extensions which is also a fully functional git GUI for Windows.

See also some Notes about Git

NAnt

  • unzip the files to eg. c:\program files\nant
  • create file c:\windows\nant.bat with content:
@echo off
"C:\Program Files\NAnt\bin\NAnt.exe" %* -t:net-2.0

See also some Notes about NAnt

Database systems

Optional Software

  • For the editing YAML files we use Notepad++, which has syntax highlighting.
    • Download Notepad++
    • Once the software is installed, it needs to be set up once to accept our file extension, '.yaml', in addition to the one is built in, '.yml' for the syntax highlighting to work:
      • Menu 'Settings' -> 'Style Configurator'. Select 'YAML' in the 'Language' list and enter 'yaml' in the 'User ext.' field. Choose 'Save & Close'. (You might need to close and re-open any .yaml file that you already have open to get the syntax highlighting working.)
  • The following pieces of software are only required when you want to build releases of OpenPetra:

Get the source code

The source code is managed with Git.

Please understand that we will provide write permissions only to the core members of the development team, just to keep the project on one track. We very much need your contributions though, and we will aim to quickly deal with submitted patches and code via the forum. This still has to be worked out how this works best to submit code that way.

You can get the source code in several ways:

for anonymous access, you can use this URL to clone the repository with TortoiseGit: 

git://openpetraorg.git.sourceforge.net/gitroot/openpetraorg/openpetraorg

for developer access (with write permissions), use this URL to clone the repository with TortoiseGit: 

ssh://USERNAME@openpetraorg.git.sourceforge.net/gitroot/openpetraorg/openpetraorg

For development, I recommend you create a local branch, and switch to it. Then you pull updates from the server ("master") into your local branch, and push your updates up to the server in the master branch. Otherwise you get all sorts of problems with pushing and pulling, so don't commit to master at all. see also Notes about Git

Configuration of Development Environment

The recommended way of installing OpenPetra.org for development is to somewhere map a network drive, using the DOS command subst

For example: 

mkdir c:\development
subst u: c:\development
download the git repository into u:\openpetraorg (it contains the .git directory, and the OpenPetra.build: U:\openpetraorg\OpenPetra.build, etc)
URL of the git repository:
   anonymous access: git://openpetraorg.git.sourceforge.net/gitroot/openpetraorg/openpetraorg
   developer access: ssh://USERNAME@openpetraorg.git.sourceforge.net/gitroot/openpetraorg/openpetraorg
     make sure that you set your username and email address in your git client
  • you need to make a copy of the file OpenPetra.build-sample-windows.config and call it OpenPetra.build.config
copy OpenPetra.build-sample-windows.config OpenPetra.build.config

Please check your OpenPetra.build.config file and make sure the paths are all adjusted to your system and the version numbers in the paths are correct.

NAnt script

There is a central NAnt script that is able to generate a lot of code and is able to do all automated tasks in the OpenPetra project.

Please see OpenPetra NAnt script for details

Retrieved from ‘https://wiki.openpetra.org/index.php?title=Setup_of_Development_Environment_for_Windows&oldid=600’