Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI Questions #372

Open
rgleason opened this issue Dec 23, 2023 · 6 comments
Open

CI Questions #372

rgleason opened this issue Dec 23, 2023 · 6 comments

Comments

@rgleason
Copy link
Contributor

rgleason commented Dec 23, 2023

Submodule OpenCPN/opencpn-libs For commands see the Instructions at the bottom.

NO NEED TO DO YET

@rgleason
Copy link
Contributor Author

rgleason commented Oct 13, 2024

5.10 is here, should we be doing these?

  • Update to wxWidgets 3.2.2 - Dave says no need to until v5.10
  • Upgrade to API 118 for OpenCPN 5.10
    • Change 1.17 to 1.18 in CMakeLists.txt
    • Change 117 to 118 in [plugin_pi.cpp] around line 91
  • Move from API 117 to API118 with v5.10 not necessary, but desireable Give us improved version numbering. Need to change some code in each plugin.

@jongough
Copy link
Owner

jongough commented Oct 13, 2024

Upgrading testplugin to 118 in version 1.0.308.0. This will require two changes in the CMakeLists.txt file

  • Change the line set(OCPN_API_VERSION_MINOR "17") to set(OCPN_API_VERSION_MINOR "18")
  • Change the line add_subdirectory(opencpn-libs/api-17) to add_subdirectory(opencpn-libs/api-18)

Then the main cpp file will need to be based on 118
change

testplugin_pi::testplugin_pi(void *ppimgr)
:opencpn_plugin_117(ppimgr)

to

testplugin_pi::testplugin_pi(void *ppimgr)
:opencpn_plugin_118(ppimgr)

and in the header file change class testplugin_pi : public opencpn_plugin_117 to `class testplugin_pi : public opencpn_plugin_118'

These should reflect the plugin name not testplugin.

@rgleason
Copy link
Contributor Author

That is a great help, Thank you Jon. I missed a couple of things (got the first and third changes).
What/where is the "header" file with the "class"

@jongough
Copy link
Owner

The plugin header, in FE2's case - testplugin_pi.h, so just look in the requisite header file for the plugin where it defines the plugin class.

@rgleason
Copy link
Contributor Author

Thanks, found it here in your commits . I am rusty!
0f0db24

@rgleason
Copy link
Contributor Author

DONE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants