Re: gEDA-user: minipack-result -- gschem

2011-05-13 Thread Duncan Drennan
>> By the way, should the lines of the config files be terminated unix style, >> or DOS style? > > Doesn't make any difference either way. I did recently pick up a bug with gschem's postscript output and EOL characters which I must report on launchpad (not related to config files). It seems that

Re: gEDA-user: minipack-result -- gschem

2011-05-13 Thread Duncan Drennan
> Next step: How do I configure gschem to find my local library? > On my linux box I have these lines in ~/.gEDA/gafrc : Look in C:\Users\username\.gEDA I have my gafrc and gschemrc in there. In gafrc I use the following line, (component-library-search "d:/Projects/sym") i.e. / works perfectly

Re: gEDA-user: minipack-result -- gschem

2011-05-12 Thread Peter TB Brett
On Thursday 12 May 2011 17:06:01 Kai-Martin Knaak wrote: > [snip] > > Now I get a decent gschem GUI :-) Great! > [snip] > > What would be the HOME in windows. Or alternatively, how would I give > a full windows path that includes backslashes and the drive letter? Just like that, I think (you may

Re: gEDA-user: minipack-result -- gschem

2011-05-12 Thread Kai-Martin Knaak
Duncan Drennan wrote: > I have the following environment variables set in Windows Vista, > > GEDABIN=D:\Program Files\gEDA\bin > GEDADATA=D:\Program Files\gEDA\share\gEDA > GUILE_LOAD_PATH=D:\Program Files\gEDA\share\guile\1.8 > Thanks! Now I get a decent gschem GUI :-) Next step: How do I confi

Re: gEDA-user: minipack-result -- gschem

2011-05-11 Thread Duncan Drennan
> Okay, the problem is definitely with Guile rather than gschem. Please make > sure that you have its paths set up correctly so that it can find its > Scheme library. I have the following environment variables set in Windows Vista, GEDABIN=D:\Program Files\gEDA\bin GEDADATA=D:\Program Files\gEDA\

Re: gEDA-user: minipack-result -- gschem

2011-05-11 Thread Peter TB Brett
On Wed, 11 May 2011 19:08:07 +0200, Kai-Martin Knaak wrote: > Peter TB Brett wrote: > >> boot-9.scm is part of Guile (it's the master Scheme script needed to >> initialise the interpreter). Guile may not be installed correctly. Try >> running 'guile' and see if you get to a prompt. > > I get th

Re: gEDA-user: minipack-result -- gschem

2011-05-11 Thread Kai-Martin Knaak
Peter TB Brett wrote: > boot-9.scm is part of Guile (it's the master Scheme script needed to > initialise the interpreter). Guile may not be installed correctly. Try > running 'guile' and see if you get to a prompt. I get the same result: C:\Programme\result\bin>guile.exe ERROR: In procedure pr

Re: gEDA-user: minipack-result -- gschem

2011-05-11 Thread Peter TB Brett
On Wed, 11 May 2011 18:31:35 +0200, Kai-Martin Knaak wrote: > Kai-Martin Knaak wrote: > >> -minipack-gschem-with-winXP-in-Virtualbox-- >> C:\Programme\result\bin>gschem.exe >> ERROR: In procedure primitive-load-path: >> ERROR: Unable to find file "ice-9/boot-9.scm" in load

Re: gEDA-user: minipack-result -- gschem

2011-05-11 Thread Kai-Martin Knaak
Kai-Martin Knaak wrote: > -minipack-gschem-with-winXP-in-Virtualbox-- > C:\Programme\result\bin>gschem.exe > ERROR: In procedure primitive-load-path: > ERROR: Unable to find file "ice-9/boot-9.scm" in load path I forgot to mention that the binary just dies after this. No G

gEDA-user: minipack-result -- gschem

2011-05-11 Thread Kai-Martin Knaak
Kai-Martin Knaak wrote: > Unfortunately, the binaries fail when started with wine. They fail with > different symptoms: This was via ssh. So this may have been an additional complication. From the local desktop I get different spew. I'll split the output of the different binaries to separate pos