efl/edje: codegen shouldn't use BUILT_SOURCES.

if use BUILT_SOURCES it will always generate those files, and their
requirement codegen.edj, even if examples were not to be built.

make will automatically build the files if there are rules to do so,
we just have to clean them.

SVN revision: 82275

diff --git a/src/examples/edje/Makefile.am b/src/examples/edje/Makefile.am
index a070801..97bcd1c 100644 (file)
--- a/src/examples/edje/Makefile.am
+++ b/src/examples/edje/Makefile.am
@@ -140,11 +140,13 @@ AM_CPPFLAGS = \
 -DPACKAGE_DATA_DIR=\"$(datadir)/edje\" \
 @EDJE_CFLAGS@
 
+CODEGEN_GENERATED = \
+codegen_example_generated.c \
+codegen_example_generated.h
+
 codegen_example_generated.c codegen_example_generated.h: codegen.edj
        $(AM_V_GEN)$(EDJE_CODEGEN) $(EDJE_CODEGEN_FLAGS) codegen.edj example_group $(builddir)/codegen_example_generated.c $(builddir)/codegen_example_generated.h
 
-BUILT_SOURCES = codegen_example_generated.c codegen_example_generated.h
-
 edje_codegen_example_SOURCES = \
 edje-codegen-example.c
 nodist_edje_codegen_example_SOURCES = \
@@ -197,7 +199,7 @@ endif
 examples: $(EXTRA_PROGRAMS) $(EDJS)
 
 clean-local:
-       rm -f $(EXTRA_PROGRAMS) $(EDJS)
+       rm -f $(EXTRA_PROGRAMS) $(EDJS) $(CODEGEN_GENERATED)
 
 install-examples:
        mkdir -p $(datadir)/edje/examples