Find one minor correction to my previous post below.
On Jan 23, 2014, at 1:11 PM, Andreas Schuh <[email protected]> wrote:
> For example, in case of Python, you can “wrap” the script and have it act as
> both Windows NT Script and Python script by adding the following line at the
> top
>
> @setlocal enableextensions & "/path/to/required/python/version" -x "%~f0" %*
> & goto :EOF
> % Any Python code goes below this line
>
> Python will ignore the first line. In case of Perl, however, you need to do a
> bit more:
>
> @goto = "START_OF_BATCH” ;
> @goto = ();
> % Any Perl code goes in between these lines
> __END__:
> “START_OF_BATCH"
> @“/path/to/required/perl" -w -S "%~f0" %*
>
> As this modified Perl script is no longer valid Perl
>
Actually the neat thing about this added code is that it is both, valid Perl
and valid Windows NT Script syntax. It is thus mostly about wrapping scripts
automatically as well as replacing the path to the found interpreter executable.
Andreas
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
