Olena-patches August 2010

olena-patches@lrde.epita.fr

6 participants
204 discussions

by Olena

#169: Lighten the repository -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Getting a fresh working copy from the repository takes time, as there are many medium- or big-sized files (images and meshes). We should probably remove some of them, or move them elsewhere. Of course, we should remove most of these files from the distribution as well. -- Ticket URL: <https://trac.lrde.org/olena/ticket/169> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #222: Clean up the Git repository

by Olena Trac

#222: Clean up the Git repository -----------------------------+---------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: minor | Milestone: Component: Olena | Version: 1.0 Keywords: rewrite history | -----------------------------+---------------------------------------------- Warning, this requires a whole rewriting of the repository with `git- filter-branch`. Notify users in advance. To be performed during vacations? Tasks: * Author name: s/Nicolas Croiset/Tristan Croiset/. * Remove copyrighted files. * ... (list them here) * What else? -- Ticket URL: <https://trac.lrde.org/olena/ticket/222> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #202: Document build procedures

by Olena Trac

#202: Document build procedures ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: task | Status: new Priority: critical | Milestone: Component: Trac | Version: 1.0 Keywords: gcc icpc | ----------------------+----------------------------------------------------- Write a Trac page (several pages?) on these topics: * Why `make` is the way to go. * Why you should (normally) run `bootstrap` only once. * Why you should (normally) run `configure` only once per build directory. * How to build Olena with the Intel C++ Compiler (ICC) * By setting it a build time (not very good). * By setting it a configuration time (better). * By setting it in a `config.site` file (the best). * How to automate things using `CONFIG_SITE`. * Why compiling from Emacs (using `M-x compile`) is better than... * ...Compiling with `make` from a terminal. * ...Compiling with `g++` from a terminal (arg!). This is not restricted to Olena, so we might want to move this material elsewhere later. -- Ticket URL: <https://trac.lrde.org/olena/ticket/202> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #224: Automatically generate ChangeLog entries

by Olena Trac

#224: Automatically generate ChangeLog entries -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: major | Milestone: Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Instead of documenting changes both in Git messages ''and'' !ChangeLog entries, just rely on the first and generate the latter. Use Jim Meyering's `git-to-changelog` script. * http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob_plain;f=build- aux/gitlog-to-changelog * http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/gitlog-to- changelog We can pick some hints and ideas here: * http://git.savannah.gnu.org/cgit/coreutils.git/plain/HACKING * http://git.savannah.gnu.org/cgit/coreutils.git/plain/Makefile.am * http://cyberelk.net/tim/2009/06/25/generating-changelog-files-from- commit-logs/ I suggest we still 1. Record the !ChangeLog into the repository, so that we can fix it (and keep the fixes!). 1. Keep the date of the last !ChangeLog generation so that we generate only the missing entries next time. There's a additional problem with Olena's repository: we have several !ChangeLogs and the system should be either smart enough to find the right !ChangeLog (!ChangeLogs?) or accept tags/metadata to generate entries at the right place. -- Ticket URL: <https://trac.lrde.org/olena/ticket/224> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #196: Kill Doxygen warnings in Olena 1.0

by Olena Trac

#196: Kill Doxygen warnings in Olena 1.0 --------------------+------------------------------------------------------- Reporter: theo | Owner: Olena Team Type: task | Status: new Priority: major | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- `doxygen` emits warnings for certain documented parts; adjust the documentation or Doxygen's options to get rid of them. -- Ticket URL: <https://trac.lrde.org/olena/ticket/196> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #218: Check for unnecessary includes.

by Olena Trac

#218: Check for unnecessary includes. ---------------------+------------------------------------------------------ Reporter: lazzara | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | ---------------------+------------------------------------------------------ Few files may includes unnecessary files. Write a program and include these files: #include <mln/core/var.hh> #include <mln/core/image/image2d.hh> #include <mln/debug/iota.hh> #include <mln/debug/println.hh> #include <mln/pw/image.hh> You will be able to use p_array and sub_image without including their related files. Unnecessary includes slow down compilation and is damaging. -- Ticket URL: <https://trac.lrde.org/olena/ticket/218> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #195: Organize accumulators in subdirectories

by Olena Trac

#195: Organize accumulators in subdirectories -------------------------+-------------------------------------------------- Reporter: theo | Owner: Olena Team Type: enhancement | Status: new Priority: critical | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- For instance: * `accu/stats/` * ... * What else? -- Ticket URL: <https://trac.lrde.org/olena/ticket/195> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #208: Fix dependencies of the HTML documentation generation?

by Olena Trac

#208: Fix dependencies of the HTML documentation generation? ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: minor | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: doc | ----------------------+----------------------------------------------------- The generation of the HTML documentation requires a file named `html.sty`, which is not provided by HeVeA, but by latex2html. Is that right? I thought we only had a dependency on the former, not the latter. -- Ticket URL: <https://trac.lrde.org/olena/ticket/208> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #219: Add \internal in the documentation of internal code

by Olena Trac

#219: Add \internal in the documentation of internal code ---------------------+------------------------------------------------------ Reporter: lazzara | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | ---------------------+------------------------------------------------------ Currently, in order to not expose the internal code in the user documentation, everything in the internal and trait namespaces is ignored during the doc generation. The main issue is that inherited members are not shown in the documentation of the classes exposed to the user. The only way to ask Doxygen to show inherited members and not to show internal documentation is to add \internal in the documentation of internal code. -- Ticket URL: <https://trac.lrde.org/olena/ticket/219> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

[Olena] #235: Support GraphicsMagick++ and drop support for ImageMagick++

by Olena Trac

#235: Support GraphicsMagick++ and drop support for ImageMagick++ -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: major | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: io external | -------------------------+-------------------------------------------------- !GraphicsMagick (http://www.graphicsmagick.org/) seems to provide a framework more modern than !ImageMagick's (http://www.imagemagick.org), in particular regarding multi-core support. Moreover Fabien has discovered weird behaviors (#210) and Buildbot has also recently exhibited run time errors that did not surface before (https://buildfarm.lrde.org/buildfarm/oln/builders/i486-linux-gnu- gcc-4.1/builds/539/steps/check/logs/stdio) -- though I don't know who's the culprit here. -- Ticket URL: <https://trac.lrde.org/olena/ticket/235> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

12 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Olena-patches August 2010