Am Mittwoch, 30. November 2016 um 10:48:03, schrieb Scott Kostyshak <[email protected]> > On Wed, Nov 30, 2016 at 04:10:38PM +0100, Kornel Benko wrote: > > > Selected parameters in prefTest.pl will remain until next call to > > prefTest.pl. > > The call sequence could be: > > # prefTest.pl ... > > # ctest ... (this is the same as prefTest.pl with previous params) > > # ctest ... > > ... > > # prefTest.pl (with new values) > > # ctest ... > > Ah I see. So by default we would configure CMake to automatically run > prefTest.pl to point to the preferences file that allows knitr to run > without error. So we would still be able to do: > > cmake > make > ctest
It will work this way too, yes.
What I have in mid is:
# cmake
Now the file prefTest.pl is in the build directory, so you
could immediately use
# prefTest.pl use_converter_needauth_forbidden�lse
use_converter_needauth�lse -j3 -R export
> and knitr and Sweave would have successful exports.
>
> Then if we wanted to e.g. run the tests with different preferences we
> could do:
>
> prefTest.pl (with new values)
> ctest ...
Yes
> If I understood correctly, that seems good to me.
>
> Scott
Like the attached. (prefTest.pl.in goes into lib/scripts, executable flags
should be set)
Kornel
prefTest.pl.in
Description: Perl program
diff --git a/lib/scripts/CMakeLists.txt b/lib/scripts/CMakeLists.txt
index a9439b7..d39e4fb 100644
--- a/lib/scripts/CMakeLists.txt
+++ b/lib/scripts/CMakeLists.txt
@@ -9,4 +9,5 @@ if (UNIX)
set(_project "scripts")
# include(../PyCompile)
endif()
+configure_file("${CMAKE_CURRENT_SOURCE_DIR}/prefTest.pl.in" "${CMAKE_BINARY_DIR}/prefTest.pl" @ONLY)
signature.asc
Description: This is a digitally signed message part.
