I apparently need to do this to use dialogs in my programs...but I can't figure out how to link with them. Thanks!

Okay...I'm not sure how to do that...usually I do this:

g++ -s -mwindows -O2 -O3 winwolf.cpp -o winwolf.exe -lalleg

So, I'm guessing I'd stick rsrc.o in between the -o and winwolf.exe? (I'm not going to use resources for winwolf, this is just hypothetical.)

Yup. You put the rsrc.o file in after the -o option but before the .exe option. If I remember right anyway, -o is putting everything together, so adding rsrc.o in after -o is telling the compiler to put that object with the result of winwolf.cpp together into winwolf.exe. I'm not sure that's how it works, given that I haven't used a gcc command line in 2 or 3 years, but I think that's what you need. :}

That's what I said (twice) Here's the relevant bit of my makefile, if it does Oolong any help ...

# main rule; compiles and links everything
$(BINARY) : $(OBJS) rsrc.o 
  $(CXX) -o $(BINARY) $(OBJS) rsrc.o $(FLAGS)

# the rule that handles the resource file/object
rsrc.o : rsrc.rc
  windres rsrc.rc -o rsrc.o

# compiles all .cpp files
%.o : %.cpp *.h
  $(CXX) -o $@ -c $< -gstabs

Okay. This is what I'm gonna do:

//Type my file.cpp!
//Type my filerc.rc!
//Or in the other order...
>windres filerc.rc -o filerc.o

>g++ -s -mwindows -O2 -O3 file.cpp -o file.exe

Now, this is the code I want to use. Can I link with resources in that second commandline? Or do I have to separate the compiler/linker commands?

EDIT: Whoa...you beat me...TWICE!
23: I have <i>NO</i> idea what that stuff means...;D:o

23, show him your generic makefile that automatically generates object targets from every .cpp file in the directory.

Oh, and supplying both -O2 and -O3 on the same commandline seems ... redundant at least.

Carrus: I'm learning the Win API...I thought I would since I now have a windows compiler!

GEEZ! Slow down people!
23: I wanted to give you guys the commandline I'll be using, so you could know how to tell me where to stick filerc.o!

X-G: I know, I was still working on it ... how's it now?

Learning the windows API is ok, just don't corrupt your winwolf project with foreign propretary windows "devils", so no one can test in on linux.