Closed tdhock closed 4 years ago
Displaying a message when the user is unable to compile the codes. checking for deepstate test harness files and makefiles and as well as checking for the TestHarness executable generation and reports the user with a message saying the couldn't compile the testharness.
> deepstate_harness_compile_run("/home/akhila/R/binsegRcpp")
[1] "/home/akhila/R/binsegRcpp/inst/testfiles/rcpp_binseg_normal/Makefile"
TestHarness and makefile doesn't exist for - rcpp_binseg_normal
[1] "/home/akhila/R/binsegRcpp/inst/testfiles/rcpp_binseg_normal_cost/Makefile"
TestHarness and makefile doesn't exist for - rcpp_binseg_normal_cost
[1] "Issue compiling the function - rcpp_binseg_normal"
[2] "Issue compiling the function - rcpp_binseg_normal_cost"
are you using print? you should use message or warning instead.
this is related to #30 in which deepstate test harness compilation says that compilation worked, but actually it did not because the test harness had not yet been generated.
you should also add code to handle (and a test case) packages with code that does not compile for whatever reason. Here is an example of some code for which linking fails but success is reported.
You should stop as soon as one of those compilation commands fails, so the user knows he needs to fix that.