<div dir="ltr"><div>Gerald,</div><div><br></div><div>There are so many decisions that should be made regarding to either the suggested directions to follow, or the technical details, which might apply for a PSC indeed. </div>
<div><br></div><div>You've meant to prepare something for the developers (something like what I've indended to do with the binaries at <a href="http://www.gisinternals.com/sdk/">http://www.gisinternals.com/sdk/</a>) which is probably different as what the end user would expect. Development SDKs would support to compile all versions especially the latest development version, while the production edition should be based on the latest stable releases. A testing edition would probably be based on the current development or stable branches providing daily built binaries if possible.</div>
<div><br></div><div>Switching from one version to another might also require a policy as upgrading a lower level library may definitely break the upper level binaries. Either the projects or the multiple versions of a specific project may require different versions of the same dependencies that should also be pointed out somewhere. </div>
<div><br></div><div>We (with Jürgen and Paolo) have also been talking about whether to use a freeware compiler edition (like Visual Studio 2010 Express) which doesn't seem to contain x64 support unless a proper Windows SDK is installed or we make our life less painful to let OSGeo to purchase one license of the full version of MSVC 2010 to be installed on the VM. Furthermore we should also evaluate all projects (to be supported by OSGeo) regarding to their need of the compilers/environments for both x86/x64 which should also be installed on the VM. </div>
<div><br></div><div>One other decision should also be made about the suggested scripting environment to be used for automating the compilation, whether to use nmake/batch file/bash whatever and how the compilation process itself will be organized. I'm not sure I can enumerate all possible aspects but we would require quite some negotiation, and to test what works and what not (for each project).</div>
<div>We may also require to tweak / modify the external libraries (adding makefiles of fixing issues) which should also be tracked somewhere.</div><div><br></div><div>Most projects may have scripting interfaces using further dependecies required for the compilation like SWIG/Java/Python/C#. Which Java SDK or SWIG version should be used, which Python version(s) should be supported?</div>
<div><br></div><div>Is that the responsibility of the projects to provide their scripts to control the compilation of their binaries at OSGeo4w. Would that be a requirement to add their OSGeo4w build/install controller scripts along with their sources? </div>
<div><br></div><div>Some projects may not support MSVC builds do they require a completely different framework (ie. msys/mingw) which can or cannot work along with the MSVC based dependencies or we force the project to author their nmake or cmake based makefiles as a prerequisite to be included in OSGeo4w?</div>
<div><br></div><div>We should also make sure whether the licensing model of a project (or dependency) allows or denies the inclusion of that in OSGeo4w.</div><div><br></div><div>And so on.... (anyone is welcomed to add further experiences or ideas) </div>
<div><br></div><div><br></div><div>Best regards,</div><div><br></div><div>Tamas</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/21 Fenoy Gerald <span dir="ltr"><<a href="mailto:gerald.fenoy@geolabs.fr" target="_blank">gerald.fenoy@geolabs.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alex,<br>
thanks a lot for such kind of answer.<br>
<br>
In fact what I have in mind is more to provide a "build suite", I definitely don't know how to name it.<br>
<br>
Anyway, let say something that make you able to download this or that software and which will make sure that you will get everything required to build this specific project installed in your OSGeo4W environment. I think of cmake or mingw for instance.<br>
<br>
I think about a tool which let you set some parameters where you can define the compiler version you want to use (or the path to the script which setup environment variables, we may also think of adding some optional command line options to this batch script (if required but, I'm pretty sure it is required).<br>
<br>
This way, you choose one software you want to build from source from the OSGeo4W, then all the dependencies will be setup (packages in their dev versions), the required tools are setup (if not already setup as another software requirement) then the build is done from the OSGeo4W installer. Obviously, the source code should still be available after the build finished. If we can provide such a thing it means that you can apply after build finish the patches you want to apply on one software before building it again with fixes.<br>
<br>
I think it may be a great gain of time for Lazy Developers, as I am.<br>
<br>
I hope my answer is clear enough this time.<br>
<br>
Best regards,<br>
<br>
Gérald Fenoy<br>
<a href="http://www.osgeo.org" target="_blank">http://www.osgeo.org</a><br>
<br>
<br>
Le 21 sept. 2013 à 02:01, Alex Mandel <<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a>> a écrit :<br>
<div class="HOEnZb"><div class="h5"><br>
> On 09/20/2013 05:33 PM, Dave Patton wrote:<br>
>> On 2013/09/20 16:39, Alex Mandel wrote:<br>
>><br>
>>> Unlike OSGeoLive we can't supply VMs as that takes paid licenses for<br>
>>> the software in question.<br>
>><br>
>> Alex - could you please clarify what you mean by this statement.<br>
>><br>
>> Thanks<br>
>><br>
><br>
> We can't give out Windows Virtual Machine(VM) images with Visual Studio<br>
> already installed. The Licensing terms of Windows and Visual studio<br>
> don't allow for that, even if the end user has a valid license its<br>
> probably not legal. The only exception might be if we make a Windows<br>
> Azure image that can be cloned on that platform, since I believe paying<br>
> for an Azure instance automatically gives you the Windows License.<br>
><br>
> Which is different from Ubuntu (what we build OSGeoLive on top of), free<br>
> and open source software that is gratis too. We can build derivates all<br>
> we want and hand them out.<br>
><br>
> Were you thinking I meant something else?<br>
><br>
> What we can do is create an installer or scripts that makes it easier to<br>
> deploy a build environment on top of an already installed Windows, I<br>
> defer this back to being a subcomponent of osgeo4w.<br>
><br>
> Thanks,<br>
> Alex<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" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><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" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br></div>