Go to file

daid303 57b585b851 Fix another UTF-8 filename encoding bug. Add error output to the slice log so we see exceptions.		2012-12-04 08:27:04 +01:00
Cura	Fix another UTF-8 filename encoding bug. Add error output to the slice log so we see exceptions.	2012-12-04 08:27:04 +01:00
scripts	allow user to cancel automatic installation of dependencies during install	2012-11-19 12:37:46 -05:00
.gitignore	Added G4 to GCode reader. Fixes #132	2012-06-19 21:57:16 +02:00
.gitmodules	Show a warning if computer is not connected to AC power.	2012-11-20 15:32:34 +07:00
README.md	Update README to point people better to the right location	2012-04-06 16:20:22 +02:00
changelog	Updated changelog.	2012-11-12 10:04:11 +01:00
package.sh	Increased version number to 12.11	2012-11-12 09:59:59 +01:00

README.md

Cura

If you are reading this, then you are looking at the development version of Cura. If you just want to use Cura look at the following location: https://github.com/daid/Cura/wiki

Development

Cura is developed in Python. Getting Cura up and running for development is not very difficult. If you copy the python and pypy from a release into your Cura development checkout then you can use Cura right away, just like you would with a release. For development with git, check the help on github. Pull requests is the fastest way to get changes into Cura.

Packaging

Cura development comes with a script "package.sh", this script has been designed to run under unix like OSes (Linux, MacOS). Running it from sygwin is not a priority. The "package.sh" script generates a final release package. You should not need it during development, unless you are changing the release process. If you want to distribute your own version of Cura, then the package.sh script will allow you to do that.