Bash for loop

Genjix · 12-22-2004, 05:25 AM

Code:

for i in `find | grep .cpp`; \
	do \
		gcc -c $$i; \

		# check for compilation errors
		if [ $? -ne 0 ]; then \
			echo "compilation aborted"; \
			exit; \
		fi; \
	done;

actually in a Makefile, anyone tell me whats wrong with my syntax and how can i get rid of the backslashes?

bigearsbilly · 12-22-2004, 06:52 AM

why is it in a makefile?

If all you are doing is compiling all sources
regardless of dependencies etc.
why not just in a script?

This sort of thing should not ideally be in a makefile.

regards billy

Genjix · 12-22-2004, 10:58 AM

ok, its just that people are so used to typing make that its the accepted standard, and to be honest this method is alot quicker if i simply follow the rule of making all object files end in cpp

Hko · 12-22-2004, 12:22 PM

Sorry, that doesn't make sense (to me).

jlliagre · 12-22-2004, 12:43 PM

You can still have the users type make, and have the Makefile call your external shell script.
That would be far more easier to maintain.

bigearsbilly · 12-23-2004, 02:56 AM

I Wasn't being rude. ;-)

incidentally

Code:

find . -name '*.cpp'

is better
Are your .cpp files in multiple subdirectories?
if not you can do

Code:

for i in  *.cpp

It's probably better to construct a proper makefile though.
It's worth learning make well.

regards billy