Skip to content

Development: Getting started

Peter Uithoven edited this page Apr 11, 2015 · 21 revisions

This is a guide for people who want to start contributing to VisiCut as a developer.

Setting up the environment

Necessary software

If you want to build the installer, Debian/Ubuntu is recommended because you can generate the packages for all other operating systems from there.

If you want to change the GUI, some parts are created with an old UI-Editor-Version of NetBeans, which means that you have to use NetBeans <= 7.0.1 (http://netbeans.org/downloads/7.0.1/index.html) to change those. However we are continuing to change those to newer Version, so first try to open it with a more recent version. If you just change code, which is no UI-Form, you do not need the old version.

Initial setup

  • Open up a terminal (git bash on windows)
  • cd to a folder, where you want to have the VisiCut sources e.g.:
cd Desktop
  • clone the VisiCut repository including the LibLaserCut repository
git clone --recursive https://github.com/t-oster/VisiCut.git
  • If you get an error message that --recursive is unsupported (old version of Mac OSX e.g.), use:
git clone https://github.com/t-oster/VisiCut.git
cd VisiCut
git submodule init
git submodule update
  • Open up NetBeans
  • Open the LibLaserCut project, then the VisiCut project:
  • File->Open Project
  • select the path where you cloned the VisiCut repository, expand it and select the subfolder "lib/LibLaserCut"
  • Hit 'Clean and Build'
  • File->Open Project
  • now select the VisiCut path

Congratulations. You should now have the latest Visicut version.

If you have this setup and want to start developing, always update to the latest develop-version first:

Updating to the latest version

If you want to develop and publish a fix or a feature, read submit a fix or feature

Distribution

To create distribute files for the different platforms run distribute.sh

cd distribute; ./distribute.sh

(answer "n" for all packages you don't need like windows etc.)

To view compile errors you need to run make manually, in the main folder.