Kohei Yoshida wrote:
I'm in the process of creating a CWS for the solver feature I've been
working on for quite some time. I have spoken to Martin Hollmichel
and Michael Meeks about this, and the only bits that we need to be
sure about is whether or not you guys are okay with the naming of
modules.
The way it's set up right now in ooo-build - I may have explained this
before but duplication may not hurt - is that we have a separate
top-level 'lpsolve' module that houses lp_solve as an external
library, and another top level 'scsolver' module that contains the
main code for the solver.
The lpsolve module contains the unmodified lp_solve 5.5 package that
gets unpacked, built, and delivered just like any other external
library would.
The scsolver module builds libscsolver.uno.so shared library, which
dynamically links against liblpsolve55.so to make use of it as LP
algorithm backend. So, licensing-wise (lpsolve is LGPL) we should be
okay.
Let me know if the way it's set up is okay for upstreaming or not.
That would be "lpsolve" in the "external" project and "scsolver" in
"sc"? Sounds good. Martin probably knows better than me about the
necessary steps before actually committing external code.
Niklas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
