OpenEuphoria

1. Obsolete EUDIR!

• Posted by jimcbrown (admin) Nov 29, 2012
• 5298 views

Forked from Re: Building eu40.4 question

Yes, but the issue in the previous thread isn't one of them.

The environment variable EUDIR has been obsolete for a long time now. Can you enumerate the problems that EUDIR works around, so they can acutally get fixed?

3. Re: Obsolete EUDIR!

• Posted by SDPringle Nov 29, 2012
• 5306 views

If you don't install to one of the hard coded directory locations, you don't use the eudir option with configure, and you don't set EUDIR, the build wont work with Watcom. I've just tried it, prompted by the post I saw. I don't have time to enumerate all of the problems. I set EUDIR appropriately. The debate is over, those who voted against setting EUDIR in the installer can do the enumerating.

Shawn

5. Re: Obsolete EUDIR!

• Posted by DerekParnell (admin) Nov 29, 2012
• 5273 views

I don't have EUDIR set either and I'm not having any problems. What am I doing wrong?

7. Re: Obsolete EUDIR!

• Posted by SDPringle Nov 30, 2012
• 5167 views

Okay here is my environment setup:

C:\Users\Shawn>echo %EUDIR% 
C:\Program Files\Euphoria\4.0.5 
 
C:\Users\Shawn> 
 
C:\Users\Shawn>echo %E0T% 
c:\Users\Shawn\Documents\development\hg\4.0 
 
C:\Users\Shawn> 

C:\Users\Shawn>cd %E0T%\source 
 
c:\Users\Shawn\Documents\development\hg\4.0\source> 

I can make all with this setup using Watcom make. I have to use the MINGW shell to make with MINGW gcc. I assume this is normal.

Now, I'll do:

 
c:\Users\Shawn\Documents\development\hg\4.0\source>copy config.wat standard.wat 
        1 file(s) copied. 
 
c:\Users\Shawn\Documents\development\hg\4.0\source>set EUDIR= 
 
c:\Users\Shawn\Documents\development\hg\4.0\source>configure --build ..\build\noEUDIR 
        1 file(s) copied. 
        1 file(s) copied. 
        1 file(s) copied. 
        1 file(s) copied. 
Build directory is ..\build\noEUDIR 
c:\Users\Shawn\Documents\development\hg\4.0\source>wmake source 

One of the errors I receive is:

Error(E14): Cannot execute ("C:\euphoria\bin\eui.exe"): No such file or directory 

The Makefile makes a guess and if all of you are installing to C:\EUPHORIA, then everything will be fine. But the installer allows the user to choose to install to any location.

c:\Users\Shawn\Documents\development\hg\4.0\source>hg sta 
? bin\echoversion.exe 
? bin\mkver.exe 
? source\eu.cfg 
? source\standard.wat 
? tests\ctc.log 
? tests\exported_from_memory.txt 
? tests\exported_from_safe.txt 
? tests\publicized_from_memory.txt 
? tests\publicized_from_safe.txt 
? tests\serialize.dat 
? tests\t_declasgn_wrning-bound.exe 
? tests\t_hash-bound.exe 
? tests\t_override-bound.exe 
? tests\t_rand-bound.exe 
? tests\unittest.log 
 
c:\Users\Shawn\Documents\development\hg\4.0\source>hg summary 
parent: 5741:362497032f33 tip 
 * updated release date in ../4.0.5.txt and the debian change log to October 19th. 
branch: 4.0 
commit: 15 unknown (clean) 
update: (current) 

Now, using the MINGW bash shell:

$ echo $EUDIR 
C:\Program Files\Euphoria\4.0.5 
 
Shawn@Joy-PC /home/shawn/Documents/development/hg/4.0/source 
$ unset EUDIR 
 
Shawn@Joy-PC /home/shawn/Documents/development/hg/4.0/source 
$ echo $EUDIR 
 
 
Shawn@Joy-PC /home/shawn/Documents/development/hg/4.0/source 
$ configure --build ../build/noEUDIR 
Configuring to build for target: WINDOWS / default platform 
Writing eu.cfg to C:/Users/Shawn/Documents/development/hg/4.0/build/noEUDIR/eu.cfg 
 
Shawn@Joy-PC /home/shawn/Documents/development/hg/4.0/source 
$ make source 

This results in code translating and compiling without any problem apparently. So, what is different? The Watcom makefiles try to use EUDIR and if it cannot find it, it assumes C:\EUPHORIA. Look also at Makefile.wat in the creole distribution. It also uses EUDIR. Any thing designed in the 3.1 era including our Makefiles use EUDIR.

There is code in EUPHORIA for guessing certain paths. So, if you really want to see how robust this is, remove EUPHORIA from the paths found in source/common.e, and install to something not listed there.

9. Re: Obsolete EUDIR!

• Posted by jimcbrown (admin) Nov 30, 2012
• 5130 views

So we do have a real bug!

11. Re: Obsolete EUDIR!

• Posted by K_D_R Feb 01, 2013
• 3136 views

I agree. It strikes me as rash to suddenly drop EUDIR. However; if it is dropped, then some function like this added to std filesys.e would be helpful:

include std/os.e                                                                                               
include std/filesys.e                                                                                          
                                                                                                               
--  get EUDIR from path to "eui", thanks to SDPRINGLE:                                                  
sequence eui                                                                                                   
ifdef WINDOWS then                                                                                             
    eui = "eui.exe"                                                                                            
elsedef                                                                                                        
    eui = "eui"                                                                                                
end ifdef                                                                                                      
                                                                                                               
public function eudir()                                                                                        
sequence eudirectory                                                                                           
    eudirectory = locate_file( eui, getenv("PATH") )                                                           
    eudirectory = eudirectory[1..length(eudirectory)-length(eui)-4]                                            
return eudirectory                                                                                             
end function                                                                                                   
public constant EUDIR = eudir() 

13. Re: Obsolete EUDIR!

• Posted by SDPringle Feb 03, 2013
• 2830 views

In 4.0 (and 4.1), there is a routine called include_paths() for finding where the include files are stored. One can use locate_file with getenv to find out where the interpreter and other binaries are.

Shawn Pringle