Hi there

I'm having some trouble compileng my program in the terminal.

I read the tutorial on this site, but it didn't really help much

i have 8 files that i have written;

AIsnake.cpp
Snake.hpp
AIsnake.cpp
Snake.hpp
food.cpp
food.hpp
GameEvent.cpp
Gameevent.hpp

I use the stl list header, and several headers that are contained in a file called prg.

could someone please tell me how to compile this?

thanks

ES

What command lines have you tried and based on which tutorial(s) ?

http://www.linuxquestions.org/linux/...ams_on_Linux_0

i used this tutorial, but it doesn't really go into much detail

What about the second part of my question, i.e. what command lines did you use ?

this is what i typed into the terminal

g++ -ansi -pedantic main.cpp gameevent.cpp gameevent.hpp etc etc for all the files i stated above -o snakegame

not sure if this is what your asking about though...

So, what were the warning/error messages if any ?

I'm sorry, I can't remember.

I had to leave the programming Lab (it's 1am here) and I'm using windows at home.

should what I typed have worked? assuming everything is write with the code?

So, then don't start a thread. I.e. if you have a problem, you have to be able to exactly show what the problem is. Otherwise the thread looks like translated literally from Russian saying: "Bring me something I don't know what, process that something I don't know how".

I was still in the lab when I started the thread, I have since left.

I'm sorry, I thought there would be a standard command for grouping all the different files I need into on

I know the g++ "-ansi -pedantic" is right and I know the "-o Snakegame" is the name of the output file. The only thing i needed to know was how I should put my file names in, whether just putting them in one big list was right, or whether there was something similar to the "-o" that needed to be added

You need a MAKE file....

Nice...

-ansi -pedantic is superfluous at this point; it just makes things confusing. Leave that stuff out and use -Wall instead, which will give you a warning about everything the compiler is capable of warning about (good for mitigating bugs.) When you compile again, please post all the output and the source file(s).

In my experience, one first perfects his or her source files, then learns what's wrong with them from the compiler. If you haven't compiled your code before, despite it looking correct, in all likelihood you've messed something up. It works that way even for experienced programmers.
Kevin Barry

thanks for the tips ta0kira.

I know my source code deffinatly works as I made it in an IDE and have compiled it in there, but my assesment says i need to say

"how to compile and evoke the code on the linux command line"

Thats the only problem I'm having :-S

You shouldn't give the .hpp files to the compiler.