![]() ![]() different exception handling conventions and, as in this case, different threading models. I didn't have time to investigate and wanted to make it short so I copied the dll and it worked for me.Īh - OK yes, I remember now that some of the mingw64 ports offer different compilation-mode variants, i.e. ISTR that it is a gcc built-in issue so the compiled programs require this dll. IIRC you had to select the *right* compiler option/version/build to get the exception and threads model you wanted. > when I saw this dependency I remembered that I had such issues with different compiler (gcc) "features" (configurations) when I experimented with MinGW-w64. > On, at 08:34, Albrecht Schlosser wrote: I'll try to investigate this on one of my I described the case only as a starting point, and I consider this as a ![]() ![]() So I copied the dll and it worked for me. I didn't have time to investigate and wanted to make it short ISTR that it is a gcc built-in issue so the compiled programs require Option/version/build to get the exception and threads model you wanted. IIRC you had to select the *right* compiler When I saw this dependency I remembered that I had such issues withĭifferent compiler (gcc) "features" (configurations) when I experimented ![]() > expect a mingw build to depend on pthreads, would we? > (6) I also copied the missing file libwinpthread-1.dll to this shared > On Mon, at 16:33, Albrecht Schlosser wrote: Maybe the cross-compiled fluid in yourĬonfiguration can work because you're running under Windows?Īnyway, I hope this is of any value for you and others and helps you to I don't know if it is possible to tweak configure to use a native fluid The missing dll can maybe beĪvoided but I can't help with this right now. Windows 10 system (using explorer to run the executables). Now I could run the built FLTK programs on /path/to/win10/ from the (6) I also copied the missing file libwinpthread-1.dll to this shared (5) I copied *.exe to a shared file system (/path/to/win10/) (4) I used 'make -k' to ignore errors when fluid was used (see above) (3) '-host=x86_64-w64-mingw32' is the host triplet of my installedĬross compiler for windows. (2) LDFLAGS='.' links statically with some system libs (1) `make clean' does "nothing", but generates. Since this was only for a test I ignored this To generate the sources from all test/*.fl files (you need a nativeįluid program to do that). This configuration builds fluid but can obviously not use this fluid.exe $ cp fluid/*.exe test/*.exe /path/to/win10/ $ LDFLAGS='-static-libgcc -static-libstdc++'. I used configure and make with these commands: Virtualbox VM under Windows 10 and I could execute the built programs > and you need to use platform "triplets" to specify the target platform.įYI: I just managed to build FLTK (1.4.0) and many example programs (allĭemo programs that don't use fluid) on my Ubuntu 14.04 system in a You need to tell configure if you want to cross compile, there are extra ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |