Configure isn't actually a command per se, though it's often mistaken as such. The ./configure is an autotools convention for configuring Makefiles and other related files that tell the compiler how to build a project. Breaking it down into pieces, the ./ tells the shell to look in the current working directory (in your case ~/temp/qc-messenger/) and therefore ./configure is really just telling the shell to look for a file located at ~/temp/qc-messenger/configure and if the file is executable, the shell will run it.
Usually the configure file contains a bunch of bash scripts that examine your system, looking for specific libraries, utilities, applications, etc. and locations of said libraries, utilities, applications, etc. then dumping the results into a Makefile. I say
usually because there are always exceptions, and this particular piece of software may just be one of those exceptions.
Sometimes projects don't use a configure script...they may have a premade Makefile or use other means to configure the software for compilation (scons for example).
So I guess the first step would be just to list all the files in the directory and see if there's a file named configure, and if so see if it's executable by your user. Also, most projects include a README or INSTALL text file that explains the build process and will tell you what to do to get the software installed.
Hope that helps!