3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Клиппер
879 Commits 1 Branch 0 Tags 27 MiB
C 96.7%
Python 2.8%
C++ 0.3%
Go to file
Kevin O'Connor 28d70eaf0c test: Update travis build to include a basic klippy host test 
Move the travis installation steps from the travis-build.sh script to
a new script (scripts/travis-install.sh).  Move the travis-build.sh
script to the scripts/ directory as well.

The data dictionaries built in the compile tests are useful during
host software testing, so run all the compile tests sequentially in a
single VM and save the data dictionaries after each build.  Also,
build all the config files found in the test/configs/ directory.

Create the python virtualenv environment during the install phase and
invoke the klippy.py host software in the build phase to perform a
basic host software sanity check.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
 		2018-02-26 14:58:49 -05:00
config config: Use .0025 as the default z step_distance in sample configs 2018-02-25 16:00:55 -05:00
docs docs: Add tips for porting to new kinematics to Code_Overview.md 2018-02-17 13:48:53 -05:00
klippy avr: Add at90usb646 support 2018-02-25 10:23:00 -05:00
lib sched: Introduce sched_wake_tasks() function to wake up tasks 2017-08-08 00:27:28 -04:00
scripts test: Update travis build to include a basic klippy host test 2018-02-26 14:58:49 -05:00
src avr: Add at90usb646 support 2018-02-25 10:23:00 -05:00
test/configs test: Update travis build to include a basic klippy host test 2018-02-26 14:58:49 -05:00
.gitignore Initial commit of source code. 2016-05-25 11:37:40 -04:00
.travis.yml test: Update travis build to include a basic klippy host test 2018-02-26 14:58:49 -05:00
COPYING Initial commit of source code. 2016-05-25 11:37:40 -04:00
Makefile build: Link objects ahead of libraries to avoid failures on some platforms 2018-02-25 10:39:06 -05:00
README.md docs: Add a features document 2016-12-20 22:31:46 -05:00

README.md

Welcome to the Klipper project!

This project implements a 3d-printer firmware. There are two parts to this firmware - code that runs on a micro-controller and code that runs on a host machine. The host software does the work to build a schedule of events, while the micro-controller software does the work to execute the provided schedule at the specified times.

See the features document to find out why you should use Klipper. To begin using Klipper start by installing it.

There is also developer documentation available.

License

Klipper is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Klipper is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with Klipper. If not, see http://www.gnu.org/licenses/.