I've created this ticket to track the process:
https://trac.osgeo.org/gdal/ticket/7066
On Mon, Sep 11, 2017 at 8:39 AM, Kurt Schwehr wrote:
> I declare RFC68 passed with the following votes:
>
> Even +1
> Jukka +1
> Daniel +0
> Howard +1
> Kurt +1
>
> I appreciate all the
I declare RFC68 passed with the following votes:
Even +1
Jukka +1
Daniel +0
Howard +1
Kurt +1
I appreciate all the discussion and the non-PSC folks who weighed in. I
will update the RFC and begin staging a pull request targeted for Oct 1 or
shortly thereafter.
-kurt
On Fri, Sep 8, 2017 at
On Fri, 8 Sep 2017, Even Rouault wrote:
If you look at Linux platforms that have not a default C++11-ready compiler (ie
gcc < 4.8) and
are still security maintained, I don't think there are that many. In Ubuntu
world, 12.04 is no
longer security maintained since April or May this year. And
> On Sep 8, 2017, at 3:29 PM, Even Rouault wrote:
>
> If people really need to have recent GDAL on old platforms, they can use
> backported toolchains, hire developers to backport the features they need to
> older branches, etc...
+1 for C++11
Howard
Daniel,
> It's not clear to me that the benefits of the C++11 requirement justify
> the potential trouble for those who have to support platforms with older
> compilers.
I can understand your concerns, and I would personnaly have been fine with
sticking with
oldish C++ as well, but we must
On 2017-09-06 12:14 PM, Kurt Schwehr wrote:
Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote
by the PSC on RFC68: C++11 compilation mode.
The draft is here:
https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
-Kurt
+0
It's not clear to me that the benefits of the
On 7 September 2017 at 18:44, David Strip wrote:
>
> For a while now the Windows dll search order starts with the directory that
> the app was loaded from. This was in response to the "dll hell" phenomenon
> in earlier editions that was created when an app overrode a dll
On 7 September 2017 at 17:59, Joaquim Luis wrote:
> Thanks Even and Mateusz for clarifying this.
>
Thanks to your persistence that helped to dig the issue further :-)
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
On 9/7/2017 9:59 AM, Joaquim Luis
wrote:
And
since more people are probably confused as well I find 16 copies
of api-ms-win-crt-runtime-l1-1-0.dll in my machine that has a
updated Win10 + VS compilers. Among them, those installed by
Thanks Even and Mateusz for clarifying this.
And since more people are probably confused as well I find 16 copies of
api-ms-win-crt-runtime-l1-1-0.dll in my machine that has a updated Win10 +
VS compilers. Among them, those installed by
Firefox
TortoiseSVN
MikTex
VScode
OneDrive
and others
On 7 September 2017 at 11:58, Even Rouault wrote:
>
> I can give you some feedback regarding this.
> [...]
> So I suspect the situation is the following :
>
> * ship the api-ms-win-crt-*.dll next to your binaries and that should work
> everywhere
> * if not shippig the
On jeudi 7 septembre 2017 07:47:40 CEST Mateusz Loskot wrote:
> On 7 September 2017 at 01:01, Joaquim Luis wrote:
> > On Wed, 06 Sep 2017 21:22:18 +0100, Mateusz Loskot
> > wrote:
> >> On 6 September 2017 at 21:53, Kurt Schwehr wrote:
> >>>
On 7 September 2017 at 01:01, Joaquim Luis wrote:
> On Wed, 06 Sep 2017 21:22:18 +0100, Mateusz Loskot wrote:
>> On 6 September 2017 at 21:53, Kurt Schwehr wrote:
>>>
>>> I was just about to write something along the lines that follow, but
On Wed, 06 Sep 2017 21:22:18 +0100, Mateusz Loskot
wrote:
On 6 September 2017 at 21:53, Kurt Schwehr wrote:
I was just about to write something along the lines that follow, but
Mateusz
looks to have more of an understanding.
My best guess was that
On 6 September 2017 at 21:53, Kurt Schwehr wrote:
> I was just about to write something along the lines that follow, but Mateusz
> looks to have more of an understanding.
>
> My best guess was that it is an incomplete install of Windows? e.g.
>
>
I was just about to write something along the lines that follow, but
Mateusz looks to have more of an understanding.
My best guess was that it is an incomplete install of Windows? e.g.
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
I haven't done
On 6 September 2017 at 21:21, Joaquim Luis wrote:
> Kurt,
>
> The Tamas SDKs are not enough as to provide all the dependencies to a GDAL
> Win installation. It miss all those dlls (didn't check if the list is
> complete) that the VS2015/17 builds now depend on. So if one wants to
>
Joaquim,
Please give it another go at explaining what this use case is and the
issues with it. I didn't follow your comments about the need for VS2013.
If users are on a legacy compiler (w.r.t. to C++11), can they not be served
by the 2.2 branch? How does that use case fair with the impending
On 6 September 2017 at 20:18, Joaquim Luis wrote:
> On Wed, 06 Sep 2017 18:34:06 +0100, Mateusz Loskot wrote:
>> On 6 September 2017 at 19:14, Joaquim Luis wrote:
>>>
>>> Wait, does this means that VS2013 will no longer be supported?
>>
>> With
Hi,
I'm not a PSC member, but like to note the great work Kurt has done on
C++11 compilation mode.
I strongly support this RFC.
Best regards,
Dmitry
06.09.17 19:14, Kurt Schwehr пишет:
Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote by
the PSC on RFC68: C++11
On 6 September 2017 at 19:14, Joaquim Luis wrote:
> Wait, does this means that VS2013 will no longer be supported?
With respect, Kurt has been asking for comments for very long time.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
On 6 September 2017 at 19:11, Even Rouault wrote:
> On mercredi 6 septembre 2017 19:04:34 CEST Mateusz Loskot wrote:
>> On 6 September 2017 at 18:58, Andrew Bell wrote:
>> > On Wed, Sep 6, 2017 at 12:14 PM, Kurt Schwehr
Wait, does this means that VS2013 will no longer be supported?
That's awful because I'll have to rebuild all my dependencies and honestly
do not understand what compiler dlls must be distributed with the code
(with VS2013 I only has to ship in 2 dlls) and the last thing I want is to
force
On mercredi 6 septembre 2017 19:04:34 CEST Mateusz Loskot wrote:
> On 6 September 2017 at 18:58, Andrew Bell wrote:
> > On Wed, Sep 6, 2017 at 12:14 PM, Kurt Schwehr wrote:
> >> Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote
On 6 September 2017 at 18:58, Andrew Bell wrote:
> On Wed, Sep 6, 2017 at 12:14 PM, Kurt Schwehr wrote:
>>
>> Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote
>> by the PSC on RFC68: C++11 compilation mode.
>>
>> The draft is
On Wed, Sep 6, 2017 at 12:14 PM, Kurt Schwehr wrote:
> Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote
> by the PSC on RFC68: C++11 compilation mode.
>
> The draft is here:
>
> https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
>
I'm late to the
On mercredi 6 septembre 2017 09:14:10 CEST Kurt Schwehr wrote:
> Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote by
> the PSC on RFC68: C++11 compilation mode.
>
> The draft is here:
>
> https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
+1
Just a comment regarding
Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote by
the PSC on RFC68: C++11 compilation mode.
The draft is here:
https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
-Kurt
>
> > Hi Even,
>
> >
>
> > The new SDK-s have now been added.
>
> >
>
> > Best regards,
>
> >
>
>
28 matches
Mail list logo