Hi all,
Seeing as you're all game ;)...
The makefile I'm trying to beat into submission now gets to the point
where it builds a dependency file using the following command:
g++ -M $(CPPFLAGS) $(SRC) > $(DEPSFILE)
This generates output in $(DEPSFILE) that looks like this:
vertex.o: src/vertex.cpp \
/HostFS::HostFS.$$/AppsInUse/Dev/GCC474r1/!GCC/bin/../lib/gcc/arm-unknown-riscos/4.7.4/../../../../include/c++/4.7.4/iostream
\
/HostFS::HostFS.$$/AppsInUse/Dev/GCC474r1/!GCC/bin/../lib/gcc/arm-unknown-riscos/4.7.4/../../../../include/c++/4.7.4/arm-unknown-riscos/bits/c++config.h
\
/HostFS::HostFS.$$/AppsInUse/Dev/GCC474r1/!GCC/bin/../lib/gcc/arm-unknown-riscos/4.7.4/../../../../include/c++/4.7.4/arm-unknown-riscos/bits/os_defines.h
\
etc., etc.
The problem then becomes, that when this dependency file is parsed by
make, it sees the colon(s) in "/HostFS::HostFS.$$/Blah-blah..." as another
rule, and gives the error message: "multiple target patterns". On the
Internet, I've seen a lot of references to this when people use make under
Cygwin, and have the same problem with a "C:\" path in Windows.
What would be great is if there was a way to make the dependencies output
use a RISC OS system variable -- ideally GCCbin$Path looks the most
sensible -- so that absolute paths aren't hard-coded into the dependencies
file in the first place. Is there a way to do this? And will it resolve
the colon problem anyway?
Is there some other way around the colon problem? How do people normally
handle dependency data using GCC on RISC OS?
Really appreciate all your help so far, guys. Quite a learning curve, this
is!
WPB
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment