the procedure entry point OleInitialize could not be located in the dynamic link library libglib-2.0.0.dll
Dan Kegel
dank at kegel.com
Mon Nov 11 07:15:02 PST 2013
That looks like a static library. How did you build glib? Did you
build output a glib-2.0.dll ?
On Sun, Nov 10, 2013 at 3:40 PM, Hugo MACHEFER <hugo.machefer at gmail.com> wrote:
> WinLauncher.exe doesn't fail anymore when LINK rather happens with official
> glib.LIB from
> http://win32builder.gnome.org/packages/3.6/glib-dev_2.34.3-1_win32.zip.
>
> So what's wrong with my library: ? GLIB.LIB
> <http://gstreamer-devel.966125.n4.nabble.com/file/n4663218/glib-2.0.lib.GENERATED.SUCCESSFULLY.BY.HUGO>
> here enclosed ?
>
> Knowing that generation of GLIB and GSTREAMER completes well (as DLL), and
> execution using gst-launch (out of webkit) is successful.
>
> -- hmachefe
>
>
>
> --
> View this message in context: http://gstreamer-devel.966125.n4.nabble.com/the-procedure-entry-point-OleInitialize-could-not-be-located-in-the-dynamic-link-library-libglib-2-0l-tp4663215p4663218.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
More information about the gstreamer-devel
mailing list