#118: Ensure Milena supports separate compilation
-----------------------+----------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: defect | Status: new
Priority: critical | Milestone: Olena 1.0ß
Component: Milena | Version: 1.0
Resolution: | Keywords: multiple objects separate compilation
-----------------------+----------------------------------------------------
Old description:
Currently, several things prevent any attempt to use
Milena in a
multiple-object (`.o` files) context:
* method and function definitions shall be tagged `inline` to prevent
any name clash;
* definitions of global variables shall be replaced by function serving
a static variable;
* and so on.
I (Roland) am not sure which test protocol we should use to check this is
fixed correctly in the whole library. Maybe include the whole headers in
two separate units, and link them together. Or proceed component per
component?
New description:
This ticket depends on #43.
Currently, several things prevent any attempt to use Milena in a multiple-
object (`.o` files) context:
* method and function definitions shall be tagged `inline` to prevent any
name clash;
* definitions of global variables shall be replaced by function serving a
static variable;
* and so on.
I (Roland) am not sure which test protocol we should use to check this is
fixed correctly in the whole library. Maybe include the whole headers in
two separate units, and link them together. Or proceed component per
component?
Comment (by levill_r):
Mention ticket:43.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/118#comment:1>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image library.