| Ticket UUID: | 909911 | |||
| Title: | tclConfig.sh generation from makefile.vc | |||
| Type: | Patch | Version: | None | |
| Submitter: | patthoyts | Created on: | 2004-03-04 16:36:01 | |
| Subsystem: | 53. Configure and Build Tools | Assigned To: | davygrvy | |
| Priority: | 7 High | Severity: | ||
| Status: | Closed | Last Modified: | 2004-05-20 07:52:08 | |
| Resolution: | Accepted | Closed By: | patthoyts | |
| Closed on: | 2004-05-20 00:52:08 | |||
| Description: |
This patch fixes makefile.vc to generate a tclConfig.sh file. | |||
| User Comments: |
davygrvy added on 2004-05-19 03:07:06:
Logged In: YES user_id=7549 Added to HEAD. dkf added on 2004-05-18 21:48:02: Logged In: YES user_id=79902 Revisit TIP#59? patthoyts added on 2004-05-18 20:11:36: Logged In: YES user_id=202636 So can we add this in then? patthoyts added on 2004-05-14 20:04:36: Logged In: YES user_id=202636 Personally I think all these values ought to be embedded in tclsh as done for Perl. However... the intent is to ensure that having built and installed tcl using nmake/cl that a user can expect to build TEA projects using msys + cl. For that we need a valid tclConfig.sh - one that matches the current installation (normally the release, dynamic, non-threaded). IMO if the file is slightly wrong I'm not to bothered. Its easy to fix if it's just removing a t suffix from a few names. However converting tclConfig.sh.in into something useful is more work that I imaging most people can be bothered with. In other words, I'd rather have a slightly broken version than no version. dkf added on 2004-05-14 16:40:30: Logged In: YES user_id=79902 The tclConfig.sh file must always have the same name as that's the only way you can bootstrap the locating of the configuration. If people insist on putting different styles of build in the same dir it will break, but that's just tough since the other way round is really fscked up by design. The sensible thing is for people wanting to keep multiple installations of the same version of Tcl/Tk to do so by keeping them in different directory structures (e.g. c:/tcl/8.4static, c:/tcl/8.4threaded, etc) davygrvy added on 2004-05-14 08:14:12: Logged In: YES user_id=7549 This is an interesting marriage of concepts. this might need to be built for install rather than build. If one builds all possible flavors of Tcl: threaded, debug, static, memdbg, etc.. tclConfig.sh is built to the same spot each time overwriting what was done last. The same would be true if we generated it for install assuming one places tcl85.lib (the import) in the same place as tcl85s.lib (the static), etc. The use of different names per flavor was cosen to avoid this. I don't what the resolve is. tclConfigs.sh and tclConfigt.sh? patthoyts added on 2004-05-13 22:14:11: Logged In: YES user_id=202636 Reassigning as DG is really the makefile.vc person. patthoyts added on 2004-03-04 23:36:02: File Added - 78940: tclConfig.vc.patch | |||
Attachments:
- tclConfig.vc.patch [download] added by patthoyts on 2004-03-04 23:36:02. [details]