Kohei Yoshida wrote:
Hi all,
I was hoping that someone on this list could help me out on this.
Here is what I'm trying to do. I have a top level module called
'scsolver' which provides an optimization solver component for Calc
(or just 'Solver' for short). You don't see this in the upstream
build since this module is still ooo-build only, just in case you're
wondering.
In this module, I need to include a set of new, private UNO IDLs to
glue the main Solver component with an external optimization library.
Both the main component and the external component need to be able to
use these UNO interfaces, which means that, somehow the source files
in this module need to be able to find the header files (*.hpp) that
are generated from my IDLs. The external library, for now, will
remain inside the scsolver module.
So, how do I go about defining my private IDLs at module level,
without adding them to the master list used by the entire OO.o source
tree? I've check the source, and the chart2 module may have done
something similar, but I'm not entirely sure how it's done.
The by far easiest approach would be to do add your UNOIDL entities to
CVS module offapi, but to not mark them as published so that they can
change over time if there is a need (you might also want to add some
comment that those are private entities that are not intended to be
published at all, and you might want to choose some appropriately named
UNOIDL module for them). That way, you do not need to fiddle with the
details of cppumaker, and your UNO types are readily available in every
UNO environment (Java, CLI, etc.) where you might need them in the future.
-Stephan
Thanks in advance,
Kohei
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
