1. EU4.1 Struct Branch eubw.exe missing
- Posted by andi49 Jan 30, 2013
- 1864 views
Hallo
i compiled Eu 4.1 Struct branch
Euphoria Interpreter v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2013-01-25 11:16:28, Id: 5966:2674457e63b8
euiw.exe seems to work stable (as far as i can test it).
But eubw.exe is not build, and why is the interpreter using System Memory? Not Managed Menory. And what is the difference (what does it mean to my program?)
Thank you
Andreas
2. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by jimcbrown (admin) Jan 30, 2013
- 1845 views
Hallo
i compiled Eu 4.1 Struct branch
Euphoria Interpreter v4.1.0 development 32-bit Windows, Using System Memory Revision Date: 2013-01-25 11:16:28, Id: 5966:2674457e63b8
euiw.exe seems to work stable (as far as i can test it).
But eubw.exe is not build,
There was a fix that went in recently for this, here http://scm.openeuphoria.org/hg/euphoria/rev/92453e0aa709
But it doesn't appear to have gone into the struct branch yet. You'll need to apply the patch manually.
and why is the interpreter using System Memory? Not Managed Menory.
That's just the default setting. You can change it with an option to ./configure
And what is the difference (what does it mean to my program?)
Thank you
Andreas
Managed Memory caches memory allocations (using its own memory management system on top of the System), while System Memory just use the System (so memory allocated goes directly to the System, and memory freed is immediately returned to the system).
Managed Memory results in a small speedup compared to using System Memory.
3. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by andi49 Jan 30, 2013
- 1842 views
Hallo
thank you for your fast reply.
I will give it a try tomorrow.
The Struct branch seems to be very interresting. Is there a chance it will go to default?
i just read some docs about memstructs (btw creating the docs, i got some errors i had to comment out some files (like windows.e) maybe creole does not like the dot notation.
If i understnad this correct, is it true if i write a wrapper for a, say Win32api function, using memstructs. This wrapper will work also on win64? Mean all calculations for Pointer and Handles are done automaticly?
If this is true, this would be a great improvement.
Andreas
4. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by mattlewis (admin) Jan 30, 2013
- 1897 views
The Struct branch seems to be very interresting. Is there a chance it will go to default?
Yes, that is the goal.
i just read some docs about memstructs (btw creating the docs, i got some errors i had to comment out some files (like windows.e) maybe creole does not like the dot notation.
If you have an up to date eudoc / creole, it should work.
If i understnad this correct, is it true if i write a wrapper for a, say Win32api function, using memstructs. This wrapper will work also on win64? Mean all calculations for Pointer and Handles are done automaticly?
If this is true, this would be a great improvement.
Yes. In fact, I've been working on converting Win32Lib to using memstructs so that it will work on Win64. The code is in a mercurial repository on the Win32Lib Sourceforge project. I've also been working on converting the IDE. That code is on bitbucket.
Matt
5. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by andi49 Feb 16, 2013
- 1795 views
i just read some docs about memstructs (btw creating the docs, i got some errors i had to comment out some files (like windows.e) maybe creole does not like the dot notation.
If you have an up to date eudoc / creole, it should work.
Matt
Sorry for the late respond, but upgrading to win8 took more time than i planed. I downloaded the last version of eudoc using hg, but it doesn't work for "make htmldocs". So where is this recent version to download?
I was able to build a 32-bit version of eu4.1 but if failed to compile a 64-bit version. Maybe it is a problem with my setup. i try to use tdm-gcc . It gives the option that it works out of the box (without starting a msys session in a msys terminal). Works really nice for 32 Bits now. Andreas
6. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by mattlewis (admin) Feb 19, 2013
- 1732 views
Sorry for the late respond, but upgrading to win8 took more time than i planed. I downloaded the last version of eudoc using hg, but it doesn't work for "make htmldocs". So where is this recent version to download?
The latest version in hg is the version to use. What did it do?
I was able to build a 32-bit version of eu4.1 but if failed to compile a 64-bit version. Maybe it is a problem with my setup. i try to use tdm-gcc . It gives the option that it works out of the box (without starting a msys session in a msys terminal). Works really nice for 32 Bits now.
In order to build a 64-bit version, you need to translate with a 4.1 interpreter (running the translator) or translator. A 4.0 translator won't handle things correctly. Could you give some more details about what happened or what didn't work?
Matt
7. Re: EU4.1 Struct Branch eubw.exe missing
- Posted by andi49 Mar 08, 2013
- 1602 views
Hi
after a while i found some sparetime to work with Euphoria.
In order to build a 64-bit version, you need to translate with a 4.1 interpreter (running the translator) or translator. A 4.0 translator won't handle things correctly. Could you give some more details about what happened or what didn't work?
Matt
I found the problem on my System. There was a missing semicolon in the PATH. Same place on two machines one with WIn XP the other win Win 8.
C:\Windows\System32\Wbemc:\euphoria...;c:\Mingw32...
The c:\euphoria PATH points to Euphoria3. I really do not know what this Wbem is good for. But it seems i don't really needed these entrys :)
Okay, what happend was that the Windows cmd just ignores the faulty entry and steps over it to the next entry in the PATH. A euc.exe built with Watcom behaves the same way, but a euc.exe built with gcc stopped searching the PATH at the point of the faulty entry (missing semicolon).
This means i was able to built a 32bit 4.1 with gcc, but only with a 4.0.x built with Watcom.
The resulting 4.1 (also 4.0.x built with gcc) just didn't find gcc on the PATH.
But, okay fixed. I'am was able to built a 64bit Version now.
Euphoria Interpreter v4.1.0 development 64-bit Windows, Using System Memory Revision Date: 2013-03-05 22:42:31, Id: 6025:b526e962eb61 ERROR: Must specify the file to be interpreted on the command line
But i was not able to run any of the demos with this interpreter. Nothing happend, no console output, no ex.err. eui.exe or euiw.exe seems to run and then return to the command prompt.
The interpreter seems at least basicly to work, i was able to run a program like this.
puts(1,"Hallo Welt")
I played a little with some of the demos and find out that there is maybe a problem with std/console.e and std/io.e, or maybe the underlying functions.
The output of my little Hello World program disapears if i include one of these. Even when no function is used.
And, yes i tried one of the nightlybuilts, with the same result. This one:
Euphoria Interpreter v4.1.0 development 64-bit Windows, Using System Memory Revision Date: 2013-02-15 14:10:08, Id: 5984:1a35013eb40e ERROR: Must specify the file to be interpreted on the command line
I'am using Win 8 Pro 64bit. The 32bit 4.1 seems to work.
Andreas
Edit:
I tried to use gdb (first time, so I'am not really sure what I'am doing ;)
C:\e64>gdb --args c:\e64\bin\eui.exe "c:\e64\demo\ascii.ex" GNU gdb (GDB) 7.5 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-w64-mingw32". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from c:\e64\bin\eui.exe...done. (gdb) start Temporary breakpoint 1 at 0x5c4be0: file c:/crossdev/src/mingw-w64-svn/mingw-w64 -crt/crt/crt0_c.c, line 17. Starting program: c:\e64\bin\eui.exe c:\e64\demo\ascii.ex [New Thread 3180.0xd04] Temporary breakpoint 1, main (flags=2, cmdline=0x361560, inst=0x361ab0) at c:/crossdev/src/mingw-w64-svn/mingw-w64-crt/crt/crt0_c.c:17 17 c:/crossdev/src/mingw-w64-svn/mingw-w64-crt/crt/crt0_c.c: No such file o r directory. (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x000000000054cc62 in _62my_sscanf () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x000000000054cc62 in _62my_sscanf () (gdb) cont Continuing. [Inferior 1 (process 3180) exited with code 0377] (gdb)
Forked into: Eu4.1 64Bit on Win8 not working