LMTools and potentially Mission Editor updates:
Finding of Compiler Path. Autofind of 2005, 2008 and 2010 compiler "if 2010 can work". Autofind of path on 32bit and 64bit OS.
Verification if Visual C++ 2010 Express can be made to compile missions properly or not.
---- Mission Editor: potential updates. I really don't care to work on the mission editor but maybe just maybe I will find the time to do these below minor alterations.. These are already in the LMTools.
Success/Fail Output check. Blank Line at end check. Punctuation in Mission Name crashes.
I tried using the microsoft visual studio C++ 2010 version a couple of weeks ago.
in the configuration I changed the line from:
C:\program files\microsoft visual studio 9.0\VC\bin
C:\program files\microsoft visual studio 10.0\VC\bin
this is what I found:
When you click 'build mission' the first 2 output windows show as they normally do, however in the 3rd window, there were several 'link errors' and a message stating that it could not locate the objectives file. Your DRL and DSL files are not in the 'missions' folder as a result.
I reverted back to the 2008 version. :)
When I find the time I'll get 2010 and put it on a system I haven't had 2008 on and see what I find. Even if it doesn't work to start, it might be possible to get it working. Won't know until I look at it. Because now that 2010 is out 2008 isn't exactly going to be easy for people to find, so it's going to make things hard for new people to get into it, as well as if someone gets a new system or reloads their system and looses 2008.
I've had litterally no time to do anything since I posted this, totally forgot about this thread even. Well anyways I'l try to remember to look into the 2010 issue.
Are you sure your binaries are in that directory? Maybe VS20010 defaults to another one. Also if you are using a 64-bit OS you have to add a (x86) to the program folder....
gdata;5213331Are you sure your binaries are in that directory? Maybe VS20010 defaults to another one. Also if you are using a 64-bit OS you have to add a (x86) to the program folder....
I tried the 2010 version of C++ on Windows XP, this was before I had installed Vista 64-bit :)