BuildBin.dsp revision 491a864b5521d69536451d22b4d9e026d5869509
59879db9d12c2ea10f77b2c44d6d3aba89bb9cb3slive# Microsoft Developer Studio Project File - Name="BuildBin" - Package Owner=<4>
59879db9d12c2ea10f77b2c44d6d3aba89bb9cb3slive# Microsoft Developer Studio Generated Build File, Format Version 6.00
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd# ** DO NOT EDIT **
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd
fd9abdda70912b99b24e3bf1a38f26fde908a74cnd# TARGTYPE "Win32 (x86) External Target" 0x0106
59879db9d12c2ea10f77b2c44d6d3aba89bb9cb3slive
59879db9d12c2ea10f77b2c44d6d3aba89bb9cb3sliveCFG=BuildBin - Win32 Debug
59879db9d12c2ea10f77b2c44d6d3aba89bb9cb3slive!MESSAGE This is not a valid makefile. To build this project using NMAKE,
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE use the Export Makefile command and run
96ad5d81ee4a2cc66a4ae19893efc8aa6d06fae7jailletc!MESSAGE
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE NMAKE /f "BuildBin.mak".
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen!MESSAGE You can specify a configuration when running NMAKE
2e545ce2450a9953665f701bb05350f0d3f26275nd!MESSAGE by defining the macro CFG on the command line. For example:
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen!MESSAGE
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen!MESSAGE NMAKE /f "BuildBin.mak" CFG="BuildBin - Win32 Debug"
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE
00c2cccc28f249fb3b968ddf3e05508595290d40nd!MESSAGE Possible choices for configuration are:
af33a4994ae2ff15bc67d19ff1a7feb906745bf8rbowen!MESSAGE
3f08db06526d6901aa08c110b5bc7dde6bc39905nd!MESSAGE "BuildBin - Win32 Release" (based on "Win32 (x86) External Target")
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE "BuildBin - Win32 Debug" (based on "Win32 (x86) External Target")
5a58787efeb02a1c3f06569d019ad81fd2efa06end!MESSAGE
Error!

 

There was an error!

null

java.lang.NullPointerException