Tom Tromey wrote:
>>>>> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes:
Alex> As IDL files use standard C preprocessor syntax for dependent
Alex> inclusion, is it not possible to wrap the idl compile in
Alex> depcomp?
Interesting idea. I thought different IDL compilers generated
different output file names, though. Is that not the case? If it is
the case you'll still need autoconf/automake hackery, I think.
That's just the case. I'm not very good at dependencies ;-), but If I've
not missed anything, dependencies are generated from the idl-generated
files, not vice-versa. As each ORB generates a different set of files, you
must write Makefile rules having only the information of:
1. The ORB being used
2. The options to IDL compiler (tie, etc.)
3. the name of the IDL file.
Those makefile rules have some restrictions due to the CORBA development
process. I'll explain myself a little better:
This is my first idea rewritten:
Suppose that I have a project that is half way. Suppose that I managed to
write some autoconf/automake macros that can deal with different ORBs
(such as those written by Ruslan). These macros allow to write code that
can have #include file hacks to deal with various ORBs, etc.
The problem is (besides designing the macros for successfully configuring
different ORBs, not little job at all) how I generate new makefile rules
for
(i) Generating stub and skeleton files from a new IDL file written (I
mean, generating the rules for executing the "idl" program of the specific
ORB)
(ii) Rules for compiling the newly created files.
What I propose as a solution to the last two points is a
configure-modified script that is capable of generating those rules
modifying the existing Makefile.am and/or Makefile.in. Of course, the
script must be prepared to deal with different ORBs, and the configuration
process must prepare it for generating afterwards the correct rules
depending on the ORB being actually used. So the steps on doing this would
be:
1. Run automake/autoconf. This will generate the initial Makefile.in
2. Run "configure". This will modify the "Generator" script
3. Run the "Generator" when you write a new IDL file. This will modify
Makefile.am, needing a new run of autoconf/aucomake/configure, (isn't it?)
Those three steps are only needed at development phase. When installing,
the installer only have to run "configure" and "make" as always.
Does this make sense?
Regards and thanks in advance.
diego.
Alex> I think this is really close. Could a depcomp guru please
Alex> confirm or deny? :)
Definitely.
Tom
--
Diego Sevilla Ruiz -- http://www.ditec.um.es/~dsevilla/
Departamento de Ingeniera y Tecnologa de Computadores
Facultad de Informtica. Universidad de Murcia
Campus de Espinardo - 30080 Murcia (SPAIN)
Tel.: +34-968-367570
E-mail: [EMAIL PROTECTED]
$_="\\l/) (>". "_'\n<";@@= /.|\n/g;$_=
"\@". "\007f". "DDq". "DD5". "\204".
"\@". "DT4CE". "D54E". "DD". "\244".
"\021". "dBDTC". "\010DD". "\200\$FD\024".
"GDAG". "DAGDT". "CqI";$c =0;$p =5;for$q
(/./g) {$q= ord$q; for(a, b){$z[$c]
=$@[$p+=($q&15) -4];$q>>=4;$c+=33 ;$c>98 &&($c-=98);}};print@z;
