You are here

WinMerge

5 posts / 0 new
Last post
buktop
Offline
Last seen: 15 years 9 months ago
Joined: 2006-10-03 18:36
WinMerge
Lurking_Biohazard
Lurking_Biohazard's picture
Offline
Last seen: 4 years 1 month ago
Joined: 2006-02-18 18:06
*
From http://winmerge.org/:
Installation

Just download the installer and double-click it.

Or you may simply unzip the binary zip package into the desired location, 
and run WinMergeU.exe (except for Windows 98/ME users who should use WinMerge.exe).

For more information, please see the Installation section of the Manual.

OK, let's look @ the manual...

From http://winmerge.org/2.4/manual/installing.html:
5.3. Installing from archive

WinMerge is pretty much independent from other system components. It doesn't 
integrate tightly to Windows or use lots of dlls. WinMerge[U].exe itself is 
dependent of MFC42[U].dll (and MSVCRT.dll) in addition to some system DLLs. 
So if mentioned DLLs already are installed to system, only WinMerge[U].exe 
is needed to run WinMerge.

Archive files have correct folder structure. WinMerge should be unzipped 
preserving folder structure to destination folder, for example C:\Program Files\. 
Root folder created has name /WinMerge-version, for example /WinMerge-2.4.0. This 
folder can be renamed or files copied to other folder (preserving folder structure!).

Seems to me if it is common/system dll files you might be alright.
Why don't you download it & try it out?

~Lurk~

~Lurk~

Ryan McCue
Ryan McCue's picture
Offline
Last seen: 13 years 1 week ago
Joined: 2006-01-06 21:27
I'm actually

Trialing this at the moment.
I'll post back once I get which DLLs.
----
R McCue
PortaBlog Home and My Website
And before anyone complains about the grammar, I'm so jetlagged that my
hands aren't even in the same time zone...

"If you're not part of the solution, you're part of the precipitate."

grizadams73
Offline
Last seen: 9 years 10 months ago
Joined: 2006-09-15 14:31
Uses the Registry

I used Portable RegShot to check, and the zip-based .exe (WinMergeU.exe) creates the following key: HKCU\Software\Thingamahoochie\WinMerge, along with 6 subkeys and 82 values. You'd need to make a launch wrapper to deal with them, for true portability.

I didn't find a setting to make it use a local .INI file. Perhaps someone would like to patch the source to do this? Or at least make a Feature Request at SF? I checked the SF trackers (ToDo, Bugs, etc) for any existing request (searched for portable and ini, individually) and found none.

Ryan McCue
Ryan McCue's picture
Offline
Last seen: 13 years 1 week ago
Joined: 2006-01-06 21:27
Well

I'll try it with Lapwing.
Edit: It works! No registry entries at all, Lapwing 1.0 RC2 worked!
Edit 2: Sorry, it crashes when you open a file. Oh well Biggrin
----
R McCue
PortaBlog Home and My Website
People who didn't need people needed people around to know that they were
the kind of people who didn't need people.
(Maskerade)

"If you're not part of the solution, you're part of the precipitate."

Topic locked