Comments (7)
I would like to know if there is someone who has ever built OpenSSL-1.0.2 on the current Windows ARM.
I have raspberry pi2 but never installed Windows 10 IOT. Building OpenSSL needs perl and I'm not sure that if it is provided for Win ARM.
Another issue is that the current no-asm configuration of openssl in node is made based on Linux. We have to check if there are some additional sources or defines needed to work on Windows.
from node.
I would like to know if there is someone who has ever built OpenSSL-1.0.2 on the current Windows ARM.
I have raspberry pi2 but never installed Windows 10 IOT. Building OpenSSL needs perl and I'm not sure that if it is provided for Win ARM.
We never built it on Windows ARM. We use Visual Studio to build and there is no Visual Studio on ARM. Instead we cross-build ARM on x86/x64 hosts.
Another issue is that the current no-asm configuration of openssl in node is made based on Linux. We have to check if there are some additional sources or defines needed to work on Windows.
Do you have specific concerns for this? Are the functionalities covered by unit tests? We have been using the current no-asm configuration for Windows ARM and it builds/runs.
from node.
@shigeki Could you please elaborate on the original WIN_CE
configuration comment? As I understand WIN_CE
is an outdated platform. Is OpenSSL dep or node.js ever built for WIN_CE
, why do you want to add it now?
from node.
@jianchun Yes, WIN_CE is very old platform and OpenSSL has not been maintaining it for a long time. I just commented about WIN_CE because https://github.com/nodejs/node-chakracore/blob/chakracore-master/deps/openssl/openssl/INSTALL.WCE indicates how to build openssl on Windows ARM and I'd like to know if it still work on the current Windows ARM with generating asm files. The current Node-Chakra is built on openssl with no asm support so that high performance of tls and crypto module is not expected.
On ARM, tls and crypto would cost much more because of its low cpu performance. I think that the asm support will be required in the future.
Do you have specific concerns for this? Are the functionalities covered by unit tests? We have been using the current no-asm configuration for Windows ARM and it builds/runs.
The current Node only use a part of functionalities of openssl and tests does not cover all inputs parameters so there is no surprise to pass all unit tests.
For define parameters, you can see the list of https://github.com/nodejs/node-chakracore/blob/chakracore-master/deps/openssl/doc/openssl_define_list.pdf and found that there are some differences between Linux and Win. For sources of no-asm build, it is defined in https://github.com/nodejs/node-chakracore/blob/chakracore-master/deps/openssl/openssl.gypi#L638-L653. I made its list from Linux build but I do not know if they are the same ones as Windows build with no-asm.
from node.
Windows CE uses ARM, but WoA uses Thumb mode
By the way, I have a native compiler on my WoA machine(cross-compiled Clang). An official MS build of Perl exists
from node.
An cross-compiled Clang runs relatively well, and works fine(even with MSBuild)
from node.
Windows CE support is not on our roadmap.
from node.
Related Issues (20)
- Building fails HOT 2
- SharedArrayBuffers can cause crashes when inspected in certain ways HOT 3
- `test-dgram-*` test failures on macOS
- Problems while building against node-chakracore master
- Wire up `resourceNameToUrl` support in inspector
- node-gyp errors installing `npm i sleep` with [email protected] and [email protected]
- Problems installing `npm i sleep` with node-chakracore 10.13.0. HOT 3
- Is this project affected by Edge’s move to Chromium? HOT 2
- --v8-options not working HOT 3
- Failed unit tests running node-ChakraCore on Windows IoT
- Issues with N-API Addon and TTD
- ttdReplayDebugUri not initialised
- TTD does not initialize properly HOT 1
- Need support for the 3 dots operator to install tensorflow/tfjs-node HOT 2
- Upgrade to node v8 7.4 which support JIT-less
- azure-sdk-js setup hits Error: The command failed with exit code 1
- napi: napi version doesn't been exposed through process.versions
- Build fails, "error: ‘vector’ in namespace ‘std’ does not name a template type" etc HOT 2
- ContextShim is leaking
- Current Status? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node.