On Fri, Oct 28, 2011 at 1:20 PM, Eero Pajarre <epajarre@gmail.com> wrote:
On Fri, Oct 28, 2011 at 6:19 PM, Diederick C. Niehorster
<dcnieho@gmail.com> wrote:
> Dear All,
>
> I've been spurred by the examples provided by John Archdeacon to
> include the possibility to build 64bit version in the Visual Studio
> project files. As a first step, I'm trying this out in Visual Studio
> 2010.
>
I asked about the library naming in August (around 10th).

Martin Payne replied:
----------------
I think the convention in MSVC is to keep the lib file names the same
on both x86 and x64, but to place the x64 libs into an “x64”
subdirectory of your “lib” directory (or “ia64” subdirectory in the
case of Itanium). For the x64 build you just need to add the x64 lib
path under “additional library directories” in the linker config.

I’m not aware of any great advantages of one method over the other,
but it might be a good idea to agree on a convention before we make
any changes to the freeglut headers.
 ------------------

So currently my naming convention is something like
lib/Debug/freeglut.lib
lib/Debug/freeglut_static.lib
lib/Release/freeglut.lib
lib/x64/Debug/freeglut.lib
lib/x64/Release/freeglut.lib

etc

And in compilation I set the library path to correct directory.

 Eero

I'm fond of that kind of layout, as well. As you said, switching between 32- and 64-bit versions then becomes a simple matter of adding the correct architecture directory to the library search path, rather than appending prefixes to file names. Although I think the 32-bit binaries should go in an x86 directory for the sake of consistency.

David