This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Insight as cross-debugger: How to handle tcl?


Hi.

I'm thinking about building insight as a cross debugger... The build as such does not seem to be a problem, but the TCL installation is causing me a bit of a headache; insight comes with a complete TCL/Tk distribution, and it won't work with anything else in most cases. I'd rather not install this TCL setup, at least not on the default location, as it will probably lead to conflicts with the other tcl packages on my system and/or between cross-debuggers for different targets.

Questions:

  1. Can I tell insight (at build time) to use my standard TCL
     installation?
  2. If not, can I configure the package to install the supplied TCL
     setup on an unique location where only the corresponding insight
     build will see it?

--
Toralf



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]