itk-wasm icon indicating copy to clipboard operation
itk-wasm copied to clipboard

Unable to run itk-wasm build

Open dereklukacs opened this issue 10 months ago • 3 comments

Hello,

Currently I am having some odd behavior without getting any feedback from itk-wasm.

Version: v1.0.0-b.53, we have been using and building with this version for quite some time. My colleague is able to run and build our scripts with this version and the same version of the codebase.

My problem:

When I run itk-wasm build a web-build folder gets created with a single file itk-wasm-build-env the shell then hangs indefinitely with zero output.

If I terminate this command with ctrl+c then run it again, it finishes immediately but with no output to the terminal. If I remove the web-build folder then run it again the above sequence repeats.

Other information:

  • itk-wasm --help produces help output
  • If I don't have docker running, then I get a "Is the docker daemon running?" error
  • I don't get the docker daemon running error if the web-build folder exists.
  • my intent is to build with emscripten for the web browser
  • I have tried with npm, pnpm, npx, and pnpx commands
  • I have tried running with -s flag and from the exact folder that my CMakeLists.txt is located in.

I tried searching issues but since I'm not getting any output I don't have much to go on.

Any guidance?

dereklukacs avatar Mar 20 '25 19:03 dereklukacs

Hi @dereklukacs ,

It is hard to know what is happening without looking at the code and more details on your build system. I do offer confidential paid support if that is of interest.

In any case, you may find your issue resolved along with better performance and features by updating to the latest version. create-itk-wasm is a good place to start.

thewtex avatar Mar 20 '25 19:03 thewtex

Hey Matt, thanks for your reply. I've shot you an email to discuss direct support on my issue since I agree it is probably isolated to me. I didn't know if it was a common issue or mistake so I posted it here.

I'll ask this publicly as well so others can benefit from the response: What version am I supposed to upgrade to? The API seems to continue to evolve and with each set of changes it breaks our build/app. In order for us to upgrade I believe it will require large rewrites of large parts of our application, so if I do it I want to know that it's an upgrade to a stable version.

dereklukacs avatar Mar 21 '25 16:03 dereklukacs

Thanks @dereklukacs .

The current version is 1.0.0-b.188. We are starting to converge on stability. Not many changes are expected in the API. There are improvements expected to the build system to, for example, support multithreading.

thewtex avatar Mar 21 '25 22:03 thewtex