HighQuality
|
|
Posted on: May 23, 2011, 04:10:02 am |
|
|
Joined: May 2011
Posts: 1
|
When ENIGMA is launched for the first time it downloads some plugins and then reboots. Every time ENIGMA launches I get this error: Searching for directories between "#include <...> search starts here:" and "End of search list." ERROR: Invalid search diretories returned. Start search string does not match a line. See scrollback for more information. I've followed the installation guide correctly, atleast I think so. This has lead to me being unable to test ENIGMA and I've tried reinstalling it a couple of times. Any help? /HighQuality
|
|
|
Logged
|
|
|
|
Post made May 23, 2011, 09:52:18 am was deleted at the author's request.
|
Josh @ Dreamland
|
|
Reply #2 Posted on: May 23, 2011, 11:36:43 am |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
I said it compiled, not that it worked. I don't have a way to test if it works, and if it keeps erroring for you, I'm afraid to commit it. The Windows version has a high enough tendency to throw compile errors as it is.
The easy fix is just to read the contents of searchdirs.txt yourself and replace the text in Compilers/Windows/gcc.ey with the translation in your default language. But until I have an idea of how to get the Windows locale calls working for everybody, I can't automate it.
Maybe we can fish through the sources to replace macros that are missing with the actual code they represent, but if I recall correctly, Fede, your implementation didn't seem to define one of the most basic macros we needed. Paste your error again next you're on the IRC, and I'll make sure it has no substitute.
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|
Josh @ Dreamland
|
|
Reply #4 Posted on: May 24, 2011, 01:29:49 pm |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
That's an insane hack. I'm not going to assume that bash.exe is a magical program that can make calls ENIGMA.exe cannot.
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|
Post made May 25, 2011, 01:56:57 am was deleted at the author's request.
|
Josh @ Dreamland
|
|
Reply #7 Posted on: May 25, 2011, 11:00:16 am |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
I had already tried setting LC_ALL, and told you it didn't work. That was the very first thing I tried, using Windows' very own SetEnvironmentVariable. ENIGMA isn't its own shell; it doesn't require its own shell. I install Msys exclusively for rm and mkdir.
Making sure that the locale is correct for calls to GCC should be the job of ENIGMA's exec() function. We should not be setting the locale for the entire process, as LGM was designed to use translation files (we just haven't set them up).
The only method I can see us using to fix this, and the only one I see actually working at this point, is using Windows' own locale functions, because that's all that ever works in Windows. Until I can get someone to confirm that doing so works, as opposed to what I've been told so far (it causes compile to fail catastrophically due to ten undefined macros), which, for some reason (maybe ignorance), makes me want to not commit that particular change.
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|