Simon Lundmark
Simon Lundmark
Looking really good! Will you be adding it to the lib or will it just be a snippet?
What would submenues within a pie-popup look like?
Another idea would perhaps be to expand the pie outwards, presenting a top-down menu. The amount of choices could be increased by increasing the size of the extended pie-slice upwards/downwards?
This should probably look something like this instead: ``` local depgraph = require 'tundra.depgraph' function _mt:create_dag(env, data, deps) return depgraph.make_node { Env = env, Pass = data.Pass, Label = "MyCompiler...
It shouldn't be Inputs / Outputs, it should be InputFiles / OutputFiles. Is it possible to get ConfigInvariant working on your own Unit Extension somehow?
This also seems to be an issue when having a deeper nested hierarchy, such as: StaticLibrary { name = "foo" } StaticLibrary{ name = "bar", Depends = { "foo" },...
This goes for all Propagates such as includes, defines etc.
This seems to solve the issue for me. It's recursive though, so expensive :/ Perhaps add a flag to the unit for the recursive-functionality? ``` diff --git a/build/tundra2/scripts/tundra/nodegen.lua b/build/tundra2/scripts/tundra/nodegen.lua ---...
Sorry, I'm not sure if that one included my change on (the new) line 309 where ``` local function resolve_dependencies(decl, raw_deps, env) ``` needs to be ``` function resolve_dependencies(decl, raw_deps,...
Note that this does not fix the #195 - issue regarding double-linkage.