Replies: 4 comments 7 replies
-
|
By searching for some informations, now I solved the "g++: error: wsock32.lib: No such file or directory"and "g++: error: ws2_32.lib: No such file or directory" problem. But things got worse，when I run mex command I get these errors: I will continue to work on this problem, but is there something I missing? I am so confused right now. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In terms of your initial Visual Studio 2017 linker errors:
So I'm guessing you're not rebuilding the whole of JSBSim with VS2017, rather when building the S-Function you're linking against some pre-built JSBSim libraries that are built using VS2019. So I see two options. Grab the JSBSim repo and build everything using VS2017 or install VS2019. |
Beta Was this translation helpful? Give feedback.
3 replies
-
@WangKeji I agree with @seanmcleod. In alternative I would install the latest Visual Studio Community Edition and build everything with it. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, option 3 is to build everything using VS2022, i.e. the latest version of VS.
The one thing I'm not 100% sure of is what the compatibility matrix is between Matlab R2021b and VS versions. |
Beta Was this translation helpful? Give feedback.
-
|
I uninstall VS2017 and install VS2019. Then I install Matlab R2020b.Now everything works perfectly! Thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
|
At the moment our GitHub Actions workflows pick the latest version for windows (i.e. jsbsim/.github/workflows/cpp-python-build.yml Lines 199 to 205 in 59389f6 jsbsim/.github/workflows/cpp-python-build.yml Lines 349 to 352 in 59389f6 According to the GitHub Actions docs, this means that we are currently compiling the library In order to avoid other users to stumble upon the same issue, I guess we need to:
|
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
But those commits are contradictory right? The readme commit says VS2022 but the github action commit changes from latest to 2019? |
Beta Was this translation helpful? Give feedback.
-
I hope not 😄 We are now building again with MSVC 2019 but the last release So I modified the workflow to build with MSVC 2019 (commit 6aaee6b) and the |
Beta Was this translation helpful? Give feedback.
-
|
And hopefully, the workflow will automatically update the MSVC version in |
Beta Was this translation helpful? Give feedback.
-
Yep, especially for users who don't download the repo and build everything themselves, which seems to be quite common for those users wanting to build the Matlab S-Function only.
Well V2022 was released Nov 8 2021, so maybe not so bleeding edge anymore, it's roughly 7 months old already 😉 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there！Recently I am trying to use JSBSim with Simulink. I have tried for many times following what said in README.md, but it doesn't work. My matlab version is R2021b, C++ complier is Visual Studio Community 2017, and I have tried JSBSim version 1.1.11 and JSBSim version 1.1.10.
I followed all the steps but still arrived at some errors:
If I choose to use MinGW64 Compiler with Windows 10 SDK or later (C++) as my compiler, the error will be:
I am totally a new guy on matlab compile...any assistance you can provide would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions