Hi Wolfgang, thank you for your feedback. I will try to consider this for my next update.
Interesting that you used GDAL 2 - I never had the courage to try. Concerning Python//Java/Swig: QMS does not depend on this, so we can safely leave it out. Just a quick feedback concerning your question at the end: > Question: > > If I compile everything as described and build the FILES directory at > the end without wanting an installer I have a lot of DLL's twice on my > machine. > Would it be possible to define some environment variables (or simply > extend PATH) > so that QMS can use DLL's already stored in the Qt5.5/Routino/... > directories? (I'll chack this by myself later on). This is a valid thought of course. But if you rely on PATH, you might run into DLL hell if users have installed different versions of the required DLLs. You depend on the order of directories in PATH, you may get strange errors or error messages which are hard to understand and so on. We already had such issues. And as consequence I explicitly reset the PATH to avoid that wrong .dll's are loaded. See https://bitbucket.org/maproom/qmapshack/commits/50d50a033fa5ea00e6515559fd86563ef61f17ef Storage is cheap nowadays and there are as may different configurations out there as there are QMS users. So I still think that providing QMS as completely self-contained package is the only reasonable solution. Of course, you could do a local patch on your machine to use the standard PATH. But please don't expect it for the standard distribution. Have a nice weekend, too, Helmut Am 27.02.2016 um 17:16 schrieb Wolfgang Thämelt: > > Am 25.02.2016 um 23:07 schrieb Helmut Schmidt: >> Hi zero and Wolfgang, >> >> thank you for your valuable feedback. >> >> I have updated the Windows build descriptions according to your comments: >> https://bitbucket.org/maproom/qmapshack/raw/tip/nsi/HOWTO-BUILD.md >> >> I hope I have covered everything important. >> If there are still issues, please tell me. >> >> There is still one open point which I will fix later: describe where >> to get from the libmysql.dll. >> For the momemt, it mightt be easiest to get it from the latest >> installer (QMapShack_Install_Windows64bit__1.6.0.exe) which has just >> been uploaded to https://bitbucket.org/maproom/qmapshack/downloads. >> >> Best Regards, >> >> Helmut > > Hi Helmut, > > thank you for your information. I think your compile instructions are > quite good, complete and understandable. > > I repeated the whole process described in the instructions (without the > preparation of an installer) > and had now problems, but I had a chance to find a few additional points > that might by good for consideration. > > Nevertheless allow me to point to a few of these details that could be > helpful if added to the instructions. I also formulated a few > questions and remarks. Maybe some of this stuff can be used to add some > more details and hints to your already good instructions. > > Required tools part: > > add > svn (co http://routino.org/svn/trunk routino ) download from ???? > hg (clone https://bitbucket.org/maproom/qmapshack QMapShack ) > download from ???? > > hg and svn can be avoided. Routino and QMS sources can be downloaded > as TGZ compressed files. > If somebody likes to use version control he certainly has got svn/hg > and knows how to use it. > > Qt5.5: describe if any possible required components. Complete package > is pretty large. > MinGW: describe required components - see remark in Routino part. > > GDAL part (used gdal 2.0.2): > > GDAL nmake.opt: > > set correct Python path: (required??????) > PYDIR = C:\Python33 > > set swig path: (required?????) > SWIG = c:\QtProjects\QMS\GDAL\gdal-2.0.1\swig.exe > > what about the JAVA part for SWIG???? > > - On the Windows Desktop: > => select Start | All Programs | Microsoft Visual Studio 2013 | > Visual Studio Tools | VS 2013 x64 Native Tools Command Prompt. > > On my machine/installation (Visual Studio 2013 Community-Edition) I > have to select: > Start | All Programs | Visual Studio 2013 | Visual Studio Tools | > VS 2013 x64 Native Tools Command Prompt > > (I'm not sure what the reason for this difference is! Maybe the > package used, maybe a repeated installation.) > > nmake /f makefile.vc step: > - plenty of warnings, only a few different warning types > - result: gdal200.dll, gdal_i.lib, gdal_i.exp, gdal.lib > > nmake /f makefile.vc devinstall step: > - similar warnings as in previous step > - result: some files are copied to the lib, include, ... > subdirectories of GDAL_HOME > > Proj.4 part: > > download from https://github.com/OSGeo/proj.4 (click "Download ZIP", > http://trac.osgeo.org/proj/ links to this page) > result: project.4-master.zip, used recent version: 4.9.2 > > routino part: > used version: 3.0, downloaded as routino-3.0.tgz and unpacked > > move QMS download step in the instructions to this place to have > build_routino.bat available > > Get build_routino.bat which you can find in \nsi directory of your > QMS source directory. > > Follow the instructions about the installation of the mingw64 package > and install this package > (I remember that I had some trouble when using msys from mingw64 - I > had to install msys separately and used > this msys successfully - this may relate to the remark in > "COPYFILES.BAT": "in my installation originally at > C:\msys\opt\windows_64\bin") > > Adapt the following part of build_routino.bat: > > rem Section 1.) Environment variables > rem ROUT_SRC_PATH: location of the routino sources (svn or > extracted from archive) > set ROUT_SRC_PATH="M:\src\routino" > rem ROUT_PKG_PATH: directory where to store deplyment artifacts > rem such as compiled binaries, header files, xml configuration files > set ROUT_PKG_PATH="M:\src\routino_pkg" > rem add mingw64 toolchain to PATH > set PATH=C:\msys\bin;%PATH% > set PATH=C:\msys\opt\windows_64\bin;%PATH% > > Run build_routino.bat > - plenty of warnings > > QMS part (used version: qmapshack-1.6.0.tar.gz) > CMake: > if source code and build directories are correct, check if also > correct "Visual Studio 12 2013 Win64" compiler setting > remove source code and build directories if directories or compiler > type are wrong > select source code and build directories, click "Configure", in the > next pop-up window select "Visual Studio 12 2013 Win64" > and "Use default native compilers", click "Finish" > set correct directories (use Qt5.5 and msvc2013_64) - requires > recursion! Be careful! Don't use backslashes in directories - they may > result in > compilation errors! > > Is Zlib required - if so then this branch should be added to the > instructions. Otherwise hint: "Leave zlib entry as it is" > > Set CMAKE_BUILD_TYPE to "Release" > What is the meaning of CMAKE_INSTALL_PREFIX? > > When "Configure" runs without errors click "Generate" > > Open the generated build\QMapShack.sln with VS2013 using the file > context menu > > Compilation: > some warnings in gis\fit part and elsewhere > still routino version problem in CAbout.cpp (strange - should > have been corrected? I used some fixed string to cope with the problem.) > > Create installer part: > - not done > - copyfiles.bat: I removed the quotes in the set statements at the > begin of the script. Looks better for me, but I don't know the syntax > rules here! > > Question: > > If I compile everything as described and build the FILES directory at > the end without wanting an installer I have a lot of DLL's twice on my > machine. > Would it be possible to define some environment variables (or simply > extend PATH) > so that QMS can use DLL's already stored in the Qt5.5/Routino/... > directories? (I'll chack this by myself later on). > > > Have a nice weekend > > > Best regards > > Wolfgang > > ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Qlandkartegt-users mailing list Qlandkartegt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
