Re: no rule to make asm targets

[Stepan Kasal]

Hello,

On Wed, Dec 06, 2006 at 06:21:09AM +0200, Jari Strand wrote:
> >For example, does bin_PROGRAMS really contain only one program?
> 
> Yes, [...]

OK, in that case there is no need to use per-target flags.

Let me show an example:

bin_PROGRAMS = first second third
first_SOURCES = first.c
second_SOURCES = second.c
third_SOURCES = third.c

AM_CFLAGS = ...
second_CFLAGS = ...

In this example, `AM_CFLAGS' is used for all programs, with one
exception: when compiling program `third', `third_CFLAGS' is used
instead.

This `third_CFLAGS' is called per-target variable, and overrides the
corresponding general one AM_CFLAGS.

The mechanism is the same in your case, when you are using *_CPPFLAGS
instead of *_CFLAGS.

Since you have only one program, you can set `AM_CPPFLAGS' as needed
for the program `editorD', and there is no need to use the override
mechanism.

Then, because of some internal mechanisms of Automake, the suffix
rule `.asm.o' will be used, and you can redefine it if you like.

Start with the following code, adding back the things you removed
to simplify the example.

> >bin_PROGRAMS = editorD
> >TLIB_PATH = /home
> >AM_CPPFLAGS = -I$(TLIB_PATH)/openal/LINUX -I$(TLIB_PATH)/lungif \
> >     -I$(TLIB_PATH)/lungif -I$(TLIB_PATH)/opengl2d3d \
> >     -I$(TLIB_PATH)/zlib -I$(TLIB_PATH)/lpng -I$(TLIB_PATH)/ljpeg \
> >     -I$(TLIB_PATH)/vorbis/include -DEDITOR_BUILD
> >editorD_SOURCES = someSource.cc someAsm.asm
> >.asm.o:
> >     $(NASM_PATH) -o $@ -f elf -dLINUX $<

Have a nice day,
        Stepan Kasal