OpenEuphoria

2. Re: Euphoria Wrapper Problem

• Posted by jimcbrown (admin) Jun 03, 2015
• 1908 views

Try modifying your wrapper like this:

--Wrapper code 
if ttf = 0 then 
	puts(2, "Load of Library ttf failed!\n") 
end if 
public constant xTTF_Init = define_c_func(ttf,"TTF_Init",{},C_INT) 
if xTTF_Init = 0 then 
	puts(2, "Load of function TTF_Init failed!\n") 
end if 
 
public function TTF_Init() 
 
 return c_func(xTTF_Init,{}) 
	 
end function 

And let us know what the output is.

4. Re: Euphoria Wrapper Problem

• Posted by petelomax Jun 03, 2015
• 1938 views

	puts(2,"Failed to open SDL2_tff.dll!\n") 

I would run procmon and see where it was trying to load that dll from, and what errors it got. Be warned it may collect thousands if not hundreds of thousands of events, so first make sure you are ready to have it fail, then start procmon and click OK to start capturing events, run your app and immediately switch back to procmon and stop capture (third icon, looks like a cotton wool toffee apple). Then use right click menus to exclude what you safely can, especially anything from your browser/av/svchost/lsass/taskhost/services/csrss/conhost/DllHost/etc. Another possibly easier way to set filters is start capture and exclude (by Process Name) everything that appears before you run your app, which you start once you've got procmon down to a blank screen. Either way it is far easier the second time you use procmon, as it remembers all your filters. One word of warning: if you leave capture running your pc will grind to a halt before very long, so always turn it off as soon as you can.

if that did not solve I would try dependency walker and see what that said.

Pete

6. Re: Euphoria Wrapper Problem

• Posted by petelomax Jun 03, 2015
• 1868 views

My only gripe is it ain't so hot when analyzing a 32bit dll on a 64bit OS, or at least wasn't the last time I looked. It will behave itself after I've messed about with the directory orders, though.

Pete

8. Re: Euphoria Wrapper Problem

• Posted by petelomax Jun 04, 2015
• 1836 views

Can you quickly confirm there is no "Error: Modules with different CPU types were found"?

Taking two that I know are absolutely fine:

If I load C:\Windows\system32\kernel32.dll (the 64 bit one), it is fine.

If I load C:\Windows\syswow64\kernel32.dll (the 32 bit one), I get errors, until I select Options/Configure Module Search Order, and move syswow64 above system32.

That's with the latest 64-bit version 2.2, if I try the 32-bit version it quietly ignores several 32/64 bit errors.

If you like, select File/Save As, change the drop-down to .txt, and post the resulting file here.

Pete

10. Re: Euphoria Wrapper Problem

• Posted by petelomax Jun 04, 2015
• 1847 views

I've tried that, also on 64-bit Windows 7, but the 32-bit version quietly ignores 32/64 bit errors, that you can see if you look carefully enough. To be fair, if it reports no errors when it is actually looking in error at a few 64-bit dlls, it probably means everything is OK, but I would still have to recommend tweaking the Directory Search Order until it is loading all the right (32-bit) ones, and there is less scope for error if you stick to the 64-bit one when your OS supports it.

As a quick example (using 32-bit dependency walker on a 64-bit OS):

 
[   ] c:\windows\syswow64\KERNEL32.DLL 
     [   ] c:\windows\syswow64\API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL 
     [   ] c:\windows\system32\NTDLL.DLL 
     [   ] c:\windows\system32\KERNELBASE.DLL 

Pete