From: Bertrand C. <bco...@gm...> - 2018-10-19 14:05:01
|
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. Le jeu. 18 oct. 2018 à 12:54, Alan Teeder <ajt...@v-...> a écrit : > I have found the reason for this link error. > > I am doing an out of source build in directory > C:/FlightGear/jsbsim/build64, and > looking in C:/FlightGear/jsbsim/build64/python/devnull.txt I see this :- > > C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.15.26726\bin\HostX86\x64\link.exe > /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO > /LIBPATH:C:/FlightGear/jsbsim/build64\src /LIBPATH:C:\Python36\libs > /LIBPATH:C:\Python36\PCbuild\amd64 "/LIBPATH:C:\Program Files > (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.15.26726\ATLMFC\lib\x64" > "/LIBPATH:C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64" > "/LIBPATH:C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64" > "/LIBPATH:C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.15.26726\atlmfc\lib\x64" > "/LIBPATH:C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Auxiliary\VS\lib\x64" "/LIBPATH:C:\Program Files > (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64" "/LIBPATH:C:\Program Files > (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\VS\UnitTest\lib" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64" > "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\Lib\um\x64" > JSBSim.lib /EXPORT:PyInit_jsbsim > build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python/jsbsim.obj > /OUT:C:/FlightGear/jsbsim/build64/tests\jsbsim.cp36-win_amd64.pyd > /IMPLIB:build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python\jsbsim.cp36-win_amd64.lib > LINK : fatal error LNK1181: cannot open input file 'JSBSim.lib' > > If I copy the file C:/FlightGear/jsbsim/build64/src/release JSSim.lib to > to C:/FlightGear/jsbsim/build64/src , I can then build PythonJSBSim, and > also run the tests. > > All of the tests run, but I get. > 1>The following tests FAILED: > 1> 5 - CheckFGBug1503 (Failed) > 1> 45 - FGLocationTest1 (Failed) > > Hope this helps. > > Alan > _______________________________________________ > Jsbsim-devel mailing list > Jsb...@li... > https://lists.sourceforge.net/lists/listinfo/jsbsim-devel > _______________________________________________ > The JSBSim Flight Dynamics Model project > http://www.JSBSim.org > _______________________________________________ > > |