Re: proposed patch for orogen/typegen

On Fri, Feb 1, 2013 at 2:05 PM, Sylvain Joyeux <[email protected]> wrote:
> On 01/31/2013 05:44 PM, Peter Soetens wrote:
>>
>> Also, I had a question regarding typegen -i pkgname, where 'pkgname'
>> is also typegen generated:
>> It seems that it picks up the .tlb files, but still the code for the
>> transport of these earlier defined types is generated. Can typegen be
>> changed such that for these -i specified packages, no code is
>> generated anymore ?
>
> It is a typegen-specific issue, orogen does show the "right" behaviour.
>
> I'm having a look and I am puzzled. Could you send the .pc file for the
> imported typekit ?

This patch on typegen fixes it:

$ di
diff --git a/bin/typegen b/bin/typegen
index 517448f..971a0e7 100755
--- a/bin/typegen
+++ b/bin/typegen
@@ -38,9 +38,10 @@ this installation of typegen knows the following
transports: #{available_transpo
               exit(1)
             end
         end
-        if pkg.typelist && !pkg.typelist.empty?
-            typekit = typekit_loader.load_typekit(name)
-            typekit.using_typekit(typekit)
+        if pkg.type_registry && !pkg.type_registry.empty?
+             STDERR.puts "Typekit: #{name}"
+            newtypekit =
typekit_loader.load_typekit(pkg.project_name)
+            typekit.using_typekit(newtypekit)
         else
             typekit.using_library(pkg)
         end

So typelist -> type_registry and store the result of loading in a
different var ...

Now the code is correctly generated, but I don't know if this is not
obfuscating a deeper-down bug...

Peter
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev