You need to fix the hardcoded path in Visual Studio 2013 and register the hMailServerlibs
Environment variables and copy the needed boost and openssl binaries to it.
For Setups you need the InnoDB Installer Kit:
mattg wrote:You could probably just do that with a script rather than a re-write of the source
mylove1289 wrote:Dear Dravion,
I downloaded and used versions:
- hMailServer: download "Branch:master" version on github: https://github.com/hmailserver/hmailserver
- Lib Boost source release: 1_57_0
- Lib OpenSSL source release: 1.0.2a
According to your instructions in previous post, I have built successfully.
I'm really grateful to you, my output look like screenshot:
Now, when I'm running sourcecode on debug mode, I have received a error as screenshot:
mylove1289 wrote:mattg wrote:You could probably just do that with a script rather than a re-write of the source
thanks for your comments, which can be a good idea for me
you did this problem yet, please guide or give me some suggestions
thank you very much.
If you take a close look you see the "Errors" is reflectig missing Debug Symbol files of the Windows
Operating System itself. To get rid of the PDB Error messages do the following steps:
In Visul Studio 2013 goto the Debug Menue
1) Debug->Options and Settings
2) Expand "Debugg" and select "Symbols"
Check [x] Microsoft Symbol Servers
Set "Cache symbols in this Directory" to something like this: C:\dev\hmailserver\symcache or somthing.
After new build/rerun you will notice Visual Studio loads a lot of PDB files from Microsoft Debug Symbol
servers, this can take a few seconds or minutes, depending on your connection speed.
hMailServer.exe is a Windows Service which means it runs in the Background without a Userinterface
(even not a Console interface). So the normal behavior is to run silent in the Background. Obviously this
is not verry developer friendly and just for this Martin (the Inventor of hMailServer) implemented a
"/Debug" switch to make sure hMailServer doesnt simply quit if started from Visual Studio in a Debugging
Session. To make sure hMailServer.exe runs in a console Window and stays open do the following steps
1) Rightclick the hMailServer Project in Visual Studio Solution Explorer and click properties
2) Expand Configuration and Properties > Debugging
3) Insert /Debug in the field Command Arguments and click ok
4) Rerun your Debug session
mattg wrote:Not exactly the same, but close.
This user saved attachments to a networked drive, and replaced the attachment with a link embedded into the email.
I'm guessing that all recipients in the distribution list are LOCAL users
Dravion wrote:The Errors you receive is because the Tools Solution is set to x64 bit and therefore needs a x64
The easiest steps to solve the problem is to change config of the Tools Solution Workspace to x86 and
not x64, then the hMailServer tools will compile just fine.
Dravion wrote:Second Option:
Just download hMailServer production release hMailServer-5.6.5-B2367.exe
https://www.hmailserver.com/download_fi ... loadid=254 and do a full install for MSSQL-Server
and start the Server the normal way.
Login via hMailServerAdmin, setup settings ect. Logout and stop the hMailServer Windows service.
Go back into Visual Studio and restart hMailServerAdmin from Tools project Workspace.
If anything is fine and dandy, hMailServer service should be automatically launched and connected
to MSSQL and hMailServerAdmin should ask for a password to login
Dravion wrote:You running in this problems because you need some registry settings and a valid hMailServer.ini config file.
To make this work the simples way is to just install a ordinary hMailServer Setup
Just download and install hMailServer
After this, goto Windows Computer Management and stop hMailServer, go back to Visual Studio and build/restart hMailServer with the password of your former hMailServer setup. Info: hMailServer from visual Studio will override the needed registry settings automatically and redirects all calls to your compiled hMailServer.exe in your development directory
(DONT TRY TO RUN AND BUILD HMAILSERVER from Visual Studio ON A PRODUCTION SYSTEM)!.
This is only needed to get started. Later, if you build the Installer, all registry settings for your build will setup correctly,
so there is no need to mess arround for customers - this is just needed for your Visual Studio Environment.
Hardcoded file and path entries (i allready created an issue on GitHub, do you remember?)
I tested the source on Visual Studio 2015 Enterprise x86 and i got over 120 errors on source level!!
mylove1289 wrote:thank Dravion,
I follow your steps and when running "hMailServer Solution Tools", I get a message:
Next, i run DBUpdater.exe in the installation directory (exp: C:\Program Files (x86)\hMailServer\Bin), i get a error
Please help me, many thanks to you.
martin wrote:Hardcoded file and path entries (i allready created an issue on GitHub, do you remember?)
Actually not. Care to link it? The only issue created by "Dravion" is the request for an alternative access protocol.I tested the source on Visual Studio 2015 Enterprise x86 and i got over 120 errors on source level!!But the instructions tells you to use VS2013. So not sure why you would try with another version.
Sure, but VS2015 is now out there quite some time and had some Servicepacks and 2016 is on the way.
You need to migrate the source in some point in time. I played a bit arround with it, degrading some Warning level to /w2 and supress/disable some Warnings but without effect, i think there is code in the
repo which isnt supported any longer by VS2015 and newer. Sure this isnt priority right now.Reading your other comments, I get the feeling that some essential part of the instructions is missing. Because these binaries are built on several machines with different paths set up without getting the issue you are getting.
This is no suprise. If you build it periodically on diffrent systems without reinstalling VS and the SDK
it will work, until you install a new Version of VS. Precompiled Headers are a Major problem and can
easy lead to a Visual Studio Setup which cannot compile the source regardles if you step up every step
in your readme or not.Do you happen to have a link to the hardcoded file path issue? That seems like a good starting point to understand the issue.
martin wrote:1) Uninstall hMailServer
2) Delete the entire hMailServer directory
3) Install hMailServer 5.7 from the build server https://build.hmailserver.com/viewLog.h ... =artifacts
You're using the source code for version 5.7, and the database version must match that one. But you installed an older version of hMailServer, so in your case the source code is not compatible with the database version. Installing the right version of the binaries will solve that.
martin wrote:3) Install hMailServer 5.7 from the build server https://build.hmailserver.com/viewLog.h ... =artifacts
mattg wrote:martin wrote:3) Install hMailServer 5.7 from the build server https://build.hmailserver.com/viewLog.h ... =artifacts
This link should be on the github main hmailserver page, in environment setup section please.
RvdH wrote:I can confirm Martin's directions in the readme on how to compile hMailserver (5.6.x) work perfectly with 3th party libraries used by hmailserver (eg: without updating boost/openssl)
Users browsing this forum: No registered users and 4 guests