Faculty of Information Technology
Software Engineering Group

#172 closed defect (fixed)

Smalltalk/X fails to start on Windows when launcher script is run from different directory

Reported by: Jan Vrany Owned by:
Priority: major Milestone: 8.0.0
Component: default Keywords:
Cc: Also affects CVS HEAD (eXept version): no

Description

Steps to reproduce:

  1. Open terminal, in build tree go to build\stx directory
  2. Run Smallltak/X from there: projects\smalltalk\smalltalk.bat --eval "Logger info: 'KUK'"

Observed behavior

Smalltalk/X IDE does not start, smalltalk.bat says:

jv@WIN7 H:\Projects\SmalltalkX\sources\stx_8_0_0_x32_lin\build\stx      
> projects\smalltalk\smalltalk.bat --eval "Logger info: 'KUK'"          
The system cannot find the file smalltalk.cfg.                          
                                                                        
"[INFO] PowerShell detected: ->TRUE<-.                                  
"[INFO] The latest latest_powershell_version found: 2.0."               
"[INFO] With the runtime being: v2.0.50727."                            
                                                                        
"[ERROR] No message defined."                                           
                                                                        
"[ERROR] No message defined."                                           
Press any key to continue . . .                                                                                                                

--
I have not tested but I think this also affects "release" builds. This must be tested before closing this issue!

Also, this makes me think whether the launcher script should look for it's configuration file also on %USERPROFILE%\.smalltalk\smalltalk.cfg. It kind of make sense to ma to configure the behavior once for all different installations ans build trees I'm using (for example, when working on different features/projects).

Change History (6)

comment:1 Changed 16 months ago by Patrik Svestka

I see the issue was that the path variable was missing from the whole configuration filename. The patch should fix the issue.

comment:2 Changed 16 months ago by Patrik Svestka

Status: newtesting

comment:3 Changed 16 months ago by Patrik Svestka

In the last patch I have added a link to the ticket.

Note: See TracTickets for help on using tickets.