Is Tuttle continuous integration build for Windows x32 or x64?

[kevi...@insightdigital.org]

Launching 'sam.bat', I receive the Windows 'application cannot start correctly 0xc00007b' error, which usually indicates an x32/x64 mismatch.  In this case, though, I *believe* that both python and Tuttle are x32.

- My working 32-bit Python is on an x-64 Windows 8.1 machine

- I downloaded the 'production' Windows binaries from http://www.tuttleofx.org/download, which I deduce should be x32 as the x64 option in the download matrix is greyed out

- I found I had to add 'C:\Windows\SysWOW64' to Windows path (location for x32 DLLs)

Has anyone else run into this?

For additional information, I edited 'sam.bat' as follows:

@echo off

REM you can set here your PYTHONHOME (if you haven't one already defined for example).

REM Setting Pythonhome causes trouble

REM See:  https://groups.google.com/forum/#!topic/tuttleofx-user/deZg7AKU8SU

set PYTHONHOME=c:\Python27

ECHO var = %PYTHONHOME%

set PYTHONPATH=c:\Python27\Lib

ECHO var = %PYTHONPATH%

REM set Path=%PYTHONHOME%;%Path%

set PATH=%PYTHONHOME%;%PATH%

REM ECHO var = %Path%

set TUTTLE_ROOT=%~dp0

ECHO var = %TUTTLE_ROOT%

set TUTTLE_HOME=%UserProfile%\cache_tuttleofxRelease

if not exist %TUTTLE_HOME% mkdir %TUTTLE_HOME%

ECHO var = %TUTTLE_HOME%

REM python.exe "%TUTTLE_ROOT%/sam.py" %*

C:\Python27\python.exe "%TUTTLE_ROOT%/sam.py" %*

[Clément Champetier]

Hello,

Actually, the windows release you get from http://www.tuttleofx.org/download is for x64 system (build production). The left of the "download matrix" is for x32, and the right is for x64 (with for each production/release/debug builds). But i agree with you, the download page (http://www.tuttleofx.org/download) can be a bit confusing...

Is this help you ?

[kevi...@insightdigital.org]

Many thanks, Clément,

This makes sense now that you mention it -- I was being too literal.

I downloaded python x64 and have no trouble running x32 and x64 side-by-side.  (I actually can't quite believe that it's 2015 and we're still dealing with the x32/x64 bifurcation in Windows.)

I can now invoke SAM from the command line with this slightly edited 'sam.bat', below:

@echo off

REM you can set here your PYTHONHOME (if you haven't one already defined for example).

REM Setting Pythonhome sometimes causes trouble

REM See:  https://groups.google.com/forum/#!topic/tuttleofx-user/deZg7AKU8SU

set PYTHONHOME=c:\Python27_x64

ECHO var = %PYTHONHOME%

set PYTHONPATH=c:\Python27_x64\Lib

ECHO var = %PYTHONPATH%

set PATH=%PYTHONHOME%;%PATH%

REM ECHO var = %Path%

set TUTTLE_ROOT=%~dp0

ECHO var = %TUTTLE_ROOT%

set TUTTLE_HOME=%UserProfile%\cache_tuttleofxRelease

if not exist %TUTTLE_HOME% mkdir %TUTTLE_HOME%

ECHO var = %TUTTLE_HOME%

python.exe "%TUTTLE_ROOT%/sam.py" %*

[Clément Champetier]

Glad to hear that!

Feel free to contribute if you find any problems on Windows.

And don't hesitate to contact us if you build the project on Windows with latest version (the team usually works on linux...).