Equivalence between sources and generates

Hello!
Okay, this might be a strange use case since it's not really supported by any build system that I know of.

I would want to map the

sources

sources

to the

generates

generates

. Take the following example:

  PSD-to-PNG:
    sources:
      - psd/**/*.psd
    generates:
      - png/**/*.png
    cmds:
      - for: sources
        cmd: convert {{.ITEM}} TARGET

  PSD-to-PNG:
    sources:
      - psd/**/*.psd
    generates:
      - png/**/*.png
    cmds:
      - for: sources
        cmd: convert {{.ITEM}} TARGET

If I have a file

psd/sprite/enemy.psd

psd/sprite/enemy.psd

(here an iteration of {{.ITEM}}), I would like to create

png/sprite/enemy.png

png/sprite/enemy.png

(here TARGET), knowing that at first my png folder is empty. I don't know if there's a simple way to get this TARGET, except with regexps that would defeat the purpose of readability (and not depend on

generates

generates

at all...). I wonder if there's a simpler way to achieve that?

Thanks!

Task•8mo ago•

15 replies

Keb

Equivalence between sources and generates

Hello!
Okay, this might be a strange use case since it's not really supported by any build system that I know of.

I would want to map the

sources

sources

to the

generates

generates

. Take the following example:

  PSD-to-PNG:
    sources:
      - psd/**/*.psd
    generates:
      - png/**/*.png
    cmds:
      - for: sources
        cmd: convert {{.ITEM}} TARGET

  PSD-to-PNG:
    sources:
      - psd/**/*.psd
    generates:
      - png/**/*.png
    cmds:
      - for: sources
        cmd: convert {{.ITEM}} TARGET

If I have a file

psd/sprite/enemy.psd

psd/sprite/enemy.psd

(here an iteration of {{.ITEM}}), I would like to create

png/sprite/enemy.png

png/sprite/enemy.png

generates

generates

at all...). I wonder if there's a simpler way to achieve that?

Thanks!

Equivalence between sources and generates

Similar Threads

Equivalence between sources and generates

Similar Threads

Similar Threads

Similar Threads