huili2
huili2
@tottaka There should be many successful examples for OpenGL usage online to simply render the YUVI420 input data. I'm not able to provide this here :)
So it has been resolved?
Will close this if no update.
is it still existing in latest version? There should be no issues with default build/link options in CI.
Thanks for the prompt information and verification. For codec operations, it is very effective to do some "non-strict-aliasing" copy as in above MV copy. So this warning type is not...
actually in build/platform-linux.mk, it already has CFLAGS += -fno-strict-aliasing. If there's still something missed, we could consider add this option.
is this issue still existing? In my opinion, it supports visual studio.
> Unfortunately there's no .h file that contains the definitions of the functions that are exported from the DLL. Please refer to codec/api/wels and you can find several header files.
Is there any issues now? The logs are out of date.
Not yet such an API for this. You may do it in the source code according to your requirement.