<HTML dir=ltr><HEAD><TITLE>Re: R: R: [GRASS-dev] GRASS-6.3.0RC4 Windows Native Binary (MSYS) Build Errors</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR><BASE href=http://mailstore.rossoalice.alice.it/exchange/Alice000000001264700/Bozze/R:%20R:%20R:%20[GRASS-dev]%20GRASS-6.3.0RC4%20Windows%20Native%20Binary%20(MSYS)%20Build%20Errors.EML/1_text.htm></HEAD>
<BODY>
<DIV id=idOWAReplyText39472 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Hamish,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2><FONT face="Times New Roman">>Note Cygwin+GRASS works well if you need to run on Windows in a stable<BR>>way. Of course helping to test the experimental native build is most<BR>>welcome too.</FONT></FONT></DIV><FONT face=Arial size=2><FONT face="Times New Roman"></FONT></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>
<DIV dir=ltr><BR>Yes, I read about it, but I agree that Windows Native Binary compiled using MinGW32 should be the right way.</DIV>
<DIV dir=ltr>Now I need to let things (I need) work in grass, intented as plugin in qgis.</DIV>
<DIV dir=ltr>I'm completing qgis building; later I will approach grass building as "standalone" application (so with TclTk and other stuffs not needed for grass-in-qgis use only);</DIV>
<DIV dir=ltr>I hope to give help in building and source code bug fixing... but I cannot be helpful in application testings, because, actually, I'm not a "full" grass user</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Regards,</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Marco</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>PS: I think that including Windows API lots of problems could be fixed, changing functions like alarm(), fork(), wait()... in the source code, with their equivalents avaible in Windows API. Is there possible to make a conditional structure in order to determinate which build platform is in use? in the way to let gcc determinate which header/function it should include/compile?</DIV></FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Da:</B> Hamish [mailto:hamish_b@yahoo.com]<BR><B>Inviato:</B> ven 25/01/2008 2.52<BR><B>A:</B> marco.pasetti@alice.it; Moritz Lennert; grass-dev@lists.osgeo.org<BR><B>Oggetto:</B> Re: R: R: [GRASS-dev] GRASS-6.3.0RC4 Windows Native Binary (MSYS) Build Errors<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>marco.pasetti wrote:<BR>> I'm an engineering student and I'm making an experimental thesis on<BR>> solar radiation and mathematic models simulating transitory<BR>> functioning of solar cells (photovoltaic); I approached GIS few weeks<BR>> ago only to know how to determinate horizon lines starting from<BR>> elevation data and a given GPS point (I need that to carefully<BR>> compare my model results with real measured data); so, I discovered a<BR>> big and deep world (have you ever heard to pandora's box myth?)... I<BR>> also discovered that JRC developed a GRASS module called r.horizon<BR>> that it's perfect for my purpose... even if it's not included in<BR>> current grass distribution. I looked for sources and informations on<BR>> how to build executables for windows; I even installed linux (ubuntu<BR>> 7.10, dual boot with xp pro) on my machine, to let it work easily....<BR>> but, for many reasons, I need it on windows... so.. here I am! at<BR>> this stage I already built r.horizon (and r.sun2 module, also from<BR>> JRC) without errors... but I want to continue because I think that,<BR>> if you (developer community) have been so kind in writing wikies and<BR>> replay to mails, I must replay with tryng to do my job too... ;-)<BR><BR>Note Cygwin+GRASS works well if you need to run on Windows in a stable<BR>way. Of course helping to test the experimental native build is most<BR>welcome too.<BR><BR><BR>Hamish<BR><BR><BR><BR> ____________________________________________________________________________________<BR>Be a better friend, newshound, and<BR>know-it-all with Yahoo! Mobile. Try it now. <A href="http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ">http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ</A><BR><BR><BR></FONT></P></DIV></BODY></HTML>