Re: missing eu.a
- Posted by jimcbrown (admin) Aug 16, 2009
- 1384 views
just has a problem with backslashed filenames in some cases depending on the shell used, and callbacks seem to be a problem.
...
maybe just a warning banner in the production releases for -gcc on win32?
What would be optimal is to solve these problems before the next beta release, scheduled for 8/25. Any chance on that happening?
Jeremy
I wasn't aware that there was a problem with callbacks. What is the issue there?
I'm not sure what to do about the backslash problem. Are you saying that 'include std\file.e' fails because of this? Or that open("temp/test.txt", "w") fails? My understanding was that MinGW supported it either way, so MinGW compiled Eu should too. If I am wrong, then the typical way to deal with this is to have a standardize_file_seperator() function which would accept using either backslash or forward slashes as a file seperator and then return either all backslash on watcom or all forward slash on MinGW.
