Here is a patch that incorporates mingw/msys run via "MSYS Makefiles"
generator to obtain
the system name via "uname -s".
On Fri, Aug 7, 2015 at 4:45 PM, Greg Jung wrote:
> On Fri, Aug 7, 2015 at 1:16 PM, Brad King wrote:
>> > On 08/07/2015 05:25 AM, Ray Donnelly wrote:
>> >> CMake needs to be
Chris Bieneman wrote:
> One big things I’m working on is improving the way we build our runtime
> libraries. These libraries are built for the targets that the compiler
> supports generating code for, so they can use different architectures,
> headers, and libraries than are used to build the comp
>
> On Fri, Aug 7, 2015 at 1:16 PM, Brad King wrote:
> > On 08/07/2015 05:25 AM, Ray Donnelly wrote:
> >> CMake needs to be able to identify MSYS2 distinctly from both MINGW and
> MSYS
> >> first. Would a patch making that distinction be acceptable to CMake?
> > Yes, I think that makes sense sinc
>
> > I have two changes in FindPythonLibs that should make for less failure
> in
> > the MINGW/MSYS camp.
>
> While I support this stuff, I think for it to not
> break other people (who use either mingw.org/MinGW-w64 compilers or
> the old MSYS with 'normal' Windows CPython),
If there is not a
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15690
==
Reported By:Clinton Stimpson
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15689
==
Reported By:James Johnston
Assigned To:
Please find attached two patches which allow these libraries to detect
debug versions of the libraries on Windows. I copied the behaviour from
the PNG module as suggested on #cmake.
Kind regards,
Roger Leigh
0001-FindTIFF-Find-debug-libraries.patch
Description: Binary data
0001-FindXercesC-Fi
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15688
==
Reported By:bburgerm
Assigned To:
On Fri, Aug 7, 2015 at 2:21 PM, Brad King wrote:
> On 08/07/2015 08:33 AM, Ray Donnelly wrote:
>> Finally, there's the consideration as to whether "MSYS2" implies you
>> are using just the minimum amount of the MSYS2 shell or whether you've
>> gone all-in with MSYS2
>
> CMAKE_SYSTEM_NAME should re
On 08/07/2015 08:33 AM, Ray Donnelly wrote:
> Finally, there's the consideration as to whether "MSYS2" implies you
> are using just the minimum amount of the MSYS2 shell or whether you've
> gone all-in with MSYS2
CMAKE_SYSTEM_NAME should refer to the target application environment.
If you're build
On Fri, Aug 7, 2015 at 1:16 PM, Brad King wrote:
> On 08/07/2015 05:25 AM, Ray Donnelly wrote:
>> CMake needs to be able to identify MSYS2 distinctly from both MINGW and MSYS
>> first. Would a patch making that distinction be acceptable to CMake?
>
> Yes, I think that makes sense since the MSYS2
On 08/07/2015 05:25 AM, Ray Donnelly wrote:
> CMake needs to be able to identify MSYS2 distinctly from both MINGW and MSYS
> first. Would a patch making that distinction be acceptable to CMake?
Yes, I think that makes sense since the MSYS2 environment is distinct
from Windows, MinGW, MSYS, and Cy
Hi developers and experts OpenSSL!
I added a little boring and dense of code at the end FindOpenSSL.cmake module.
I just want to have imported the OpenSSL library for creating relocatable
packages.
I created a theme topic-imported-openssl on my server:
http://git.podsvirov.pro/?p=kitware/cmake.g
On 07-Aug-15 11:31, Gregor Jasny wrote:
Hi,
On 07/08/15 00:43, Ruslan Baratov via cmake-developers wrote:
Hi,
I'm thinking about fixing bug
http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper
in CMake internals just want to ask is there any work-in-progress
attempts already
On Fri, Aug 7, 2015 at 7:58 AM, Greg Jung wrote:
> Hi there,
> A patch for review:
>
> I have two changes in FindPythonLibs that should make for less failure in
> the MINGW/MSYS camp.
I think you explicitly mean the MSYS2 camp here. We have our own
Pythons (4 of them, 2 native and 2 cygwin-y)
Hi,
On 07/08/15 00:43, Ruslan Baratov via cmake-developers wrote:
Hi,
I'm thinking about fixing bug
http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper
in CMake internals just want to ask is there any work-in-progress
attempts already or hints/directions of how it can be done
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15687
==
Reported By:Adn
Assigned To:
Hi,
New version of patch attached.
I added a check on java tool to execute test only if java and shared library
built by test have same architecture (32 or 64bit).
Marc
On 05/08/15 17:49, "Brad King" wrote:
>On 08/05/2015 03:15 AM, CHEVRIER, Marc wrote:
>> For point 2., The best approach
18 matches
Mail list logo
