Editing Developers
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
This page contains links to pages of interest to developers. Some links appear in multiple sections. | |||
==Getting started== | |||
* [[Developer FAQ]] | |||
* [[Contribution guidelines|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. | |||
* [https://ccache.samba.org/ 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]] | |||
==Works in Progress== | |||
* [[Classdef]] | |||
* [[Java interface]] | |||
* [[JIT]] | |||
==Code sprints== | |||
* [[2015 Code Sprint]] | |||
* [[Code sprint Zurich]] | |||
==Release procedures== | |||
* [[Release Checklist]] | |||
==Other== | |||
* [[Hacking]] | |||
* [[Project Infrastructure]] | |||
[[Category:Development]] |