Update/Fix for World Wind 1.4.0 Imagery and Terrain

[Genericly]

'TesterAlso' is me prior to registering for the forum. Sorry for the duplicate post.

[James_In_Utah]

Regarding building for 64-bit. I don't have a 64-bit OS to test on. I did the build with VS 2005. I'll look to see if I can find any compiler options addressing 64 bit compatibility. If anyone has a suggestions on what to look for that would be appreciated.
James

[Genericly]

James,

Thank you very much for looking into this and helping to keep WW1.4.0 alive and going. Pangloss, maleport, and your efforts are greatly appreciated by me and I'm sure many others. I'd be glad to assist with whatever I can.

To start, here are a couple links to pages that contain information specifically on compiling for 64bit systems and how you might go about doing that.

When compiling C++ code for .net applications (I think we are, correct?), you can use a compiler options of '/clr:safe' to compile an agnostic binary that will run in 64bit and 32bit depending on system that's running it. There are some caveats to this but since the original WW1.4.0 doesn't not contain any special 64bit binaries then there must be a way to compile a single EXE that will correctly run on both architectures.
Source: http://msdn.microsoft.com/en-us/libr...(v=vs.80).aspx (see Compiler support for creating 64-bit applications)
Source: http://msdn.microsoft.com/en-us/libr...(v=vs.80).aspx (see Remarks / Safe and Pure Images)

Additionally, by default, the 64bit compilers are not installed on 32bit system, but you can manually install them.

Goto Add/Remove programs, select Visual Studio, Change, Add/Remove features and add x64 compilers from C++ node. After installing x64 compilers, you should see appropriate options under Platform and shoudl be able to build x64 projects on 32 bit machine.

Source: http://social.msdn.microsoft.com/For...6-f169aff0388d

I don't know how much you changed or added in (by way of dlls), but if it's minimal then the solution may just be a simple recompilation having the 64bit compiler options installed and/or using the /clr:safe agnostic compiler flag turned on.

I don't know but perhaps a simple test would be to compile the vanilla WorldWind 1.4.0 code on your system without any changes to either the code or your VS2005 install, and then test that new EXE on a clean install of WW1.4.0 on a 64bit system just to see if it throws the error. If it does, then take the next step of installing the 64bit compiler additions to VS2005, recompile the vanilla code, and test on 64bit system again. If it throws the error again, then take the next step of adding the /clr:safe compiler flag, recompile the vanilla code, and test yet again on a 64bit system.

If at any point you/we can get the recompiled binary working on a 64bit system then add back your changes to the source code and try the compile again to see if the new binary works on 64bit systems.

I hope this is helpful and not overwhelming. I also hope this doesn't take too much of your time. Thanks again for your help with all of this.

[James_In_Utah]

I'm not sure if my install of VS 2005 can do that. I looked around in the build options and didn't see any reference to that flag. I also tried just typing it in on the additional compiler directive box, which threw a warning saying it was invalid and would be ignored. Maybe we should try to find out who built the official release.

[pangloss]

I don't know if it helps any, but a lot of this was discussed in the IRC channel.

http://worldwindcentral.com/chat/irclog/worldwind/

[James_In_Utah]

That's a lot of monthly log files to search through. Do you remember who did the release build for 1.4?

[m_k]

1.4 was released Feb 2007 (wow! 4 years...), so search afround January, February. And I guess that bull did that release.

[Genericly]

Originally Posted by pangloss

I don't know if it helps any, but a lot of this was discussed in the IRC channel.

http://worldwindcentral.com/chat/irclog/worldwind/

Originally Posted by m_k

1.4 was released Feb 2007 (wow! 4 years...), so search afround January, February. And I guess that bull did that release.

Thank you both for the heads up and direction in where to start. I'm grabbing the logs now and will search them shortly. I'll post back anything useful I can find. Hopefully the solution will be something very simple (e.g. a checkbox that needs checked ).

[James_In_Utah]

The only thing I could find on the build settings page in VS2005 was a choice of x64, x32, or Any CPU. I had it set for Any CPU when I did my build.

[Genericly]

If it's not too time consuming or hard, it might be worth trying to compile specifically for x32 (i.e. x86). Perhaps it's the any-architecture binary that's causing 64bit systems the problem making the system think it can run the binary natively when in fact it cannot. If 64bit systems are forced into using WoW64 then perhaps it will run on those systems (probably at a slower pace than native 32bit system but run nonetheless). Is this something what would be easy to try?