python x86 does not run with win x64

[maybeec]

We currently follow the approach to distribute software packages in x86 architecture to not break backward compatibility to those, who did not upgrade to x64.
Unfortunately, this does not work with python. We need python 2.7 for OASP4JS npm setup to work properly. But the currently distributed x86 version does not work on win x64.

We have two options:

1. distributing both x86 and x64 and provide a switch script to enable x86 software packages and vice versa.
2. do not distributing python and treat it as a precondition for working with the OASP4JS.

[tbialecki]

Why OASP4js needs Python ?

Tomasz

2015-08-26 10:16 GMT+02:00 Malte Brunnlieb [email protected]:

We currently follow the approach to distribute software packages in x86
architecture to not break backward compatibility to those, who did not
upgrade to x64.
Unfortunately, this does not work with python. We need python 2.7 for
OASP4JS npm setup to work properly. But the currently distributed x86
version does not work on win x64.

We have two options:

1. distributing both x86 and x64 and provide a switch script to enable
   x86 software packages and vice versa.
2. do not distributing python and treat it as a precondition for
   working with the OASP4JS.

—
Reply to this email directly or view it on GitHub
#72.

[maybeec]

During npm install, there are package, which need to be rebuilt by using python. Otherwise, you will see a lot errors on your console as python could not be started successfully.
Nevertheless, overall npm install seems to terminate without any complains and you can do a gulp serve afterwards.

I had a look at this issue as in the latest trainings, we have seen a lot npm install problems and I want to get rid of at least the ones, I can reproduce.

[tbialecki]

Errors are being produced because some optional dependencies failed(please
analyse the log) which are need for spritemesh mechanism - but it is still
ok.

2015-08-26 11:01 GMT+02:00 Malte Brunnlieb [email protected]:

During npm install, there are package, which need to be rebuilt by using
python. Otherwise, you will see a lot errors on your console as python
could not be started successfully.
Nevertheless, overall npm install seems to terminate without any complains
and you can do a gulp serve afterwards.

I had a look at this issue as in the latest trainings, we have seen a lot
npm install problems and I want to get rid of at least the ones, I can
reproduce.

—
Reply to this email directly or view it on GitHub
#72 (comment).

[maybeec]

yes, as I said. It is still ok.
Nevertheless, it indicates, that python x86 is not running on x64.
Thus, we should consider providing a working solution or none. OASP4JS is just the context, where we can benefit from having a working solution as it might not confuse users while building OASP4JS. Nobody, who gets in contact with OASP4JS the first time, knows, which errors are ok, and which are not.