From: Keith M. <kei...@us...> - 2012-09-09 00:35:20
|
On 08/09/12 23:23, Maximus wrote: > Keith Marshall <keithmarshall@...> writes: >> Why? Users will install for a host which is either 32-bit or 64-bit; >> they don't need both together. > > It is valid ONLY for 32-bit OS. > When you use 64-bit OS, ConEmu must use appropriating libraries. > For example, user may start either 32-bit or 64-bit version of cmd.exe. > You can't restrict or predict bits of applications, so both > ConEmuHk.dll and ConEmuHk64.dll must exists (injects). > And ConEmuCD.dll or ConEmuCD64.dll must exists too, if started > console application uses some features like > * SetConsoleActiveScreenBuffer in Windows 7, > * or xTerm 256 colors. > As for ConEmuC.exe and ConEmuC64.exe, both are required for injects > and debug dumps features (32-bit and 64-bit processes respectedly). > > Only unwanted ConEmu.exe or ConEmu64.exe may be removed from package. Understood. So, you split it into the two packages, as below. Users on x86 install only the mingw32 package. Users on x86_64 request the installation of only the mingw64 package, which you have declared as requiring the mingw32 package, (within the mingw-get XML package specification), and mingw-get installs both packages. >> I would separate the two into: >> >> conemu-major.minor-mingw32-bin.tar.xz >> conemu-major.minor-mingw64-bin.tar.xz > > Is, for example, "conemu-5.120909-mingw32-bin.tar.xz" suitable? ;) Yes. >> Or, you might consider: >> >> $MINGW_ROOT/libexec/ConEmu32 >> $MINGW_ROOT/libexec/ConEmu64 > > I prefere one folder, because both versions (32/64) of helper files > may be called from ConEmu. > > $MINGW_ROOT/libexec/ConEmu That's fine, if it's better suited to the needs of your application. -- Regards, Keith. |