Skip to content

Editor: Refactor Windows (Visual Studio) and macOS (XCode) project generators to use dynamic dependency placeholders #1295

@eprikazchikov

Description

@eprikazchikov

Current Behavior

Currently, the project generators for Windows (Visual Studio) and macOS (XCode) use templates that have certain dependencies hardcoded. These include:

  • Libraries
  • Include paths
  • Library paths

Desired Behavior

The templates should be refactored to dynamically include these dependencies based on meta-tags (placeholders) such as:

  • ${libraries}
  • ${libraryPaths}
  • ${includePaths}

These placeholders are already being generated in the NativeCodeBuilder class and should be reused in the template system.

Why This Change Is Needed

Hardcoded dependencies reduce flexibility and maintainability. By using the existing placeholder system, we can:

  • Centralize dependency management
  • Ensure consistency across different generators
  • Simplify future updates to dependencies
  • Leverage already implemented logic in NativeCodeBuilder

Affected Components

  • Windows Visual Studio project generator
  • macOS XCode project generator
  • Associated templates

Additional Context

The required meta-tags (${libraries}, ${libraryPaths}, ${includePaths}) are already available from NativeCodeBuilder. This change primarily involves updating the templates to use these placeholders instead of hardcoded values.

Acceptance Criteria

  • Visual Studio project templates are updated to use ${libraries}, ${libraryPaths}, ${includePaths} placeholders
  • XCode project templates are updated to use the same placeholders
  • Generated projects include the correct dependencies as provided by NativeCodeBuilder

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3This issue is nice to have

    Type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions