Closed airportyh closed 11 years ago
yeah, it doesn't work with the new node yet. I need to spend some time hacking this soon.
What version of node should we be using?
For anyone else looking it seems Chimera works with node up to version 0.8.23. Also Chimera does not work well with passport.js when using express. From my testing so far to prevent from getting a segmentation fault you must include Chimera prior to the initialization of passport with the following commands within app.configure
app.use(passport.initialize()); app.use(passport.session());
For me to get around the segmentation fault thus far I have simply added the
var Chimera = require('chimera').Chimera;
at the top of the app.js file then simply pass it to any file needing it. I have yet to run into an issue this way although im sure it is not a complete fix.
The same error occured on my mac 10.9 mavericks, node versions:
{ http_parser: '1.0',
node: '0.10.5',
v8: '3.14.5.8',
ares: '1.9.0-DEV',
uv: '0.10.5',
zlib: '1.2.3',
modules: '11',
openssl: '1.0.1e' }
It seems that node_modules/chimera/lib/chimera.node
loaded error.
@deanmao Has there been any progress on this in the last 5 months? Is it a non-trivial update?
It's working over here, but you have to build from source unfortunately. Qt updated their license which prevents static linking for webkit which is why one has to build from source. You can hack their makefile to make it build statically, but I'm guessing they disabled it due to associated licenses on webkit. I've been using it for the past 5 months so "it works for me :-)"
So node-chimera can't be installed as a module anymore?
Minimal code
Output
Debugged into it to get more detailed error when trying to load native lib