Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Le mar. 6 nov. 2018 à 11:32, Alan Teeder <ajt...@v-...> a écrit :

>
>
> *From:* Bertrand Coconnier
> *Sent:* Friday, November 2, 2018 1:15 AM
> *To:* Development issues
> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>
> Le mer. 24 oct. 2018 à 21:04, Alan Teeder <ajt...@v-...> a
> écrit :
>
>>
>>
>> *From:* Bertrand Coconnier
>> *Sent:* Friday, October 19, 2018 3:04 PM
>> *To:* Development issues
>> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>>
>> Hi Alan,
>>
>> Thanks for the feedback.
>>
>> Could you please modify the file python/setup.py.in as described below
>> and restart the build process from scratch (i.e. in a new directory) ?
>>
>> python/setup.py.in
>> @@ -62,7 +62,7 @@ setup(
>>
>> os.path.join('${CMAKE_SOURCE_DIR}',
>>                                                        'python')],
>>
>> library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
>> -                                                      'src')],
>> +                                                      'src/release')],
>>                             language='c++')])
>>
>> # Build process for the fpectl module (but don't install !!!)
>>
>> Let me know if the compilation succeeds in that case.
>>
>> Regarding the failed tests, could you please re-run them with the command
>> below and investigate if some errors are reported in the file
>> C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?
>>
>> > ctest -I 5,45,40
>>
>> Bertrand.
>>
>> -----------------------
>>
>> Betrand
>>
>> It compiles OK now (release build only of course), and I can run the test
>> suite from within the Visual Studio gui.
>>
>> However I do not know how to run the tests using the ctest command. I
>> assume that I have to be in a directory which contains the ctest executable
>> – but do not know where that is.
>>
>> Alan
>>
>
> Hi alan,
>
> I just pushed a commit to JSBSim which should fix the issue you reported.
> Now you should no longer need to modify manually python\setup.py for the
> test suite to build successfully.
>
> Regarding the command ctest -I 5,40,45, it should be launched from C:/FlightGear/jsbsim/build64/.
> The executable ctest.exe is part of the CMake package.
>
> Regards,
>
> Bertrand.
>
> ------------------------------
>
> Bertrand
>
> I have just rebuilt JSBSim with the latest git version, and then ran this
> test
>
> C:\FlightGear\jsbsim\build64> ctest -I 5,40,45
> Test project C:/FlightGear/jsbsim/build64
>     Start 5: TestActuator
> 1/1 Test #5: TestActuator .....................***Failed    0.68 sec
>
> 0% tests passed, 1 tests failed out of 1
>
> Total Test time (real) =   0.72 sec
>
> The following tests FAILED:
>           5 - TestActuator (Failed)
> Errors while running CTest
>
>
> Alan
>

Alan,

Should I understand that you can now build the Python tests without the
manual modification of setup.py.in ?

Regarding the test that fails, you should be able to get more details about
its failure by adding the -V tag to the command line

> ctest -I 5,40,45 -V

Bertrand.