Developers: Difference between revisions
Jump to navigation
Jump to search
(→Getting started: link to guidelines) |
|||
| Line 3: | Line 3: | ||
==Getting started== | ==Getting started== | ||
* [[Developer FAQ]] | * [[Developer FAQ]] | ||
* [[Contribution guidelines|Contributing to Octave]] | |||
* [[Contributing to the development of packages/modules]] | * [[Contributing to the development of packages/modules]] | ||
* [[Octave's file types]] | * [[Octave's file types]] | ||
Revision as of 18:05, 31 October 2017
This page contains links to pages of interest to developers. Some links appear in multiple sections.
Getting started
- Developer FAQ
- Contributing to Octave
- 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
- Finding Memory Leaks
- Add BIST tests for octave functions written in C++
- BIST for m-files