This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Global 32/64 bit collision issues
- From: Herbert Stocker <hersto at gmx dot de>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 28 May 2013 04:48:59 +0200
- Subject: Re: Global 32/64 bit collision issues
- References: <20130523084435 dot GB13513 at calimero dot vinschen dot de> <51A2C50A dot 5090405 at users dot sourceforge dot net> <20130527100409 dot GD2483 at calimero dot vinschen dot de> <BLU173-W111D5EE8B1171370E465CEB5960 at phx dot gbl> <20130527143315 dot GA28463 at calimero dot vinschen dot de> <51A41821 dot 7050805 at gmx dot de>
On 28.05.2013 04:36, Herbert Stocker wrote:
Therefore some config setting that tells what to append seams
necessary, be it an environment variable or a registry setting.
If the user should not be bothered with such a setting at installation
time, the 64 bit setup could rename all 32 bit services and short cuts
to have the '32' suffixes. But users may need to adopt their self-made
scripts. Therefore leaving this setting to the user, seams best for me.
Sorry for posting twice, but this idea came too late:
How about using Corinnas algorithm at installation time and
storing the result (whether to append '32', '64' or nothing)
in the registry?
Then we have the automatism as well as consistency during the
life time of an installation.
Herbert