Developers: Difference between revisions
Jump to navigation
Jump to search
Carandraug (talk | contribs) (replacing coding standards page (now removed) with the existing pages) |
No edit summary |
||
| Line 35: | Line 35: | ||
* [[Java interface]] | * [[Java interface]] | ||
* [[JIT]] | * [[JIT]] | ||
==Code sprints== | ==Code sprints== | ||
| Line 45: | Line 42: | ||
==Release procedures== | ==Release procedures== | ||
* [[Release Checklist]] | * [[Release Checklist]] | ||
==Other== | |||
* [[Hacking]] | |||
* [[Project Infrastructure]] | |||
Revision as of 15:08, 29 March 2017
This page contains links to pages of interest to developers. Some links appear in multiple sections.
Getting started
- Developer FAQ
- Contributing to the development of packages/modules
- Octave's file types
- Easy projects
- C++ style guide
- Octave style guide
Project suggestions
- Easy projects
- GSoC Project Ideas
- Projects -- Many things that would be nice to have done. Not classified into things done or not done in Matlab. (Is that a project in itself?)
Tools
- Mercurial -- version control scheme.
- MXE -- cross-compiling to Windows or OSX.
- Doxygen -- "Literate programming" documentation generator.
- gdb -- debugger. Useful to obtain stack traces.
- valgrind -- memory leak detector, profiler etc.
- ccache -- cache compilation across builds.
Bugs and testing
- Status of bugs
- Bug Fix List - 4.0 Release
- Debugging Octave, particularly using .oct files and gdb
- Add BIST tests for octave functions written in C++
- BIST for m-files