|Re: [eigen] External contributions|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] External contributions
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Wed, 4 Feb 2009 05:03:42 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=qfZ7LiWuJN7LPq+JnQPQvOJz00P4NK/8QwRSgWqE7Yc=; b=rhTMLYBRpRUwqr02NKLACf/N39Lv3BOtPS4IBzT5G6DXa7a5nd2eQN4e1N3mQ0F/5m tcdU0/AeFCWLDlAAMBZyd6wMCNe15s/JQAPxEvRHNjoe73OtN5GETKW5LopvjZbknnSQ vPo5m3oQvwNGSR81rXdzNAiFLKyTpZkcXExIw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=J0RGCQVEYcOgBj2tmyaHcXfeml8EJjVcDFmtDGHCU5dWPRUXSfQ8wgyYz9E2RTqWWW LQarrh59vsPaWz7ecqBjp8dMAAapTwkZGNLRPtDH5tQi8mzcyEL7g8dRmTkYI2pXWVjA wzw93UY1DDlqeTvy6x+1PFezfFmOq4z73fRkA=
Thanks for your idea. I too have been thinking about that.
I think that my favorite option is to have a eigen2/unsupported
directory inside which things are organized in the same way as in
eigen2/ itself. So it would look like this:
Then we would install the headers also with the unsupported/ prefix,
but still in the same eigen2/ directory, so it would look like this:
The user would either #include as follows,
or (non default behavior) he could add
/usr/include/eigen2/unsupported/ also to his include path so he could
> - documentation: the easiest would be to use the infrastructure from Eigne
Sure. It's just a matter of:
1) adding the unsupported/ paths to doc/Doxyfile.in, and backport to
Mainpage.dox (for api.kde.org)
2) copy the CMakeLists.txt files under doc/ to unsupported/doc/. They
are the code responsible for building the snippets and recording their
> have for example a different style/background in the doxygen-generated pages
> to indicate it is not supported.
That, or any other visual hint, good idea.
> - contribution policy: what should be accepted as a contribution? For
> example, I have some template files based 100% on Eigen for mechanics
> (Recursive Newton-Euler solver for kinematic chains) and control (algebraic
> riccati equation solver). I am also thinking of a convex optimization
> interior-points methods at a later point.
We have yet to write some clear criteria but I can already say that
what you mention here sounds very good.