<html><head></head><body><div class="ydp64444482yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div><br></div><div dir="ltr" data-setdir="false">Hello Gabriel,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">That was the issue! I assumed that it would look at the current directory first. I'll study the WINEPREFIX you mentioned.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks!</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">...John Alway</div>
</div><div id="yahoo_quoted_1401442071" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, October 11, 2019, 11:22:50 AM CDT, Gabriel Ivăncescu <gabrielopcode@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On 10/11/19 3:51 PM, Thales wrote:<div class="yqt5296172601" id="yqtfd06759"><br clear="none">> Hello everyone,<br clear="none">> <br clear="none">> I'm in experimental mode right now. I'm making changes to wine code to <br clear="none">> see what I can do, but when I run Wine I don't see an effect on Wine, <br clear="none">> even though the compiles are successful. I'm running from the wine <br clear="none">> 64-bit build directory, which I thought would hook into the DLLs, etc. <br clear="none">> in that build tree. Instead, it appears to be using the installed <br clear="none">> version of Wine on my system (Ubuntu, 16.04). According to the <br clear="none">> Codeweavers article I link to below, the build directory is supposed to <br clear="none">> use the newly built code when you run wine or winedbg from it. How do I <br clear="none">> get it to use my newly built code?<br clear="none">> <br clear="none">> <a shape="rect" href="https://www.codeweavers.com/about/blogs/aeikum/2019/1/10/working-on-wine-part-3-using-wine-as-a-developer" target="_blank">https://www.codeweavers.com/about/blogs/aeikum/2019/1/10/working-on-wine-part-3-using-wine-as-a-developer</a><br clear="none">> <br clear="none">> Thanks for any feedback on this!<br clear="none">> <br clear="none">> Regards,<br clear="none">> ...John Alway</div><br clear="none">> <br clear="none"><br clear="none">Hi John,<br clear="none"><br clear="none">You are using ./wine to launch it from its directory instead of just <br clear="none">'wine', right? The latter only looks into the PATH env var, not the <br clear="none">current directory (unlike Windows).<br clear="none"><br clear="none">You can also type the full path to the built wine to launch it, no need <br clear="none">to change directory to the build dir.<br clear="none"><br clear="none">If you have to run a tool from wine (like winecfg) just type <br clear="none">'/path/to/built/wine winecfg'.<br clear="none"><br clear="none">Don't forget to set the WINEPREFIX accordingly else it will mess up with <br clear="none">your default prefix!<div class="yqt5296172601" id="yqtfd89248"><br clear="none"></div></div></div>
</div>
</div></body></html>