<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Josh, Ian and Andoni,<br>
<br>
Apologies for the long silence, I had to table this issue for a
while, but I am back now - to finish this once and for all.<br>
<br>
Josh - the use of GST_PLUGIN_PATH_1_0 or GST_PLUGIN_PATH is moot,
isn't it? I mean, sure I'll switch to GST_PLUGIN_PATH_1_0 if the
other is being depricated, but it doesn't really matter in this
context, does it?<br>
<br>
Ian - I think any means to develop for either a 32 or 64 bit release
is game. But why go to the trouble of making a virtual machine when
it's perfectly possible to run both 32 and 64 bit versions on the
same OS? I'm sure the virtual machine could perhaps provide a better
testing platform, but all I aim to do is have them both run. Exact
behavior is less of a concern, currently.<br>
<br>
Andoni - I have both the x86 and x64 versions installed, but I am
still running into a lot of trouble getting the x64 version of my
app using gstreamer to execute properly. Using the dependancy
walker, I've found out that it's still grabbing the DLLs from the 32
bit version of gStreamer :( And I am currently completely at a loss
as to why. I'm literally clueless. My environment variables are as
follows:<br>
<br>
GSTREAMER_1_0_ROOT_X86 - D:\SDKS\gstreamer\1.0\x86<br>
GSTREAMER_1_0_ROOT_X86_64 - D:\SDKS\gstreamer\1.0\x86_64<br>
GST_PLUGIN_PATH - D:\SDKS\gstreamer\1.0\x86\lib<br>
<br>
The PATH variable has nothing in it relating to gStreamer. So
looking at these environment variables I thought 'aha! Obviously
it's the GST_PLUGIN_PATH! I read that a colon separated list was ok,
and tried this:<br>
<br>
D:\SDKS\gstreamer\1.0\x86\lib;D:\SDKS\gstreamer\1.0\x86_64\lib<br>
<br>
I know that's technically semi-colon separated, but no-matter.
Didn't work. Now I've just changed it to the following:<br>
<br>
D:\SDKS\gstreamer\1.0\x86_64\lib<br>
<br>
Same issue. The 64-bit executable still much prefers the 32bit
gestreamer DLLs. I'll come clean and say I have 0 understanding as
to how it currently picks its DLLs. Hopefully some kind soul will
clue me in, because as it stands now, with the changes made, my
32bit exe works great, yet my 64bit version crashes horribly.<br>
<br>
Thanks,<br>
Lasse<br>
<br>
<div class="moz-cite-prefix">On 11-07-2014 23:39, Andoni Morales
wrote:<br>
</div>
<blockquote
cite="mid:CAJNDOgj50UE9O3U1bMHYkUHVjxitQoi0=31qU_dOsBKG=tLBDw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-07-11 9:46 GMT+02:00 Lasse
Laursen <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gazoo@42.dk" target="_blank">gazoo@42.dk</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Dear
GStreamer-devel,<br>
<br>
I've recently found a need to start compiling a 64-bit
version of my GStreamer app. I'd prefer not having to
give up my 32-bit version though, so I set about to have
my cake and eat it too.<br>
<br>
But I'm left with a few questions, to which I may, or
may not already have the answers. I could do with some
input regardless.<br>
<br>
So the two big challenges I see that need resolving are
as follows:<br>
<br>
1. GST_PLUGIN_PATH defined as an environment variable.
This can - of course - only point to either the 32 or 64
bit collection of plug-ins. My assumption is that
plug-ins are also compiled in either a 32 or 64 bit
fashion and should be used with the respective version
of the GStreamer library. An earlier message on this
mailing list indicated that Gstreamer automatically
scans this place:<br>
<br>
DIR/lib/gstreamer-1.0/ where DIR is<br>
<pre>g_win32_get_package_installation_directory_of_module()</pre>
here I'm already a bit curious as whether that changes
the directory it points at if you're running a 64-bit
version of an application dynamically linked with 64-bit
GStreamer...?<br>
<br>
Another helpful user pointed out the option of using
'putenv' to modify the environment variables during
runtime, which would then fairly easily let me point the
GST_PLUGIN_PATH to the right directory.<br>
<br>
2. The PATH environment variable has the same issue -
pointing only to the 32 or 64 binaries. I'm guessing
'putenv' could solve this too, unless someone else has
some other cool and easier ways to fix this?<br>
<br>
------------------<br>
<br>
With both these approaches one thing I worry about it
having to remove the default environment variables, as
using GStreamers executables separately is quite useful
for testing a lot of stuff. But having to continuously
add and remove them is quite the hassle. Apart from
creating a custom batch file that launches a cmd window
and adds these env. variables, I'm also a little at a
loss as to how to solve this...<br>
<br>
Any and all thoughts/comments are welcome. I will test
this soon, but I am keen to hear existing experience!<br>
</div>
</blockquote>
<div><br>
</div>
<div>Hi Lasse, <br>
<br>
</div>
<div>On Windows GStreamer can be installed in parallel for
both architectures and you can work with both archs
without having to do anything else on your side.<br>
Your x64 application will link against the gstreamer
library in c:\gstreamer\1.0\x86_64\bin and therefore loads
deps and plugins from this prefix, while the x86 one will
link against the gstreamer library in
c:\gstreamer\1.0\x86\bin and use this different prefix.<br>
</div>
<div>And in case you need to set PATH the installer adds 2
env variables that you can use GSTREAMER_1_0_ROOT_X86 and
GSTREAMER_1_0_ROOT_X86_64<br>
<br>
</div>
<div>Cheers,<br>
Andoni<br>
</div>
<div><br>
</div>
<div>Cheers,<br>
Andoni<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
Regards,<br>
Lasse<span class=""><font color="#888888"><br>
<br>
<div>-- <br>
Lasse Farnung Laursen<br>
Post.doc at the University of Tokyo<br>
<a moz-do-not-send="true"
href="http://www.lasselaursen.com"
target="_blank">www.lasselaursen.com</a><br>
FB: <a moz-do-not-send="true"
href="https://www.facebook.com/lasse.laursen"
target="_blank">lasse.laursen </a><br>
Twitter: <a moz-do-not-send="true"
href="https://twitter.com/PMP_J" target="_blank">@PMP_J</a></div>
</font></span></div>
<br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<a moz-do-not-send="true"
href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Andoni Morales Alastruey<br>
<br>
LongoMatch:The Digital Coach<br>
<a moz-do-not-send="true"
href="http://www.longomatch.ylatuya.es">http://www.longomatch.ylatuya.es</a>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Lasse Farnung Laursen<br>
Post.doc at the University of Tokyo<br>
<a href="http://www.lasselaursen.com">www.lasselaursen.com</a><br>
FB: <a href="https://www.facebook.com/lasse.laursen">lasse.laursen
</a><br>
Twitter: <a href="https://twitter.com/PMP_J">@PMP_J</a></div>
</body>
</html>