Hi Guys,
First try at a compile with my new $699 Pro license after being away for a while.
If I compile the app and run it on the same machine it runs fine.
It is complied for WINDOWS / 64 BIT / Stand Alone / Web
If I move the compiled app and the 2 folders LIBS and Resources to my LIVE environment I start getting requests for DLL’s
msvcr120.dll and then something about xojoFrameworkSomething.dll and gave up.
the DEV machine is exactly the same hardware and windows 7 as the live machine.
32 bit works well.
compiles in about 20 seconds which is easily half the normal compile time.
The app itself seems to run a bit faster and looks a bit cleaner which I would hope after a year of development.
Does the compiled app run on your developemnt computer? if so, you are missing libraries on the target host.
If it does not run on the development computer, take a look at the windows application event logs (mycomputer/manage) and see what error comes out. That may indicate what the issue is (like a call to a 32-bit library, for example) Next, put your own logging code in the app to see where it runs and where it fails.
if you use a folder for the build you will see a whole heap of other DLL’s
why aren’t they all in the one folder?
I expect you have to copy all the DLL’s to the root of the other machines structure as well.
Next question - Why does the build for 64 bits take SOOOOOO long.
I mean its like 10 minutes.[/quote]
You must leave all of the dlls where you find them. We’re building a new binary format for Windows now and this is what Microsoft expects.
The new compiler (LLVM) does a lot of optimization so things are a little slower to build. That said, the code that benefits the most is math-intensive. The biggest benefit most users will see is the increased memory footprint.