Skip to content

Windows x64 builds #482

Open
Open

Description

@TwoCanPlugIn

In circleci-build-msvc-64.bat,

There is no need for:

wget https://sourceforge.net/projects/opencpnplugins/files/opencpn.lib
wget https://download.opencpn.org/s/oibxM3kzfzKcSc3/download/OpenCPN_buildwin-4.99a.7z
7z x -y OpenCPN_buildwin-4.99a.7z -o..\buildwin

as they are x86 libraries.

And quite possibly unnecessary for x86 builds as the libraries are now in the git submodule opencpn-libs.

Activity

  1. jongough commented on Oct 22, 2026

    @jongough
    Owner

    These two lines have now been removed.
    I have not done a runtime test yet as still setting up opencpn on windows for it.

  2. rgleason commented on Oct 25, 2026

    @rgleason
    Collaborator

    Jon, Thanks for your work on this.
    Reading OpenCPN/plugins#1439

    The solution seems simple: we should use x86 for 32-bit plugins and x86_64 for 64-bit. This will match other plugins, use the same xsd schemas and avoid bringing anything new into the ecosystem.

    Thus it appears that we should be using for Windows plugins

    Windows x64 Plugins

    <target>msvc-64</target>   <---EVIDENTLY msvc-x64 IS WRONG  should be msvc-64
    <build-target>msvc</build-target>
    <build-gtk></build-gtk>
    <target-version>10.0.20348</target-version>
    <target-arch>x86_64</target-arch>
    

    Windows x32 Plugins

      <target>msvc-wx32</target>
      <build-target>msvc</build-target>
      <build-gtk><build-gtk />
      <target-version>10.0.20348</target-version>
      <target-arch>x86</target-arch>
    
    
  3. rgleason commented on Oct 25, 2026

    @rgleason
    Collaborator

    How is this working out for api18 builds?

    Some flatpak builds fail due to missing #include #52
    OpenCPN/opencpn-libs#52
    Alec says changing old api118 is kind of "scary".
    And I just see that he closed your PR.

    1. Plugins on older API s like 1.18 need to add #include before including ocpn_plugin.h
    2. From 1.20 all is fine, the include is not longer necessary.

    So our choice is to upgrade API to 1.20 or insert the #include.
    Where do we have to add the #include, exactly?

    The inconsistencies do pile up. Will we ever remember this in future years? Will we need to?

  4. rgleason commented on Oct 29, 2026

    @rgleason
    Collaborator

    @jongough
    Jon, I am looking at making a PR from your Testplugin, thinking it would include win_x64 bit builds, but it does not appear to have those.
    I need to rebuild Climatology for 64bit so that we can test WR x64 bit.

    Can you advise? - I could just build with my changes which will make x64 plugins, but we will want to build all the other plugins too.
    Incidentally, it appears that the msvc-64 has been added to PImanager now. https://www.cruisersforum.com/forums/f134/weather-routing-100060.html#post4106487
    I will try it to confirm that it does work properly.

  5. jongough commented on Oct 30, 2026

    @jongough
    Owner

    My version, which I have working against OCPN with wxW 3.3.4, is in the update branch. I haven't moved it to master as I am not sure OCPN is stable enough yet.

    This version builds the windows installable. It 'should' work for all the other supported environments, but I haven't checked it yet. Been busy working on OD to get it compatible with GCC 15 which has invalidated WX_DEFINE_LIST/WX_DECLARE_LIST, which is used all over the place in the plugin. I have it working, but there are still a few edge conditions created by the change that I am fixing up. After that I will look at doing more with FE2.

  6. rgleason commented on Oct 30, 2026

    @rgleason
    Collaborator

    Paul has Celestial_Navigation x64 installing and working in Windows x64 Opencpn using msvc-64!!
    rgleason/celestial_navigation_pi#391

    Seems stable to me.

    PS: See change above #482 (comment)

  7. jongough commented on Oct 30, 2026

    @jongough
    Owner

    The version of FE2 should be 1.0.365.0.

  8. rgleason commented on Oct 31, 2026

    @rgleason
    Collaborator

    Thanks Jon,

    Do I understand correctly that TestPlugin 1.0.365.0. will build msvc_x86 and msvc_64?

    We are slowing assembling the msvc_64 Plugin Tools

    1. Weather_Routing
    2. xGrib or Grib
    3. Climatology (paul's or mine older one)
    4. We need Ocpn_Draw to create inclusion and exclusion zones for Routing.

    Do you think you could find time to accomplish that too?
    Thanks
    Rick

    @pob220

  9. jongough commented on Oct 31, 2026

    @jongough
    Owner

    I have commented out all builds apart from the msvc x64 build as that is what was being tested. The other builds have not been touched. I do not know if the older build will work on the newer windows OCPN as I haven't tried it.

    I have done a first pass on OD and most of it is working on Linux. I have tried a circleci build and identified some other issues which I am working on at the moment. The main one being the deprecation/non-working of the old WX_DEFINE/DECLARE_LIST which has to be replaced with C++ std::list type constructs (there is a lot of that in OD!). I am hoping to have an alpha working version in the next couple of days, but.....

  10. rgleason commented on Oct 31, 2026

    @rgleason
    Collaborator

    The msvc_64 builds now work in PImanager which is very helpful.

  11. jongough commented on Nov 1, 2026

    @jongough
    Owner

    There is now a working version of OD 1.11.0.1 in the ocpn_draw_pi alpha cloudsmith repository. It can be loaded by downloading the zip file and importing it through the plugin manager. I have tested it with the current alpha of testplugin on a virtual windows 10 machine using OCPN 5.15 and it seems to work with both the json and binary API.

  12. rgleason commented on Nov 1, 2026

    @rgleason
    Collaborator

    Thanks Jon, will try it out with WR and WD.

    I've made some scripts to manage CS Opencpn workspace.
    See OpenCPN/plugins#1460

    If you download and use the more current version opencpn_5.15.0-0+d2efbdb you should be able to use PImanager. Catalog

  13. rgleason commented on Nov 3, 2026

    @rgleason
    Collaborator

    Jon, I am curious, does Paul need to build 17 os?
    OpenCPN/plugins#1472 (comment)
    Which ones are not really needed?

  14. jongough commented on Nov 3, 2026

    @jongough
    Owner

    As far as I know FE2 is currently building for all supported environments. The number of environments is determined by OCPN itself. When OCPN moves to wx 3.3.4 the number of builds 'may' decrease.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions