[Dune-devel] [GSoC] Keep documentation up to date

[Miha Čančula]

Hello!

I finished converting all the code documentation to the Doxygen format, and
I also added a separate page with use instructions. The instructions are
for using automake, cmake and calling perftest.py directly from the command
line. It is all available in the HTML generated docs.

Right now I'm writing an overview report of a single test run, to see which
tests run the longest, but from this on I'm not exactly sure what to do.
I've deviated considerably from the initial plan, but IMO it's best to
stick with it, and add upload functionality. If you have other priorities,
please tell me.

Thank you, Miha


2013/9/6 Miha Čančula <miha at noughmad.eu>

> Of course, reading the email subject, I still have to update the docs. I
> think the current procedure is intuitive enough to keep it, so I will
> document it as is.
>
> 2013/9/6 Christian Engwer <christian.engwer at uni-muenster.de>
>
>> On Fri, Sep 06, 2013 at 11:09:10AM +0200, Miha Čančula wrote:
>> > I applied the changes, and made a couple of my own, and now I think the
>> > integration works quite well. Thank you especially for the recursive
>> > implementation. The only problem I have is that I can't run individual
>> > tests (using "make perftest TESTS=somethin") from the top directory, as
>> it
>> > also tries the m4/ subfolder, while the tests are only in src/. It works
>> > from src/ though, and I could make the python script just return when
>> > encountering a non-existent test. I made something similar in CMake, the
>> > target is not recursive since I don't think it's a prirority now, but it
>> > works.
>>
>> Great, I'll have a quick look, it shouldn't be too difficult.
>>
>> I'll come back to your other questions later...
>>
>> Ciao
>> Christian
>>
>> PS: I would have appreciated if you kept the author-ship of my
>> patches. git am would have done the trick.
>>
> I must admit I did not think about that. Instead of using git apply (or
> am, which I didn't even know about) I applied the patches individually and
> checked them. I can still amend the commits if you wish, but this can cause
> some trouble after pushing.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20130911/bf429214/attachment.htm>