Re: [orbitcpp-list] compiler issues

[Andreas K. <ak...@ix...>]

Phil dawes wrote:
> 
> Hi Andreas & everyone,
> 
> The orbitcpp compiler is a bolt-on to the orbit-idl compiler. I have a
> couple of questions:
> 
> 1) Currently you must install the plugin C++ backend library before you
> can use the compiler. Is there anyway around this?
> Ideally I'd like to be able to run the compiler with the library in the
> build directory so that the tests can be run without installing the
> compiler. (Otherwise this will break nifty things like make distcheck)
> Do I have to patch the orbit-idl compiler to supply a backend directory
> as an argument?

at least. but libtool won't make your job that easy.
(you might try libtool --mode=execute ...)

> 
> 2) Currently you must issue 2 commands to generate the stubs/skels:
>         orbit -l c blah.idl
>         orbit -l c++ blah.idl
> How easy is it to integrate the call to the C compiler into the C++
> backend, thus reducing it to
>         orbit -l c++ blah.idl

i asked elliot about this. currently, we would either have to duplicate
code (10 lines or so) from orbit-idl or patch it to make those calls
easier. neither seems worth the trouble, since they consider their
backend interface "rather a joke". i believe we should go with the two
commands until they rewrite their compiler. 

cu
andreas