public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tom Browder" <tom.browder@gmail.com>
To: "Michael Sullivan" <michael@espersunited.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Undefined References
Date: Sat, 01 Dec 2007 15:27:00 -0000	[thread overview]
Message-ID: <8bc817ee0712010726v7fbba8b0kfa548a547128661d@mail.gmail.com> (raw)
In-Reply-To: <8bc817ee0712010645w6efd39bey1d3b4931e36f1183@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

You're getting the errors about vtable... because you have an
undefined virtual function declared in character.h.

Getting rid of the virtual attribute eliminates those errors and
allows a successful build (and you can eliminate the virtual
destructor).

Then you can concentrate on other problems in the overall program, if any.

I've attached a little cleaner Makefile for your consideration.

-Tom

[-- Attachment #2: Makefile --]
[-- Type: application/octet-stream, Size: 312 bytes --]

CXX=g++

CFLAGS= -W -Wall -pedantic `sdl-config --cflags`

LIBS=`sdl-config --libs` -lSDL_image -lSDL_gfx -lSDL_ttf

OBJS = battle.o character.o

INCS = battle.h character.h

all: battle

battle: $(OBJS)
	$(CXX) -o $@ $(OBJS) $(LIBS)

%.o : %.cpp $(INCS)
	$(CXX) $(CFLAGS) -c $<

clean:
	-rm *.o *~ core* battle

  reply	other threads:[~2007-12-01 15:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01  1:26 Michael Sullivan
2007-12-01  4:01 ` Tom Browder
2007-12-01  4:28   ` Michael Sullivan
2007-12-01  4:43     ` Tom Browder
2007-12-01 11:32       ` Michael Sullivan
2007-12-01 12:22         ` Tom Browder
2007-12-01 12:43           ` Michael Sullivan
2007-12-01 13:09             ` Tom Browder
2007-12-01 13:16               ` Michael Sullivan
2007-12-01 13:23                 ` Brian Dessent
2007-12-01 13:27                   ` Michael Sullivan
2007-12-01 14:22                     ` Tom Browder
2007-12-01 14:28                       ` Michael Sullivan
2007-12-01 14:45                         ` Tom Browder
2007-12-01 15:27                           ` Tom Browder [this message]
2007-12-01 15:34                             ` Michael Sullivan
2007-12-01 15:43                               ` Tom Browder
2007-12-01 15:44                                 ` Tom Browder
2007-12-01 15:49                                   ` Michael Sullivan
2007-12-01 16:01                                     ` Tom Browder
2007-12-02  2:59                                       ` Tom Browder
2007-12-02 11:42                                         ` Undefined References [SOLVED] Michael Sullivan
2007-12-01 17:45                                 ` Undefined References Ted Byers
2007-12-01 13:29                   ` Tom Browder
  -- strict thread matches above, loose matches on Subject: below --
2007-12-01 15:14 J.C. Pizarro
2007-12-01 15:30 ` Tom Browder
2004-04-27 12:21 undefined references Lev Assinovsky
2004-04-27 11:43 gnuml
2004-04-27 12:16 ` Eljay Love-Jensen
     [not found] <B56E6BDB.43%jokada@oceanit.com>
2000-06-15 14:35 ` llewelly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8bc817ee0712010726v7fbba8b0kfa548a547128661d@mail.gmail.com \
    --to=tom.browder@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=michael@espersunited.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).