kicad-developers team mailing list archive

[Jason Whiteman <whitemanjason@xxxxxxxxx>]

Thanks again for the continued support from the list.

All previous environment snapshots I have sent were after running the
"setenv.bat" script.   My methodology for loading pcbnew is to try running
direct from ./kicad/bin (from a sentenv.bat load) and also from using
"RunKicad.bat" which loads kicad.exe first.

I have sent bits and pieces of my environment as it applies to the
suggested assumed missing dependency.

Here is the full environment ( C:\> set >env.txt    - env.txt results)
slightly censored only for what looks a mentor graphics key.   Otherwise
as-is.  Therefore, there is some "noise" from other env variables for other
packages.  However, everything fed to kicad.exe and pcbnew.exe is below as
a result of setenv.bat.

ACTEL_FOR_ALTIUM_OVERRIDE=
ADSK_3DSMAX_x64_2012=C:\Program Files\Autodesk\3ds Max Design 2012\
ALLUSERSPROFILE=C:\ProgramData
AltiumPath=C:\Program Files (x86)\Altium Designer S09 Viewer\System
AMDAPPSDKROOT=C:\Program Files (x86)\AMD APP\
APPDATA=C:\Users\MY-COMPUTER\AppData\Roaming
AVR32_HOME=Y:\WinAVR-20100110
BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\bzr.exe
BZR_HOME=Y:\Kicad_Build\kicad-winbuilder-3.4\profile
BZR_PLUGIN_PATH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar\plugins
CALLDIR=Y:\Kicad_Build\kicad-winbuilder-3.4
CLASSPATH=.;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
CM2012DIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=MY-COMPUTER
ComSpec=C:\windows\system32\cmd.exe
configsetroot=C:\windows\ConfigSetRoot
EDPATH=Y:\WATCOM\EDDAT
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\MY-COMPUTER
ICONV_VER=1.9.2
ILBDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\
ILLDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\
ILMDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\
INCLUDE=Y:\WATCOM\H;Y:\WATCOM\H\NT;Y:\WATCOM\H\NT\DIRECTX;Y:\WATCOM\H\NT\DDK
KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad
LenovoTestLogFile=preload.log
LenovoTestPath=C:\prdv10\
LMC_HOME=E:\Xilinx91i\smartmodel\nt64\installed_nt64
LM_LICENSE_FILE=c:\lattice_license\license.dat
LOCALAPPDATA=C:\Users\MY-COMPUTER\AppData\Local
LOGONSERVER=\\MY-COMPUTER
MGLS_LICENSE_FILE=c:\MentorGraphics\[censored - looks like a key].txt
NUMBER_OF_PROCESSORS=2
OMP_NUM_THREADS=2
OS=Windows_NT
Path=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar;Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\python;Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10;Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin;Y:\Kicad_Build\kicad-winbuilder-3.4\kicad;C:\windows\System32
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.RB;.RBW
PATH_BZR=Y:\Kicad_Build\kicad-winbuilder-3.4\env\bazaar
PATH_CMAKE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\cmake\cmake-2.8.12.2-win32-x86\bin
PATH_ENV_BASE=Y:\Kicad_Build\kicad-winbuilder-3.4\env
PATH_ICONV=Y:\Kicad_Build\kicad-winbuilder-3.4\env\iconv-1.9.2.win32\bin
PATH_KICAD=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin
PATH_KICAD_ROOT=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad
PATH_MINGW=Y:\Kicad_Build\kicad-winbuilder-3.4\env\mingw-w64\mingw32\bin
PATH_PATCH=Y:\Kicad_Build\kicad-winbuilder-3.4\env\patch\bin
PATH_PROFILE=Y:\Kicad_Build\kicad-winbuilder-3.4\profile
PATH_PY=Y:\Kicad_Build\kicad-winbuilder-3.4\env\python
PATH_SWIG=Y:\Kicad_Build\kicad-winbuilder-3.4\env\swig\swigwin-2.0.10
PATH_TEE=Y:\Kicad_Build\kicad-winbuilder-3.4\env\tee
PATH_TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp
PATH_TMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\tmp
PATH_WIN=C:\windows\System32
PATH_XML2=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxml2-2.7.8.win32\bin
PATH_XSLT=Y:\Kicad_Build\kicad-winbuilder-3.4\env\libxslt-1.1.26.win32\bin
PATH_ZLIB=Y:\Kicad_Build\kicad-winbuilder-3.4\env\zlib-1.2.5\bin
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 20 Model 1 Stepping 0, AuthenticAMD
PROCESSOR_LEVEL=20
PROCESSOR_REVISION=0100
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=KiCad-Winbuilder$P$G
PSModulePath=C:\windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
PYTHONHOME=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin
PYTHONPATH=Y:\Kicad_Build\kicad-winbuilder-3.4\kicad\bin
QTJAVA=C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
QUARTUS_ROOTDIR=C:\altera\12.1_free\quartus
SESSIONNAME=Console
SOPC_KIT_NIOS2=C:\altera\12.1_free\nios2eds
SystemDrive=C:
SystemRoot=C:\windows
TelerikSLDir=Y:\PGM_Files_Telerik\RadControls for Silverlight Q2 2013\
TelerikWPFDir=Y:\PGM_Files_Telerik\RadControls for WPF Q2 2013\
TEMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\temp
TMP=Y:\Kicad_Build\kicad-winbuilder-3.4\profile\tmp
USERDOMAIN=MY-COMPUTER
USERNAME=MY-COMPUTER
USERPROFILE=C:\Users\MY-COMPUTER
VBOX_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\
VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio
10.0\Common7\Tools\
WATCOM=Y:\WATCOM
WDIR=C:\PADSViewer Projects
WHTMLHELP=Y:\WATCOM\BINNT\HELP
windir=C:\windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
WIPFC=Y:\WATCOM\WIPFC
WIX=C:\Program Files (x86)\WiX Toolset v3.8\
XILINX=E:\Xilinx91i
XILINX_FOR_ALTIUM_OVERRIDE=
XML2_VER=2.7.8
XSLT_VER=1.1.26
ZLIB_VER=1.2.5

========

I'm currently trying a debug build and starting to add "hello world"
statements in the code to orient myself to the issue from a software-debug
standpoint.  As I haven't had much experience with the kicad
source/environment - this problem is as good as any as a platform to start
modifying the code and getting familiar somewhat with the structure.  I see
one place where the error is thrown is in kiway.cpp - so I'll start there
and work backwards.

Of course this is in parallel with the thought that a user may see the
problem and alert me to some other issue.  Other than previous mingw32
environments for other (successfully compiled) projects - this is a "clean"
install on Win 7.  Unlike an earlier attempt with winbuilder 3.3 - this
time the compile worked fine and the errors are runtime related.  Other
mingw32 projects I have built are not kicad (different targets
entirely).    It looks like the setenv.bat blows away much of the
environment that would possibly interfere from previous projects - so I do
not readily see an issue there.  Although beyond the "SCRIPTING OFF" flag
-- which is in the queue for testing -- moving to a clean VM is among the
next steps.  As much as I love debugging what seems to be a "unique" and
"individual" experience with the toolchain - ultimately I just want to get
to any environment - VM or not - that produces working binaries as a
baseline and continue to actual development.

Regards,
Jason



On Fri, Jun 27, 2014 at 12:40 PM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:

> On 06/27/2014 12:01 PM, Brian Sidebotham wrote:
> > Hi Guys,
> >
> > I should first say, this is not typical of Winbuilder. Both pcbnew and
> > cvpcb work fine for me on a fresh Windows 7 install using the github
> > fp-lib-table. So there's clearly something different about your setup.
> >
> > Process monitor is (from sysinternals) is excellent at tracking
> > dependency loading, so if you want to track what's getting loaded from
> > where, that's the best tool for the job. If you use dependency walker
> > make sure you run it from the console provided by enterenv.bat so that
> > PATH is set the same as when kicad is run.
>
>
> Brian, thanks for your involvement.  I am now bowing out.  I just wanted
> us to remember
> that it loads and runs fine under pcbnew.exe, and not kicad.exe.
>
> Your comment about setting the environment differently probably pertains
> to the difference
> in loading results also.  Perhaps there's a difference in how the
> environment is setup for
> the specific process.
>
> Remember that the environment when the process runs, is what's critical.
>  A batch file can
> add or remove settings to the environment that it starts with, before the
> process runs.
> So simply getting a snapshot from the registry is not necessarily
> sufficient to describe
> the runtime environment variable values that any particular process sees.
>
> Environment varialbe "PATH" is still my biggest suspicion, in concert with
> a difference in
> launching methodology.
>
> Out,
>
> Dick
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>