https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • f
    When you compiled hashlink, did you include the sdl dev libs from the SDL2 site? https://github.com/HaxeFoundation/hashlink/tree/master/libs/sdl
  • f
  • f
    I'm asking because i'm about to do that myself and test
  • f
    yes but I'm only halfway certain I did it correctly
  • f
    VS built when I used the download link SDL2-devel-2.24.2-VC.zip on that page
  • f
    and I was able to resolve my other errors with more specific haxelib commands per the convo in #501408700142059520 , leading to a new post-compilation(?) error 
    failed to load library sdl.hdll
  • f
    I'm going to see if reverting to non-git hashlink in conjunction with the other stuff does the trick. I'd prefer to avoid a build-from-scratch approach on critical components anyway if it can be helped
  • f
    so its not seeing the sdl.hdll file, that we know you have on your system.
  • a
    i think crobes provided the material to setup heaps**in #501408700142059520
  • a
    but as this is just about setting up heaps/hashlink might want to move over to #501408700142059520
  • f
    Yeah, once I got that correctly set up with git hlsdl et al I was able to resolve my other issues
  • f
    Thanks all!
  • h
    Nice. So you can the just bind to a property on this component directly the view haxe code without having to go through another class ? Or is only on the view side, as it were ? I was just looking back at a component you helped me with for rendering error messages and seeing how this might affect that has a separate class for dealing with adding classes to style error text and make it visible when necessary
  • b
    well, not really, it just means you can build up a custom haxeui component from just an xml file... doesnt really have anything to do with binding as such
  • h
    Ah ok thx
  • i
    I'm trying to get haxeui-hxwidgets working on Windows (10)... I can get everything to compile, including wxWidgets (static and shared) and the haxeUI sample project itself, but running it gives errors about missing wxWidgets DLLs:
    Copy code
    ---------------------------
Main.exe - System Error
---------------------------
The code execution cannot proceed because wxmsw32u_gl_vc_custom.dll was not found. Reinstalling the program may fix this problem. 
---------------------------
OK   
---------------------------
  • i
    I've built the DLLs and can even find them in explorer, including the one listed as not found, but not sure if haxe is finding them
  • i
    does hxWidgets need 32-bit wxWidgets DLLs compiled?
  • i
    I've tried recompiling wxWidgets from both the x86 and x64 native Developer Tools command prompts, with appropriate 
    CPU=x86
    or 
    x64
    , both with and without 
    SHARED=1
    , all the DLLs have been built, but hxWidgets isn't finding them
  • i
    ok I think it is finding them, it seems to detect the installed version going by the logs
  • i
    on a whim I tried copying the 64-bit wxWidgets DLLs into the program folder, still crashes with this error dialogue after showing a blank command line window:
    Copy code
    ---------------------------
Main.exe - Application Error
---------------------------
The application was unable to start correctly (0xc000007b). Click OK to close the application.
    and attempting to use the 32-bit wxWidgets DLLs just opens a blank command-line window and then closes with no error
  • f
    Ian will more than likely be the man to help you with that.
  • s
    Maybe try putting the DLL files in the same directory as the executable perhaps.
  • s
    Unsure.
  • f
    Curious, try executing it as admin?
  • f
    Try reinstalling your VS C++ runtime packages and then running the exe.
  • f
    Its apparently not a new issue with wxWidgets from all the posts on that error when working with wxWidgets here and there. Seem it usually has to do with a driver preventing Win 10 from running 32bit programs, or needing to reinstall VS C++ runtime packages, or making sure you are using the correct 32bit or 64bit dll's needing (which you apparently have done tried making sure of that). Seems statically linked is a preferred way to go as well.
  • f
    Figured I would do some looking to at least try and help in some way. Knowing what corrects the issue may help me down the road if I play with hxWidgets.
  • f
    Come across this on a ros app build, "For the 32 bit build you may encounter a 0xc000007b error when running rcdiscover-gui.exe. This seems to be caused by a bug in WxWidgets build. As a workaround, rename rcdefs.h in lib\gcc_lib\mswu\wx\msw in your WxWidgets root directory to something different (e.g., rcdefs.h_old). Then, rerun above WxWidgets build command:"
  • f
1...129312941295...1687Latest