Open office ??

Bonjour à tous,
Après les nombreux apports de nos chers Philou et meas_meas, je me suis demandé s'il serait compliqué de porter pour le v-43 les applis open office de linux (ttt de texte et tableur)??
Qu'en pense nos developpeurs ? C'est possible ??

théoriquement tout est portable du moemrent que tu as le code source.

Après OpenOffice, je sais pas combien de lignes de codes ça fait et combien de millions de lib sont nécessaires, mais c toujours possible...

Après faut qqu'un qui s'y colle pendant 1 mois jour et nuit...

Meas ça te dit ??

A+

had5150

Hum... J'ai regardé un peu et je peux te dire que c'est un TRES GROS portage

C'est un super challenge mais un peu trop pour un seul homme

Voila les problemes de portage qu'on risque de rencontrer:

Porting Issues
....
One of the main issues for porting the office suite is to have a working C++ compiler. The following C++ features cause the most difficulties for compilers:

* Use of the Standard Template Library (STL). The office suite uses STLport 4.x, which is an SGI STL adaptation. Conflicts can arise with native includes.
* Deliberate use of templates as a whole.
* Namespaces.
* Exceptions, using exceptions over shared library boundaries (run the ehtest suite in STLport for verification)
* Order of initialization and destruction of global objects, especially since there are a lot of different but dependent shared libraries involved.
* Usage of GCC on most platform recommended (2.95, 3.0 and 3.1 currently supported)

Platform-Dependent Implementation

The most difficult part about platform-dependent implementation is language binding, since it requires some knowledge of the CPU architecture and how the compiler constructs vtables and so on. This is a time-consuming activity. For existing ports, this is implemented in the module bridges.

Loading Shared Libraries

Another area where some development might be necessary is the loading of shared libraries. The source code assumes the availability of dlopen() and associated files. For example HPUX 10.x uses something like shl_load() and names shared libraries differently, however the necessary changes should be minor.

meas_meas a écrit:

Hum... J'ai regardé un peu et je peux te dire que c'est un TRES GROS portage

C'est un super challenge mais un peu trop pour un seul homme

Voila les problemes de portage qu'on risque de rencontrer:

Porting Issues
....
One of the main issues for porting the office suite is to have a working C++ compiler. The following C++ features cause the most difficulties for compilers:

* Use of the Standard Template Library (STL). The office suite uses STLport 4.x, which is an SGI STL adaptation. Conflicts can arise with native includes.
* Deliberate use of templates as a whole.
* Namespaces.
* Exceptions, using exceptions over shared library boundaries (run the ehtest suite in STLport for verification)
* Order of initialization and destruction of global objects, especially since there are a lot of different but dependent shared libraries involved.
* Usage of GCC on most platform recommended (2.95, 3.0 and 3.1 currently supported)

Platform-Dependent Implementation

The most difficult part about platform-dependent implementation is language binding, since it requires some knowledge of the CPU architecture and how the compiler constructs vtables and so on. This is a time-consuming activity. For existing ports, this is implemented in the module bridges.

Loading Shared Libraries

Another area where some development might be necessary is the loading of shared libraries. The source code assumes the availability of dlopen() and associated files. For example HPUX 10.x uses something like shl_load() and names shared libraries differently, however the necessary changes should be minor.

C'est tout

Ouais, c'est vrai, si on relativise c'est pas grand chose

Mais ce qui m'embete le plus c'est la partie Platform-Dependent.
En ce moment, je suis bloqué dans le portage d'une VM java
à cause d'un truc comme ca.
Si y a quelqu'un qui s'y connait en assembleur MIPS.
Je suis preneur

C'est bien ce que je craignais...
Tant pis, enfin si t'as des idées ou si qqu'un d'autre en a, vs savez que ça peut interesser !