From: William S F. <ws...@fu...> - 2014-04-22 05:52:04
|
On 10/04/14 11:24, Oliver Buchtala wrote: > Hi, > > On Thu, 10 Apr 2014 09:21:10 +0200, William S Fulton > <ws...@fu...> wrote: > >> Same as mentioned before, are you compiling C code as C++? If so >> Octave has solutions - ignore the enum_forward testcase and document >> the limitations of wrapping C code. Use Swig_cparse_cplusplusout to >> fix nested_struct. >> > > Ok, will 'fix' it. > >> >>> >>> Ahh, and... I pushed the javascript merge candidate to swig@javascript. >> I'm not sure if you noticed, but I committed some changes into the >> javascript branch last week before I got distracted fixing the 3.0.0 >> regressions. I enabled the Travis testing. At least one of the three >> versions of Javascript passed. I think the breakages in the other two >> are the above problem you mentioned. > > Ok, great! > I've been tidying up the branch as I've been reviewing it. There are some things I'm not sure about... When using the v8 and jsc engines, is node required to be installed? configure.ac seems to indicate this atm, but it doesn't seem right. Also is node-gyp required for testing with the v8 and jsc engines? It seems to work without it on Travis. If it isn't needed, do we really need node-gyp for testing node? Oliver, can you sort out the node and v8 Travis builds? There are some failures (although currently I've left it with v8 being skipped because node-gyp is not found - this needs fixing when the answers to the above questions are clear). William |