Thread subtasks in an NE build (DEF-3616)

Open
#318 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Inspect the build orchestration entry point and trace how extension builds, Android .java compilation, .dex generation, and engine linking are sequenced. Confirm the current build dependencies before defining parallel subtasks; done means independent work runs concurrently without breaking the resulting native extension build.

Written by the indexing model from the issue text.

Description

enhancement

Some builds take more time than they should.

Although the worst pain point is waiting for the unit tests, I feel that if it's easy to do, we should try building in parallel.

  • Each extension by itself
  • Android - The .java files by itself (probably solved by building each extension by itself)
  • Android - The .dex file by itself, parallel to linking the engine
Dominant language
Java
Stars
67
Forks
25
Avg merge
1d 1h
Merged PRs (30d)
16

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defold/extender

All issues in defold/extender

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.