Opened 16 years ago
Closed 16 years ago
#4874 closed patch (duplicate)
win32 - default MYTHCONFDIR for windows
Reported by: | Owned by: | Nigel | |
---|---|---|---|
Priority: | minor | Milestone: | 0.22 |
Component: | mythtv | Version: | head |
Severity: | medium | Keywords: | win32 |
Cc: | Ticket locked: | yes |
Description
Allows default MYTHCONFDIR to be win32 path
Attachments (1)
Change History (10)
Changed 16 years ago by
Attachment: | mythcontext.patch4 added |
---|
comment:1 Changed 16 years ago by
Milestone: | 0.21 → 0.22 |
---|
comment:2 Changed 16 years ago by
Status: | new → infoneeded_new |
---|---|
Type: | enhancement → patch |
comment:3 Changed 16 years ago by
Perhaps the original submitter's desire was to have the ability to build the application in one location/configuration, and not be constrained to keeping it in that precise path when it is "installed" into a new location (ie when the binaries are copied onto a different PC they can be put elsewhere).? It's common practice under windows to allow a use to do this, and "install" the application wherever they like. hard-coding paths at compile-time is very frowned apon.
Buzz.
comment:4 Changed 16 years ago by
Possibly. I think the current code allows for that without adding anything, by building with prefix=./lib or similar
comment:5 Changed 16 years ago by
I am the submitter, somehow the email didn't stick. Buzz is correct. This will allow win32 installation to be installed by default all under {appdir} and work OOB. Directory structure will be c:\program files\mythtv
lib share
Changing the installation directory, an option often present to win32 users, will require the installer to define MYTHCONFDIR and MYTHLIBDIR appropriately. However, if it is installed in the default above, these env variables will not be required, nor will a recompile be needed. In any case, it fits together and corresponds with 4612 mentioned.
comment:6 Changed 16 years ago by
A few more thoughts: While it is appropriate to install ming and recreate the unix directory structure on a development machine, it is not on the distribution destination. Having the end-user install mingw or create c:\mysys\1.0\share, etc is not the preferred method, or recompiling to a hard-coded installation location
comment:7 Changed 16 years ago by
Status: | infoneeded_new → new |
---|
Move discussion to mailing list "Windows packaging" thread
comment:8 Changed 16 years ago by
Owner: | changed from Isaac Richards to Nigel |
---|---|
Reporter: | changed from anonymous to arnonm@… |
Status: | new → accepted |
Ticket locked: | set |
Rejecting until there is some explanation of the actual problem