On 2015-05-15 13:45-0000 Arjen Markus wrote:
> Hi Alan,
>
>
>
> With this minimal CMakeLists.txt file:
>
>
>
> function(plplot_cmake_minimum_required)
>
> cmake_minimum_required(${ARGV})
>
> endfunction(plplot_cmake_minimum_required)
>
>
>
> plplot_cmake_minimum_required(VERSION 3.0.2 FATAL_ERROR)
>
>
>
> I get the following output:
>
> -- The C compiler identification is GNU 4.9.2
> -- The CXX compiler identification is GNU 4.9.2
> CMake Warning at /usr/share/cmake-3.1.2/Modules/Platform/CYGWIN.cmake:15
> (message):
> CMake no longer defines WIN32 on Cygwin!
>
> (1) If you are just trying to build this project, ignore this warning or
> quiet it by setting CMAKE_LEGACY_CYGWIN_WIN32=0 in your environment or in
> the CMake cache. If later configuration or build errors occur then this
> project may have been written under the assumption that Cygwin is WIN32.
> In that case, set CMAKE_LEGACY_CYGWIN_WIN32=1 instead.
>
> (2) If you are developing this project, add the line
>
> set(CMAKE_LEGACY_CYGWIN_WIN32 0) # Remove when CMake >= 2.8.4 is required
>
> at the top of your top-level CMakeLists.txt file or set the minimum
> required version of CMake to 2.8.4 or higher. Then teach your project to
> build on Cygwin without WIN32.
> Call Stack (most recent call first):
> /usr/share/cmake-3.1.2/Modules/CMakeSystemSpecificInformation.cmake:36
> (include)
>
>
>
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++.exe
> -- Check for working CXX compiler: /usr/bin/c++.exe -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /cygdrive/d/tmp/cmake
>
> Whereas calling cmake_minimum_required directly does not produce the message.
Thanks for those key test results which I reported to the CMake list
(a continuation of the thread with the subject line "Chicken and egg problem
with
cmake_minimum_required(...), project(...), and CMAKE_SYSTEM_NAME")
I did get a clarification there from Brad King, that
calling cmake_minimum_required from inside a function is problematic.
I have accordingly (commit id cb528a2) updated our build system so
that the function approach is no longer used to enforce uniform
policy. Instead, I now simply call cmake_policy(VERSION 3.0.2) after
every cmake_minimum_required() call to enforce uniform policy.
The new startup logic is considerably simplified from the previous
version, follows everything Brad King has recommended, and works fine
on Linux. So I am virtually positive it will work fine on Cygwin with
no spurious messages. Therefore, I don't think you need to
specifically test this change. Instead, I think you can put off
(implicitly) testing it until the next Cygwin test I will be
requesting when I finish up a possible fix for the Fortran problems
you have encountered for the traditional build on Cygwin.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel
