Hi Daniel,
Core team support ... this work would need not be done by the core team, but if in-depth support in the form of inside knowledge was offered, that should be enough to start with ... Once the cross-compile environment is setup and running, to be used by everyone, this would be a job of everyone to maintain.
Cesc
On 3/30/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
On 03/30/07 12:30, Cesc wrote:
On 3/30/07, Henning Westerholt henning.westerholt@1und1.de wrote:
On Friday 30 March 2007 01:00, Cesc wrote:
Hi,
Just throwing wild ideas ... but if we moved to autotools (we need to look for a guru ... I agree, more than autotools is auto-chaos) we could easily cross-compile ... And that said, it just comes to mind the chance of cross-compiling with mingw and have a windows openser, just for the non-linux user and expand our borders. It may be a cut down version to start with, but wouldn't it be great?
Hi Cesc,
i don't think that it would be so easy to port openser to windows, there are many Unix/ Linux specific thinks specified deep in the code.
More easy cross-compiling could be nice. But then we should use cmake instead of autotools, like the KDE project, because this is usable even for non-gurus like me. :-)
Cheers,
Henning
Hi,
Well, never used cmake myself, so can't tell. Autotools is complicated if starting from scratch, but if using existing configs from some other project, the jumpstart is very big.
As for the port ... i would expect some difficulties in some parts, like locking, loging and memory mgmnt ... also some database access libraries ... but maybe a simple, very cut-down version, with basic functionality, could be realized ...
database should not rise issues. For locking/memory can be used sysv. The module interface should be analyzed. Won't be easy, though...
Cheers, Daniel
Just brainstorming ...
Cesc
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users