This is the mail archive of the insight@sourceware.org mailing list for the Insight project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
First off, I want to point out that I can build the very recent cvs head for an embedded arm application but it doesn't run correctly in that the insight gui does not reflect the actual location of the PC while debugging/stepping (the green highlighted line never moves). This is regarless of whether the tk/tcl is system supplied or insight's own.
But when build with i686-pc-mingw32-gcc toolchain (fedora 12 yum), the same (windows specific) kludges as before were required (syntax errors in window specific tck/tk code regarding dde and registry that can be commented out).
However, with mingw32 I had to build/install then build/install again to get insight.exe to appear at install/bin. It seems that in the install directory under lib there needs to exist *at compile time* tkConfig.sh and tclConfig.sh. So you have to make clean all, make install, then make clean all, make install again when you are starting with an empty install directory. So if you keep install/lib/tclConfig.sh and tkConfig.sh between compiles (don't completely clean the install dir) you are ok the next time.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |