Benefits of Dynamic Build Names

Oct 13, 2025 by ludoplayers7.com 53 views

As part of the ongoing development of BpyBuild 5.2, one of the exciting features being worked on is the improvement of build names to make them more dynamic and flexible. This feature aims to allow users to specify various aspects of the build process, such as the operating system, Blender version, extension vs legacy, and more. In this article, we will outline the overall plan for this feature, including templating, basic built-in variables, and extensibility with actions.

Templating: The Foundation of Dynamic Build Names

Templating is the core concept behind dynamic build names. It allows users to create build names that can be customized based on various factors. At a basic level, templating can be achieved using a simple syntax, such as:

build_name: "MCprep_addon_{version}"

However, sometimes we may want to have multiple options, such as x86 vs arm, or extension vs legacy. To achieve this, we can extend the templating syntax, like so:

build_name: "MCprep_addon_{version}_{extension|legacy}"

Or, if we don't care if a variable isn't defined, we can use a syntax like this:

build_name: "MCprep_addon_{version}_{?legacy}"

Some ideas for directives that can be used in templating include:

foo|bar - if foo doesn't exist, use bar
?foo - if foo doesn't exist, just ignore and remove surrounding characters
*?foo - same as before, but don't remove surrounding characters

The string would be parsed ahead of time and validated for syntax and if a variable would exist (where needed). Additionally, it's possible to allow extending the templating language with actions, although this is more of a "nice to have" feature.

Basic, Built-in Variables: Extensibility with Actions

Variables for templating should be extensible with actions, just like everything in BpyBuild. However, we'd want to be able to validate variable names ahead of time, so there will be 2 parts to adding new variables:

Create an action with the define_output_var hook
Add the variable to the defines section:

dev: 
  script: "dev.py"
  ignore_filters: 
    - "*.blend"
  defines:
    - foo

As for built-in variables, although we currently have a few in the milestone branch, I have plans to refactor it down to the following:

extension and legacy
version (based on either blender_manifest.toml or __init__.py)

OS and CPU specific variables were originally planned, but I don't think those are really suitable to implement as a general thing (if an addon needs those things, they could just create actions based around the addon's full build process).

Benefits of Dynamic Build Names

Dynamic build names offer several benefits, including:

Flexibility: With dynamic build names, users can create build names that can be customized based on various factors, such as the operating system, Blender version, and more.
Customization: Dynamic build names allow users to create build names that are tailored to their specific needs, making it easier to manage and organize their builds.
Extensibility: Dynamic build names can be extended with actions, making it possible to add new variables and customize the build name further.

Conclusion

In conclusion, dynamic build names are an exciting feature that will be introduced in BpyBuild 5.2. With templating, basic built-in variables, and extensibility with actions, users will be able to create build names that are flexible, customizable, and extensible. This feature will make it easier to manage and organize builds, and will provide users with more control over their build process.

Future Development

As the development of BpyBuild 5.2 continues, we will be working on refining the dynamic build name feature, including:

Refining the templating syntax: We will be refining the templating syntax to make it more intuitive and easier to use.
Adding new built-in variables: We will be adding new built-in variables, such as OS and CPU specific variables, to make the build name more dynamic.
Extending the templating language with actions: We will be extending the templating language with actions, making it possible to add new variables and customize the build name further.

As we continue to develop BpyBuild 5.2, we want to make sure that you, our users, have all the information you need to take advantage of the new dynamic build name feature. In this article, we'll answer some of the most frequently asked questions about dynamic build names.

Q: What is dynamic build naming?

A: Dynamic build naming is a feature that allows you to create build names that can be customized based on various factors, such as the operating system, Blender version, and more. This means that you can create build names that are tailored to your specific needs, making it easier to manage and organize your builds.

Q: How does templating work in dynamic build naming?

A: Templating is the core concept behind dynamic build naming. It allows you to create build names that can be customized based on various factors. You can use a simple syntax, such as {version}, to insert the version number into the build name. You can also use more complex syntax, such as {version}_{extension|legacy}, to insert multiple values into the build name.

Q: What are some examples of directives that can be used in templating?

A: Some examples of directives that can be used in templating include:

foo|bar - if foo doesn't exist, use bar
?foo - if foo doesn't exist, just ignore and remove surrounding characters
*?foo - same as before, but don't remove surrounding characters

Q: How do I add new variables to the build name?

A: To add new variables to the build name, you can create an action with the define_output_var hook. You can then add the variable to the defines section of the build configuration.

Q: What are some built-in variables that will be available in dynamic build naming?

A: Some built-in variables that will be available in dynamic build naming include:

extension and legacy
version (based on either blender_manifest.toml or __init__.py)

Q: Can I add my own custom variables to the build name?

A: Yes, you can add your own custom variables to the build name by creating an action with the define_output_var hook. This will allow you to add new variables to the build name and customize it further.

Q: How do I extend the templating language with actions?

A: To extend the templating language with actions, you can create a new action that implements the define_output_var hook. This will allow you to add new variables to the build name and customize it further.

Q: What are some benefits of dynamic build naming?

A: Some benefits of dynamic build naming include:

Flexibility: With dynamic build naming, you can create build names that can be customized based on various factors.
Customization: Dynamic build naming allows you to create build names that are tailored to your specific needs, making it easier to manage and organize your builds.
Extensibility: Dynamic build naming can be extended with actions, making it possible to add new variables and customize the build name further.

Q: How do I get started with dynamic build naming?

A: To get started with dynamic build naming, you can start by reading the documentation on the BpyBuild website. You can also join the BpyBuild community to ask questions and get help from other users.

Conclusion

In conclusion, dynamic build naming is a powerful feature that will be introduced in BpyBuild 5.2. With templating, basic built-in variables, and extensibility with actions, you'll be able to create build names that are flexible, customizable, and extensible. We hope this Q&A article has helped you understand the basics of dynamic build naming and how to get started with it.