Thread: I have an error with my make file.

The problem isn't in tankmain.c but in (probably) tankmain.h where I expect you missed out a semicolon or have some extra "rubbish" in the file [I have been known to accidentally put characters at the beginning or end of files when not paying attention to what I'm doing, and end up with "strange" errors like this].

--
Mats

Thanks for the suggestion.

I tried removing tankmain.h, as it has nothing in it yet (I removed it from the make file, main file and deleted the file itself) And I still receive the same error.

I then added everything back in and tried putting the .h files in this order.

Code:

#include "tankmain.h"
#include "world.h"

and I still receive the same error.

Maybe this will help clarify the problem.. This is the content of my world.h and make file

world.h // pardon the class's I am not entierly sure if they are correct it some of the stuff im learning at the moment

Code:

#ifndef __WORLD_H__
#define __WORLD_H__


#include <math.h>
 

using namespace std;


class boundaryType {
	public:
		float x1,y1,x2,y2;
};

class world2D {
	public:
	float degToRad (float);	
	int Xdev(void);
	int Ydev(void);
}

#endif

Makefile

Code:

tankmain.exe		: 	tankmain.o graphics.o world.o
	g++ -Wl,-s -o tankmain.exe tankmain.o graphics.o world.o 
			
tankmain.o		:	tankmain.cpp tankmain.h graphics.h
	g++ -c -fpermissive -fconserve-space tankmain.cpp	
	
world.o 			: world.cpp world.h  
	g++ -c -fpermissive -fconserve-space world.cpp

graphics.o		:	 graphics.cpp graphics.h
	g++ -c -fpermissive -fconserve-space graphics.cpp

again thanks for the help !

You're missing a semicolon at the end of your world2D class.

Code:

class world2D {
	public:
	float degToRad (float);	
	int Xdev(void);
	int Ydev(void);
};

QuantumPete

Yes, of course, if you include an empty header file (or one that has been included previously and is properly guarded against multiple inclusion), then the previous header file becomes the candidate, and so on with this type of error.

--
Mats

> God you get so caught up thinking its one this you miss something small like that!!!
> thanks again.. now I got a bunch of errors to deal with! lol
Well if you'd compiled it 5 minutes after writing it, rather than what - a few hours, then you'd have a lot less errors to look at, and a lot more idea of where to start looking.
http://cboard.cprogramming.com/showthread.php?t=88495

In short, don't code beyond your ability to deal with the compiler throwing the whole lot back at you as utter garbage.

With a decent makefile (like you have), it shouldn't take more than a few seconds to check you're still on track.