<div dir="auto">I actually looked into WSL and WSL2 but its intended use is command line executables which is not the case for QGIS. I read somewhere that you can run GUI apps from WSL by using a third party X server (you can think of it as a remote display application) but it's kinda inefficient and I think it will require more work than what you'll need if you just switch to linux. <div dir="auto"><br></div><div dir="auto">If after trying you didn't get anything working on Windows and ended up having to switch to linux. I recommend KDE environment (I'm using Kubuntu). I was using windows for everything until 3 months ago and KDE UI made the transition much easier for me.</div><div dir="auto"><br></div><div dir="auto">Best wishes,</div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 5, 2020, 8:20 AM Charles Dixon-Paver <<a href="mailto:charles@kartoza.com" target="_blank" rel="noreferrer">charles@kartoza.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If you are wanting to use Linux functionality directly within Windows 10, Microsoft has introduced Windows Subsystem for Linux. If you're having trouble with Visual Studio but want to stick with Windows it's perhaps a feasible solution.<div><br></div><div><a href="https://docs.microsoft.com/en-us/windows/wsl/about" rel="noreferrer noreferrer" target="_blank">https://docs.microsoft.com/en-us/windows/wsl/about</a><br></div><div><br></div><div>Regards</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 5 Aug 2020 at 01:50, BELGACEM NEDJIMA <<a href="mailto:gb_nedjima@esi.dz" rel="noreferrer noreferrer" target="_blank">gb_nedjima@esi.dz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hi,<div dir="auto">Here is some explanation about making .sln files for QGIS project.<br><div dir="auto">QGIS uses CMake to generate the .sln file. Ideally in a simple CMake project you run CMake where the CMakeFiles.txt is located (usually at the root of the source tree) and provide paths to the external libraries you use the you generate .sln files and build the project normally but since QGIS uses a lots of libraries some of them don't support Visual Studio well and you end up having some really complicated error messages.</div><div dir="auto">About 3 months ago I tried to use visual studio 2019 and changed somethings in the build script. I managed to generate solution files but QGIS couldn't compile. I ended up having to switch to linux.</div><div dir="auto">I hope you find a solution soon.</div></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Aug 4, 2020, 10:48 PM <<a href="mailto:tomjan@gmx.com" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">tomjan@gmx.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Ismail and thank you for your link to the pull request.<br>
Currently that PR has not been accepted, because of some checks not being successful.<br>
<br>
I do not really know exactly what that pull request is trying to do (but as many as 42 files seem to be involved in the PR) but as far as I can see it does not include a ".sln" file (Visual Studio solution file) nor any ".vcxproj" files (Visual C++ project files) nor a file "packages.config" (for NuGet managed libraries).<br>
<br>
I think I read somewhere here in the QGIS developer list archive that someone estimated that 90% percent of the QGIS developers are using Linux.<br>
If that is true then I believe the reason might be that Windows developers (which are used to NuGet and Visual Studio solutions files and project files) may choose to give up when they feel it seems difficult to even get started with the development environment for QGIS with Windows.<br>
<br>
Can anyone answer this question:<br>
Would it, for some reason, be impossible to provide a Visual Studio solution file (and .vcxproj files) that can simply be opened, and then the required dependencies would be retrieved automatically with NuGet (according to NuGet references in the ".vcxproj" files or "packages.config") ?<br>
One obvious reason could be that there may be some required libraries which are not available through NuGet but those kind of files therefore really will need a manual installation.<br>
But I mean is it possible to provide easy instructions with only very FEW manual installations for Windows, and then the majority of the dependencies would be retrieved through NuGet when you open a Visual Studio solution file which hopefully would be available from the github repository?<br>
<br>
The only kind of libraries I myself have used with NuGet is .NET libraries but as far as I understand, NuGet can also be used for native C++ libraries:<br>
<a href="https://devblogs.microsoft.com/nuget/native-support/" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://devblogs.microsoft.com/nuget/native-support/</a><br>
<br>
I believe that the QGIS project would get more contributors if you can provide a development environment that are EASY to GET STARTED WITH for potential newcomers using Windows Visual Studio.<br>
<br>
- - - - - - - - - - - - - - - - - - <br>
<br>
<br>
Sent: Tuesday, August 04, 2020 at 12:22 AM<br>
From: "Ismail Sunni" <<a href="mailto:imajimatika@gmail.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">imajimatika@gmail.com</a>><br>
To: <a href="mailto:tomjan@gmx.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">tomjan@gmx.com</a><br>
Cc: "QGIS Developer List" <<a href="mailto:qgis-developer@lists.osgeo.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">qgis-developer@lists.osgeo.org</a>><br>
Subject: Re: [QGIS-Developer] How to setup Visual Studio 2019 environment for QGIS C++ development?<br>
<br>
Hi Tomjan,<br>
<br>
Perhaps you want to see this PR <a href="https://github.com/qgis/QGIS/pull/38102" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://github.com/qgis/QGIS/pull/38102</a> for your question.<br>
Best regards<br>
<br>
<br>
On Mon, Aug 3, 2020, 23:44 <<a href="mailto:tomjan@gmx.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">tomjan@gmx.com</a>[mailto:<a href="mailto:tomjan@gmx.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">tomjan@gmx.com</a>]> wrote:<br>
<br>
I would be interested in learning to contribute to QGIS.<br>
My previous C++ experience is that about 20 years ago I did some (for a couple of years) Visual C++ programming with Microsoft's MFC as the GUI.<br>
Now I think I could refresh my C++ skills and also learn QT which I have never programmed with so far.<br>
<br>
However, I am not a Linux user, but always have been using Windows (currently Windows 10).<br>
It seems to be a complicated obstacle to get started running QGIS through Visual Studio 2019.<br>
<br>
I think it would be great with a tutorial (webpage or youtube video tutorial) about how to get started with an example showing how to do all necessary installations/configurations/setup until you can compile and run QGIS with a breakpoint in Visual Studio 2019.<br>
<br>
I have seen that the "INSTALL" file in the repository refers to Visual Studio 2015, but it seems awkward if it really would be necessary to use such an ancient version?<br>
Is nobody of the QGIS developers using Visual Studio 2019?<br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a>[mailto:<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a>]<br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer%5Bhttps://lists.osgeo.org/mailman/listinfo/qgis-developer%5D" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer[https://lists.osgeo.org/mailman/listinfo/qgis-developer]</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer%5Bhttps://lists.osgeo.org/mailman/listinfo/qgis-developer%5D" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer[https://lists.osgeo.org/mailman/listinfo/qgis-developer]</a><br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>
</blockquote></div>