I no longer get the error I mentioned in my last email.
Must be something I did wrong.
Maybe, the only thing is whether there is a better way
to write the rule to create .o and executables in another
directory than what I've done.
Thanks,
Suhas
___
Bug-
Hello,
I am lucky enough to be working on win32 at present. I have:
OBJS = "c:\test dir\main.o"
Unfortunately the quotes are being removed when the various rules are
translated into the command lines (i.e. "gcc -o test.elf $(OBJS)"). Then I
get a bizarre "access denied" message. If I use path
I like the idea of using implicit rules
to do all the work. With that objective, is there an elegant
way to do than doing it as follow:
bld_dir = ../obj
$(bld_dir)/%.o: %.cpp
$(COMPILE.cpp)
$(OUTPUT_OPTION) $<
The above rule above creates all the object files in ../obj
directory.
However
patch_item_1022.patch seems to solve the bug! Hopefully.
Dr. Jörn von Holten wrote:
Hi,
I reduced my problem to the following short Makefile
-snip---
define A
12345: $(1:.idl=.hh) $(1:.idl=S.h) $(1:.idl=C.h) $(1:.idl=SK.cc)
$(1:.idl=DynSK.cc)
endef
$(eval $(call A,012345678
This bug has already been reported and fixed in the source, and the fix
will be included with the next release.
Look here for the bug report; there's a patch attached to it:
https://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=1517
--
---
Hi,
I reduced my problem to the following short Makefile
-snip---
define A
12345: $(1:.idl=.hh) $(1:.idl=S.h) $(1:.idl=C.h) $(1:.idl=SK.cc)
$(1:.idl=DynSK.cc)
endef
$(eval $(call A,01234567890123456789012345678901.idl))
---snap-
which, when evaluated (e.g. "
