Menu
▾
▴
Re: [Hermesmail-discuss] How can I compile Eudora/Hermes Source Code ?
|
From: Curtis M. <cm...@db...> - 2021-01-14 21:42:56
|
Hi Ronald, I have a no longer-used licensed copy of Wintertree (Dec 2004) that I can provide with a license key, along with US-English, German and Finnish dictionaries. -Curtis At 02:08 PM 1/14/2021, Ronald van Ginkel wrote: >Hi guys. > >This is how things are actually: > >I have contacted Leon Shustek from The Computer >History Museum, who is the one who got the >source code from Qualcomm. He has treated me >very kindly and provided very useful information: > >- In the version published by the museum, 5 files are missing: > >Spell checker (Wintertree-software): >spell.cpp >scce.h (I have found it on the internet and added to the project) > >Combobox for embedding in a SECCustomToolBar (Stingray): >TBarBmpCombo.cpp >TBarStatic.cpp >TBarEdit.cpp > >- Wintertree also required to change the prefix >of the SCCE_ * functions to SpellCheck_ *, which >generated a lot of compilation errors. I have >undone the change and these errors are gone. > >- I keep trying to compile the original project >(the museum version) in Visual Studio 2017. >There are more than 1,000 errors, but most of >them are repetitive. I´m solving the most obvious and easy ones. >One of these errors (which generates 440 errors) >I have posted on StackOverflow for help as it is >beyond my knowledge. If anyone in this group >knows how to solve it, I would be very grateful. > >https://stackoverflow.com/questions/65718797/a-bit-complex-c2102-requires-l-value-error/65718881#65718881 > >I think the goal of compiling a version of >Eudora without the spell checker and without the >Combobox control seems quite accessible. > >I will continue to move forward with the idea of minimizing errors. > >Keep in touch > >Ronald > >______________________________________________________________________________________________________________________________________ > >Hi Curtis. > >Thank you for your clarifyng answer. > >Pete explained Stingray issue two week ago. It >seems there's not an easy solution cause Eudora >is using a custom Stingray library. > >Anyway, I shall contact Perforce to see if we can move forward. > >I shall keep you informed. > >Regards! > >Ronald > >______________________________________________________________________________________________________________________________________ >Hi Pete, >I think Ron is asking whether anybody has >successfully assembled an environment in which >Eudora can be compiled from source code released >by the museum. I suspect that the answer is no, >given the Stingray obstacle. The spell checker >should be no big deal - there are quite a few at >Nuget with an Apache license. For Stingray, it >might be a good idea to open a dialog with >Perforce - >https://www.perforce.com/products/stingray. They >do not provide pricing information - >https://www.perforce.com/how-buy - which >suggests that it is quite pricey. But it is also >possible that they might be willing to cooperate >with an open-source product in exchange for free >advertising, esp. given that most of us still >using Eudora (and those who wish they could use >it again) -- are software developers or in a >related profession. Those that are not still >tend to be scientists or researchers at academic institutions. > >Currently the biggest problem with Eudora is the >character encoding issue. Daniel Kuhn has >created a semi-effective Delphi plug-in ( >http://www.windharp.de/software/utf8iso.htm) but >lost the source code. Surely that he could >outline its operation. A plug-in just has to >compile to a Win-32 DLL so it's >language-agnostic. Another minor problem is the >mailbox limit of 2GB, but I can live with that. >HTML rendering is another, but lesser issue, >along with inability to decode some types of embedded images. > >I still use Eudora on my 8 or 10 email accounts >- with some mailboxes dating back to 1996 or so. >Occasionally I have to log into a websmail >service or gmail to deal with particularly >recalcitrant messages. With the TLS changes >already done, a good UTF8 plugin would be a huge >step forward, pending the more difficult issue >of actually getting the ^&#&$ thing to compile! >Curtis > > > >At 03:35 PM 1/9/2021, Pete Maclean wrote: >>Ron, >> >>>- Is there any source code that can be compiled in anyway ? >> >>I do not understand this question. >> >>>- If it is not: >>> >>> - What source code and environment >>> are the best to begin to fight with ? >> >>I recommend starting with the raw code that was >>published as open source rather than the Hermes repository. >> >>> - Is there an unavoidable obstacle >>> that prevents compiling the source code? >> >>Yes. The main obstacle is the Stingray >>library. It is an obstacle in several ways >>especially in that Eudora was built using a >>customized version of it and we do not have >>documentation on those customizations. Another >>minor obstacle is that Eudora uses a spell >>checker that is a commercial product. >> >>Pete Maclean >> >>At 07:28 AM 1/9/2021, Ronald van Ginkel wrote: >> >>>Hi Curtis. >>> >>>Yes, I'm afraid all of us are short of time, >>>but for me, Eudora is my main tool for my >>>work, so I wanna invest some time and resources on it. >>> >>>Thank you for your offer, but I also have all >>>VS versions (I'm Microsoft Silver Partner), >>>but I need to know what is the first step. >>> >>>As I see, Eudora 'museum' code needs VS 2003: >>> >>>>Eudora.vcproj >>> >>>><VisualStudioProject >>>> ProjectType="Visual C++" >>>> Version="7.10" >>> >>> >>>But Hermes code needs VS 2015: >>> >>>>Eudora.vcxproj >>> >>>><Project DefaultTargets="Build" ToolsVersion="15.0" >>> >>> >>>And as I see, Hermes installer's eudora.exe is >>>the original one, so it seems it's no been compiled recently. >>> >>> >>>So, my point is: >>> >>>- Is there any source code that can be compiled in anyway ? >>> >>>- If it is not: >>> >>> - What source code and environment >>> are the best to begin to fight with ? >>> >>> - Is there an unavoidable obstacle >>> that prevents compiling the source code? >>> >>>Regards! >>> >>>Ronald >>> >>>______________________________________________________________________________________________________________________________________ >>>Hi Ronald, >>>If you would like to give it a go I have VS >>>2005 Pro. I can send an ISO image and license key. Wish I had more time! >>>Regards, >>>Curtis Meadow >>> >>>At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >>> >>>>Hi Steve. >>>> >>>>Thank you for your answer, but the only thing >>>>I need to know is if it is possible to >>>>compile the source code of Eudora or Hermes >>>>and what is the necessary environment to do it. >>>> >>>> From here I will be able to understand where >>>> the project is standing and see if I can help in any way. >>>> >>>>Regards! >>>> >>>>Ronald >>>>______________________________________________________________________________________________________________________________________ >>>>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >>>> >>>>>Hi Steve. >>>>> >>>>>I took a way, but I finally could setup a >>>>>Virtual Machine with Windows XP 32 Bits >>>>>(Visual Studio 2002 cannot be installed on a >>>>>64 bits OS), installed VS2002 and imported Hermes project. >>>>> >>>>>... but it cannot been compiled. >>>>> >>>>>As I see, project file needs at least 2010 version. >>>>> >>>>>I've installed a VS2010 and tried to >>>>>compiled, but I get a lot of errors, most of >>>>>them due to the use of 'noexcept' expression >>>>>that it's only supported at VS 2015 or >>>>>above, and with VS2015 I get tons of errors trying to compile. >>>>> >>>>>Can anyone tell me is there a way to compile the source code ? >>>>> >>>>>Thank you in advance. >>>>> >>>>>Ronald >>>> >>>>Ronald, >>>> >>>>My main development machine keeps changing, >>>>and I have changed motherboards 1-2 times in >>>>recent years, so the environment I first >>>>tested the Eudora source code in no longer >>>>exists. This pre-dated the 'Hermes' project >>>>by several months at least. I don't have the >>>>'Hermes Project' files. I have the files >>>>that were released from the Computer Museum that Qualcomm authorized. >>>> >>>>A little common sense: VS2010 didn't exist >>>>at the time of the final release of Eudora, >>>>so it couldn't have been the required version. >>>> >>>>When a newer version of Visual Studio tries >>>>to open a project from a previous version of >>>>Visual Studio, it will convert the old >>>>project file to the new project file. It >>>>also shows a warning box on the screen when >>>>it does this, and gives you the option to >>>>save the old version unmodified but you have >>>>to enter a new name for the old file to >>>>use. So if you had initially tried to >>>>compile the source code with VS2010, the project file was converted. >>>> >>>>I don't presently have Visual Studio 2002 >>>>installed. I did have it installed in a >>>>64-bit Windows 7 environment. As I recall, >>>>it wasn't easy to install. I just finished a >>>>search, and I found some install instructions >>>>which say that to install it, you need to not >>>>already have newer versions of Visual Studio >>>>on the system, and there were a couple of >>>>specific items you need to check-off and not install, for it to work. >>>> >>>>Use of Windows XP to make a compiling >>>>environment is a common work around for these >>>>kinds of problems. I recently (recent defined >>>>as within the past 2 years) had to run a >>>>16-bit program that was compiled using >>>>QuickBasic. I had to do the same thing, as >>>>Windows XP could run 16-bit programs. I soon >>>>went to some trouble to write a replacement >>>>program that runs in a 64-bit environment. >>>> >>>>I don't know anything about this 'noexcept' >>>>expression you are talking about, and >>>>anything I say is going to be speculation. I >>>>generally do most of my work in older versions of Visual Studio. >>>> >>>>Steve >>>> >>>> >>>>_______________________________________________ >>>>Hermesmail-discuss mailing list >>>>Her...@li... >>>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>>> >>>> >>>>______________________________________________________________________________________________________________________________________ >>>> >>>>_______________________________________________ >>>>Hermesmail-discuss mailing list >>>>Her...@li... >>>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>> >>> >>> >>>______________________________________________________________________________________________________________________________________ >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > > >______________________________________________________________________________________________________________________________________ > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > >______________________________________________________________________________________________________________________________________ > |
