Support customed cpp_outs and options for plugins in proto_library

[noanswer]

• Generate customed cpp filenames in proto_library.
• Pass customed options to plugins in proto_library

[chen3feng]

These two attributes are actually belonged to the plugin. Can they be defined as plugin-level attributes ? By this way, they don't need to be written repeatedly for each proto_library call.

[noanswer]

cpp_outs and plugin_opts would be differnent in differnent targets. The plugin will fragment the original file into multiple pieces based on the size of the proto generated, which the user will specify in different targets, the default is divided into 3 pieces.

Here is the code we will add in BLADE_ROOT:

if get_env("USE_ADTABLE_PLUGIN_FAST_MODE"):
    def _register_proto_library_wrapper():
        from blade import proto_library_target
        from blade import build_rules
        def proto_library(*args, **kwargs):
            default_opts = ["fast_mode", "sharding_size=3"]
            default_cpp_outs = [".pb", ".core.pb", ".controller.pb", ".axu.pb", ".core.1.pb", ".core.2.pb", ".core.3.pb"]
            default_applied = False
            if "plugins" in kwargs and "adtable_codegen" in kwargs["plugins"]:
                if "plugin_opts" not in kwargs:
                    kwargs["plugin_opts"] = {"adtable_codegen":default_opts}
                    default_applied = True
                elif "adtable_codegen" not in kwargs["plugin_opts"]:
                    kwargs["plugin_opts"]["adtable_codegen"] = default_opts
                    default_applied = True
            if default_applied:
                if "cpp_outs" not in kwargs:
                    kwargs["cpp_outs"] = []
                kwargs["cpp_outs"].extend(default_cpp_outs)
                kwargs["cpp_outs"] = list(set(kwargs["cpp_outs"])) # unique
            return proto_library_target.proto_library(*args, **kwargs)
        build_rules.register_function(proto_library)
    _register_proto_library_wrapper()