On Sep 29, 2008, at 10:17 AM, Benoit St-Pierre wrote: >> > I installed the Developer tools some times ago. But since someone > from this mailing list told me to be sure to have a tcl-dev version, I > went for Tcl/Tk Aqua, batteries included, without modifying anything > during installation. It can be found there : > I imagine that for the current scid trunk, having tcl/tk 8.5 would be helpful. For 3.6.25, however, I'm not sure it is that useful. Sticking with the system installed version would be fine.
> http://tcltkaqua.sourceforge.net/ I wasn't really able to make heads nor tails of this site. I couldn't find the 8.5 stuff, it all looked rather old. I didn't look very hard, though. >> In looking at the configure script, I see that it looks for headers >> and libraries in /usr/include and /usr/lib first. This is probably >> not optimal as it means that files installed in local directories >> will always be shadowed by the system ones, which seems backwards >> to me. So, no matter where your new installation puts its headers >> and libraries, the configure script will not spit out a correct >> makefile. It's probably easiest to just edit the makefile that is >> produced. > > Do you mean that when i do ./configure, there is a file named makefile > that is produced ? And if so, what do I modify ? I will try to > A file called Makefile is created from the Makefile.conf (which you copied from Makefile.conf.darwin). Unfortunately, you can't really do any useful edits to it until you have the answers to the questions I asked about headers and libraries and such. >> I had the same problem after installing TclTk 8.5. The tcl* and tk* >> files in /usr/include and /usr/lib are soft links pointing to the >> files in Tcl.framework and Tk.framework inside /System/Library >> (default installation), so I just replaced them with soft links >> pointing to the files inside /Library (new installation). > > How do you that ? Must one use ln or just create a link out of > Finder ? > This last bit did not come from me. I'm assuming you pasted in some other email. I will comment on it, however. This is exactly the kind of thing you don't want to do. The OS "owns" everything in /usr/lib and /usr/include. It has carte blanche to scribble all over it. So if you go changing things in here be warned that things may change out from under you on any subsequent OS update. I really object to third party packages trying to install things in system owned locations. There is a place for this stuff and it is not /usr/bin, /usr/lib, etc. On old-school unix installations it is / usr/local. On OS X it is a combination of /Library (as opposed to / System/Library) and /usr/local (or /opt or /sw in the case of macports or fink). ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
