Alex Hornby wrote:
> 
> Ruslan Shevchenko writes:
>  > Are exists some documentation online ?
>  > How it determinate the name and number of generated source files ?
>  >
> 
> It takes them as environment variables. For example here is one of my
> my TAO rules.
> 
> .idl_c.hh:
>         source='$<' object='$*_c.hh $*_s.hh $*_c.cpp $*_s.cpp $*C.i $*S.i' \
>         libtool=no \
>         depfile='$(DEPDIR)/$*.Pcpp' \
>         tmpdepfile='$(DEPDIR)/$*.TPcpp' \
>         depmode=cpp $(depcomp) \
>         tao_idl $<
> 
> I don't know of any documentation yet, but IMO the source is pretty
> clear.
> 
> Alex.

1. different ORB use different extensions. 

  what mean .idl_c.hh : idl 2 c and hh ?
   can it be somethin like:
         idl_$(CORBA_CPP_EXT).$(CORBA_H_EXT) 
   ?
   If yes, then I will include $(CORBA_CXX_EXT).$(CORBA_H_EXT) in
  next revision of CORBA macroses.

2. different ORB generate different set of output files.

>     source='$<' object='$*_c.hh $*_s.hh $*_c.cpp $*_s.cpp $*C.i $*S.i' \

   In "generalized" my views, it looks, like:
     source='$<'  object='$*'$(IDL_CLN_H_SUFFIX) \
 '$*'$(IDL_CLN_CPP_SUFFIX)  '$*'$(IDL_SRV_H_SUFFIX) \
 '$*'$(IDL_SVR_CPP_SUFFIX) \
  [pseudocode:] $(IDL_CLN_H1_SUFFIX) if it is not "no" \
  ....

O'key, in principle is possible.
Can such string be generated automatically by automake ?


2. How to determinate, what generated source needed for client 
 and what to server (?). Usially I needs in separate Client
 and Server+Client set of files, defined in Makefiles{.in,.am}
 In case of using idldept we need in special
 separate utility for this ? Can you think a little on this topic,
 and help me to decide: where it must be called and what it must
 produce.

3.  What means deptmode ?

4.  different ORB use different names for compilers.  
 It can be $(IDL2CXX) $(IDLFLAGS) $< ?

P.S. 2 Peter & official autoconf people ?
 What are status of my ORB checking macroses in autoconf archive ?
 Are they reviewed, or they comed to black hole ?
 I understand, that all are very busy, but I think, that
 short and quick feedback for submissions is not very difficult;
 at the same time it's  stimulate contributions and development.

Reply via email to