-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added recipe for fftw3 #317
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks to me like a good recipe for FFTW3, thank you!
I'm happy to merge, but be aware that from my limited testing so far, it looks like the ravetools
package still won't be able to build under Wasm yet even, with the FFTW3 library available for Wasm. There is still lots of work to be done on our side for this to work really well.
Two of the things that do not currently work well under wasm are handling R packages that use configure
scripts (a specific test for cross-compiling fails) and handling R packages that use threads. Unfortunately, that package uses both.
With a little bit more digging into the build, I found that Currently export PKG_CONFIG_PATH=/opt/webr/wasm/lib/pkgconfig Any advice? : ) |
The I have been able to compile your package ( So, I will merge the change. After a few hours, once CI has finished, a new webR Docker image will be uploaded, and once that has filtered through to r-universe I expect that your package will be able to build. Local log output:
|
The ravetools wasm binaries are now available for public: https://rave-ieeg.r-universe.dev/ravetools |
Trying to resolve r-universe-org/help#321