<div dir="ltr">Hello Radim,<div><br></div><div>Thanks for information.<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 24, 2016 at 2:48 PM, Radim Blazek <span dir="ltr"><<a href="mailto:radim.blazek@gmail.com" target="_blank">radim.blazek@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sun, Feb 21, 2016 at 5:15 PM, Rashad Kanavath<br>
<<a href="mailto:mohammedrashadkm@gmail.com">mohammedrashadkm@gmail.com</a>> wrote:<br>
><br>
> Hello Markus,<br>
><br>
> As this part related to GRASS, I am writing it here.<br>
><br>
> Moving to cmake is one thing. But I don't know if that is blocking msvc<br>
> build. Did anybody tried to build grass with msvc?<br>
<br>
</span>Yes I did, the libs only.<br>
<br>
I started with <a href="https://github.com/swig/cccl" rel="noreferrer" target="_blank">https://github.com/swig/cccl</a> but that was failing<br>
because cl.exe was givin deprecation warning.....<br>
In the end, I managed to compile libs with command (manually changed Makefile):<br>
<br>
cl "-nologo" "-LDd" -Zi "-Fe$@" $(C_SOURCES) $(ALL_CFLAGS) $(ALL_LIBS)<br>
"-link" -DEBUG -OPT:NOREF -DEF:$(LIB_DEF)<br>
"-LIBPATH:c:/users/radim/devel/grass-7.0.0-msvc/dist.i686-pc-mingw32/lib"<br>
"-LIBPATH:c:/users/radim/devel/grass-7.0.0-msvc/dist.i686-pc-mingw32/lib"<br>
"-LIBPATH:/c/OSGeo4W/lib" "-LIBPATH:/c/OSGeo4W/apps/msys/lib"<br>
"-LIBPATH:/c/users/radim/devel/grass-7.0.0-msvc/mswindows/osgeo4w/lib/"<br>
"-LIBPATH:C:/lib/" "-LIBPATH:C:/Program Files (x86)/Microsoft Visual<br>
Studio 10.0/VC/lib/" "-LIBPATH:C:/Program Files (x86)/Microsoft<br>
SDKs/Windows/v7.0A/lib/"<br>
<br>
+ some manual hacks like copy proj_i.lib c to proj.lib, comment<br>
lgamma(), get dirent.h, replace .o by .obj in Grass.make and so on.<br>
<br>
I think that adding support for MSVC to current GRASS build system is<br>
possible, cl.exe is C compiler.<br></blockquote><div><br></div><div>Some of these seems easy to fix when moving to cmake. While there might be trenches.. </div><div><br></div><div>Anwyay I will give a stab on cmake with grass.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Radim<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
> BTW, What will be your opinion on adding an cmake build system?. It can<br>
> ofcourse co-exists with current auto-tools one.<br>
><br>
> On Sun, Feb 21, 2016 at 8:49 PM, Markus Neteler <<a href="mailto:neteler@osgeo.org">neteler@osgeo.org</a>> wrote:<br>
>><br>
>> FYI<br>
>> (ongoing discussion in the other list)<br>
>><br>
>> ---------- Forwarded message ----------<br>
>> From: "Jürgen E." <<a href="mailto:jef@norbit.de">jef@norbit.de</a>><br>
>> Date: Feb 21, 2016 4:14 PM<br>
>> Subject: Re: [OSGeo-Discuss] OSGeo4W maintenance activities<br>
>> To: <<a href="mailto:discuss@lists.osgeo.org">discuss@lists.osgeo.org</a>><br>
>> Cc:<br>
>><br>
>> Hi Markus,<br>
>><br>
>> On Sun, 21. Feb 2016 at 15:47:00 +0100, Markus Neteler wrote:<br>
>> > since I'm not familiar with compilation on Windows, could you briefly<br>
>> > indicate what's needed / which efforts to compile GRASS GIS with MSVC<br>
>> > rather<br>
>> > than mingw given the recent efforts on the 64bit packaging? Just to<br>
>> > better<br>
>> > understand...<br>
>><br>
>> Not sure. I'd probably start with moving the build system to CMake. Like<br>
>> I<br>
>> already did for just the GRASS libraries at some point in the past (some<br>
>> code<br>
>> changes I submitted to make the libraries build with MSVC were also<br>
>> accepted<br>
>> back then).<br>
>><br>
>> But moving all the modules there is probably a much bigger task and I'm<br>
>> also<br>
>> not sure about the acceptance of this. ;)<br>
>><br>
>> It might also be possible to integrate msvc into configure/make (at least<br>
>> I<br>
>> think I've seen configures with MSVC stuff in them). Although you'd still<br>
>> need<br>
>> a unix like shell, make and other tools from mingw/cygwin. But I never<br>
>> explored that option (mainly just because the CMake approach went much<br>
>> better<br>
>> with what I needed for QGIS).<br>
>><br>
>> But again GRASS works fine in OSGeo4W AFAICT (and as you know and that's<br>
>> still<br>
>> not much ;)) and hence I don't see the big problem of mixing MinGW and<br>
>> MSVC<br>
>> DLLs. It doesn't add much to the mess of having different MSVC compilers<br>
>> and<br>
>> runtimes around. IMHO that part of Rashad's issue is just a CMake bug<br>
>> and not<br>
>> a fundamental flaw in OSGeo4W.<br>
>><br>
>><br>
>> Jürgen<br>
>><br>
>> --<br>
>> Jürgen E. Fischer norBIT GmbH Tel.<br>
>> <a href="tel:%2B49-4931-918175-31" value="+49493191817531">+49-4931-918175-31</a><br>
>> Dipl.-Inf. (FH) Rheinstraße 13 Fax.<br>
>> +49-4931-918175-50<br>
>> Software Engineer D-26506 Norden<br>
>> <a href="http://www.norbit.de" rel="noreferrer" target="_blank">http://www.norbit.de</a><br>
>> QGIS release manager (PSC) Germany IRC: jef on<br>
>> FreeNode<br>
>><br>
>> _______________________________________________<br>
>> Discuss mailing list<br>
>> <a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
>><br>
>> _______________________________________________<br>
>> grass-dev mailing list<br>
>> <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
> Rashad<br>
><br>
> _______________________________________________<br>
> grass-dev mailing list<br>
> <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div><font face="arial, helvetica, sans-serif">Regards,<br> Rashad</font></div></div>
</div></div></div>