animate-extension icon indicating copy to clipboard operation
animate-extension copied to clipboard

Can you please release latest build that supports pixi 7?

Open CrazyFlasher opened this issue 2 years ago • 5 comments

I got error when trying to build it

gulp --plugin --install
[16:25:55] +-------------------+
[16:25:55] |    PixiAnimate    |
[16:25:55] +-------------------+
[16:25:55] Mode:  Release
[16:25:55] Using gulpfile C:\work\foxium\animate-extension\gulpfile.js
[16:25:55] Starting 'default'...
[16:25:55] Starting 'plugin'...
[16:25:55] Starting 'plugin-win-debug'...
Error: spawn C:\WINDOWS\Microsoft.NET\Framework64\v4\MSBuild.exe ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn C:\\WINDOWS\\Microsoft.NET\\Framework64\\v4\\MSBuild.exe',
  path: 'C:\\WINDOWS\\Microsoft.NET\\Framework64\\v4\\MSBuild.exe',
  spawnargs: [
    'C:\\work\\foxium\\animate-extension\\project\\win\\pixi-animate-vs2015\\pixi-animate-vs2015.sln',
    '/target:Clean;Build',
    '/verbosity:normal',
    '/toolsversion:4.0',
    '/nologo',
    '/flp:LogFile=Build.log;Append;Verbosity=diagnostic',
    '/maxcpucount',
    '/property:Configuration=Debug'
  ]
}
MSBuild failed!
[16:25:55] 'plugin-win-debug' errored after 25 ms
[16:25:55] Error: spawn C:\WINDOWS\Microsoft.NET\Framework64\v4\MSBuild.exe ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
[16:25:55] 'plugin' errored after 27 ms
[16:25:55] 'default' errored after 29 ms

CrazyFlasher avatar Sep 14 '23 13:09 CrazyFlasher

Btw in release 2.0.4 there is a 2.0.3 version of zxp

CrazyFlasher avatar Sep 14 '23 19:09 CrazyFlasher

Ok, I've installed VS 2015 and now have this error:

gulp --plugin --install
[11:14:57] +-------------------+
[11:14:57] |    PixiAnimate    |
[11:14:57] +-------------------+
[11:14:57] Mode:  Release
[11:14:57] Using gulpfile C:\work\foxium\animate-extension\gulpfile.js
[11:14:57] Starting 'default'...
[11:14:57] Starting 'plugin'...
[11:14:57] Starting 'plugin-win-debug'...
MSBuild failed with code 1!
[11:14:58] 'plugin-win-debug' errored after 1.09 s
[11:14:58] Error: MSBuild failed with code 1!
    at ChildProcess.<anonymous> (C:\work\foxium\animate-extension\node_modules\gulp-msbuild\lib\msbuild-runner.js:97:25)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:552:15)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
[11:14:58] 'plugin' errored after 1.09 s
[11:14:58] 'default' errored after 1.09 s

CrazyFlasher avatar Sep 15 '23 08:09 CrazyFlasher

Are you trying to use the combined output as a standalone animation, or are you integrating the published animations into a larger project? The published files don't care if you are using v6 or v7 of PixiJS, you just need to use the correct release of the runtime library to go with your version of PixiJS.

andrewstart avatar Sep 15 '23 13:09 andrewstart

@andrewstart will it support pixijs v8?

phamtrantriem avatar May 31 '24 07:05 phamtrantriem

At some point. I haven't had time for side projects for a while so I haven't been able to look at v8 much yet. I believe that Graphics had a significant API change, so that will be a big portion of updating this. Hopefully the format of the extension won't change so you'll just need to use the v8 compatible runtime, once it is ready.

andrewstart avatar Jun 02 '24 01:06 andrewstart