Skip to content

Latest commit

 

History

History
33 lines (25 loc) · 1.31 KB

HACKING.md

File metadata and controls

33 lines (25 loc) · 1.31 KB
Raw

compiling/testing

To test these things, you will need to setup an environment, and then run the test. This module depends on a custom variant of pyserial that contains vid/pid scanning for Linux/Windows/OSX, and therefore is best run in a virtualenv to avoid conflict with other pyserial versions

To setup the virtual envrionment test environment

. ./setup.sh

If using the virtual environment, you will need to activate it before any testing or use of the module. I have included the 'activate' in each test below, but you only need to run it once. When a virtual environemnt is active, your shell will have the prefix of (virtualenv)

#Updating the EEPROM map

  • Copy the EepromMap.hh file from MightBoardFirmware.git/firmware/src/MightyBoard/Motherboard into /makerbot_driver/EEPROM/
  • run the parse_eeprom_map_hh.py script to create a new eeprom_map.json file

Run unit tests

makerbot_driver/> . ./setup.sh
(virtuanenv)makerbot_driver/> python unit_tests.py

Running post-install tests. If you install this as an installer, or manually this will quickly verify your install is OK and likely to work properly

makerbot_driver/> . ./setup.sh
(virtuanenv)makerbot_driver/> python pi_tests.py

building an egg

To build an egg from this project: python -c "import setuptools; execfile('setup.py')" bdist_egg