[ccmtools-devel] Re: [ccmtools-cvs] ccmtools/IDLGenerator IDL2GeneratorImpl.java,1.9,1.10

[Leif J. <le...@am...>]

Hmm. I removed this code because it was part of the finalize() function
before. I was a bit wary of this but figured the Makefiles that it wrote
were in fact the same as those in the CppRemoteEnvironment ... must not
have been the case.

I still don't want to add back the finalize() method, since it's crufty.

Instead, you could fix this by doing :

    protected void writeOutput(Template template)
        throws IOException
    {
	super.writeOutput(template);

        template = template_manager.getRawTemplate("MakefilePy");
        output = new File(output_dir, "Makefile.py");
        if (template != null && ! output.isFile())
            writeFinalizedFile("","Makefile.py",template.getTemplate());

        template = template_manager.getRawTemplate("MakefileIdl");
        output = new File(output_dir, "Makefile");
        if(template != null && ! output.isFile())
            writeFinalizedFile("", "Makefile", template.getTemplate());
    }

Or, since these templates don't require information from the CCM graph,
we could treat them as environment files and create an IDL environment
concept ...

leif

On Fri, 2003-12-19 at 07:12, tei...@us... wrote:
> + To generate the Makefile.py and Makefile I changed the IDL2 generator.
>   The problem with this solution is that these files are generated with
>   every single IDL file.

-- 
Leif Morgan Johnson : http://ambient.2y.net/leif/