g said, there is no reason that we need to use the same build
system -- we could easily have custom build scripts for a project, and
still have it share the dependencies.
I was planning on getting it all further along before announcing the
project and looking for help, but since is came up...
-Ch
able hinting:
> • uncomment: #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
> • perhaps comment out: #define
> TT_CONFIG_OPTION_UNPATENTED_HINTING
handy to know.
Thanks,
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(20
aren't the best solutions for everyone.
Chris
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the m
On Mar 13, 2015, at 12:50 PM, Cyrille Rossant wrote:
> Exactly. Note that pushing data on the GPU is not that slow:
No -- and something has to be pushed to the video card at some point anyway.
But my experience is that if you need to push the data to the CPU,
that pretty much overwhelms the adv
MPL does not have a backend that used “real” GPU rendering.
And it’s very hard to make one, due to the really low level nature of
OpenGL and similar APIs, and MPL’s rendering model.
You might try VisPy — it was designed for OpenGL from the start.
-CHB
Sent from my iPhone
On Jul 5, 2018, at 5:
101 - 105 of 105 matches
Mail list logo
