BSB4 plugin for V5

[Johnk]

Hi


I am looking forward to updating to version 5 but will need this plugin to access my BA charts. Is there a planned date for its issue please?


Regards


John

[rgleason]

What OS please?
Trying to update for ov50 Windows here
https://github.com/rgleason/bsb4_pi

Appveyor fails with one fatal error

LINK : fatal error LNK1181: cannot open input file 'C:\Projects\opencpn\build\release\opencpn.lib' [C:\project\bsb4_pi\build\bsb4_pi.vcxproj]

Part of the way down:

CustomBuild: Building Custom Rule C:/project/bsb4_pi/CMakeLists.txt
CMake does not need to re-run because C:/project/bsb4_pi/build/CMakeFiles/generate.stamp is up-to-date.
VcpkgTripletSelection:
Using triplet "x86-windows" from "C:\Tools\vcpkg\installed\x86-windows\"
Vcpkg is unable to link because we cannot decide between Release and Debug libraries. Please define the property VcpkgConfiguration to be 'Release' or 'Debug' (currently 'release').

A google search on

Vcpkg is unable to link because we cannot decide between Release and Debug libraries. Please define the property VcpkgConfiguration to be 'Release' or 'Debug' (currently 'release')

turns up a problem with wxWidgets file locations for VC

https://github.com/Microsoft/vcpkg/issues/3180
MSBuild integration doesn't work for wxWidgets package
https://github.com/Microsoft/vcpkg/issues/3180
VCPKG was fixed
https://github.com/microsoft/vcpkg/pull/4846


There is also an appveyor note about this
https://help.appveyor.com/discussion...es-include-lib
I do have in the appveyor file
configuration: Release # Debug contains non-redist MS DLLs
but they ask "is 'buildwin.cmd working as intended?"


However the end result is that opencpn.lib is not found.

I don't see how I can fix this. Thoughts:
Perhaps the version of cmake has to be increased and the cmake files changed.

[bdbcat]

Rick...
Why are you using vcpkg? Have you successfully used it before?
Dave

[Johnk]

Hi


My OS is Windows 7 on my boat netbook and Windows 10 on my home laptop.


Regards


John

[rgleason]

Dave,
Never intended to.. that is just the message I found in the appveyor console


1. Forked your repository.

2. Modified another appveyor.yml file that I know works for ov50 and wxWidgets 3.1.2 and commited it.

3. Made no changes to CMAKE files.
4. Appveyor Console
line 70: download of PVW32Con.exe - not needed.

line 119 shows c:\project\bsb4_pi\build\opencpn.lib exists
line 143 cmake -T v141_xp ..
line 159-190 Deprecated policy warnings

line 192 cmakeLists.txt (include)
line 210 -- Generating doneline 211 -- Build files...written to: C:/project/bsb4_pi/build
dir c:\project\bsb4_pi\build
line 245 cmake --build . --target package --config release
line 281 done building project "C:\project\bsb4_pi\build\bsb4-i18n.vcxproj" (default targets)


line 282 PrepareForBuild: line 283 Creating directory "bsb4_pi.dir\Release\".
line 290 CMake does not need to re-run because C:/project/bsb4_pi/build/CMakeFiles/generate.stamp is up-to-date.
line 291 VcpkgTripletSelection: line 292 Using triplet "x86-windows" from "C:\Tools\vcpkg\installed\x86-windows\"
line 293 Vcpkg is unable to link because we cannot decide between Release and Debug libraries. Please define the property VcpkgConfiguration to be 'Release' or 'Debug' (currently 'release').


Which leads to this error?
LINK : fatal error LNK1181: cannot open input file 'C:\Projects\opencpn\build\release\opencpn.lib' [C:\project\bsb4_pi\build\bsb4_pi.vcxproj]

I have absolutely no idea why this version of Microsoft Visual Studio 2017 is doing this except for the google searches below.
I don't know how to fix it yet.


The appveyor file is here

Originally Posted by bdbcat

Rick...
Why are you using vcpkg? Have you successfully used it before?
Dave

[rgleason]

Line 14 in appveyor.yml

"call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars32. bat"

This is necessary to run MSVS 2017 so I cant comment it out.

[rgleason]

I think I have to tell appveyor not to use vcpkg, because their default canned version of MicroSoft Visual Studio 2017 automatically includes it!

https://www.appveyor.com/docs/lang/cpp/

Why haven't we run across this before?

Found this: https://www.appveyor.com/docs/lang/cpp/ look towards the bottom.

"AppVeyor comes with VC++ Packaging Tool pre-installed in C:\tools\vcpkg folder (without integration installed by default)."

[rgleason]

Triplet files https://vcpkg.readthedocs.io/en/latest/users/triplets/

It also has Linux and MacOS triplets

https://vcpkg.readthedocs.io/en/latest/


I believe this is available through appveyor.

[rgleason]

Found this: https://www.appveyor.com/docs/lang/cpp/ look towards the bottom.

"AppVeyor comes with VC++ Packaging Tool pre-installed in C:\tools\vcpkg folder (without integration installed by default)."

Found this in Appveyor.yml
Line 10 [vcvarsall.bat] Environment initialized for: 'x86'

=========


I notice that Leamas is using "x86-windows"

[hoolie]

It seems a very complicated answer to the OP's simple request ... ... ...

[rgleason]

In Appveyor panel settings you can specify what to use.

Choosing image for your builds

If the build configuration does not specify build worker image then Visual Studio 2015 image is used.
You can select a different image on AppVeyor UI (“Environment” tab of project settings) or in appveyor.yml:
image: Visual Studio 2017

or to build on Linux:
image: ubuntu

https://www.appveyor.com/docs/build-...or-your-builds

[rgleason]

Hoolie

Yes, I thought it would be simple too.

Do you know the answer to the problem?
Otherwise don't snit.
This is volunteer work.

You are like my Dad. He just wanted the answer, but didn't want to know how to get there.

The result was that he kept asking me the same type of question at different times, when he could have figured it out. He was smart, but just lazy.

So if you have any ideas about this, I am all ears.

[rgleason]

Well, I just determined that weather_routing_pi and bsb4_pi both have these lines

VcpkgTripletSelection: Using triplet "x86-windows" from "C:\Tools\vcpkg\installed\x86-windows\"
Vcpkg is unable to link because we cannot decide between Release and Debug libraries. Please define the property VcpkgConfiguration to be 'Release' or 'Debug' (currently 'release').

and weather_routing builds but bsb4 does not.
Therefore I believe this is not the problem

[rgleason]

I've made both appveyor files (bsb4 and weather_routing) the same essentially.
Bsb4 fails and wxrouting completes.

Done Building Project "C:\project\bsb4_pi\build\ALL_BUILD.vcxproj" (default targets) -- FAILED.
Done Building Project "C:\project\bsb4_pi\build\package.vcxproj" (default targets) -- FAILED.
Done Building Project "C:\project\bsb4_pi\build\bsb4_pi.vcxproj" (default targets) -- FAILED.Done Building Project "C:\project\bsb4_pi\build\ALL_BUILD.vcxproj" (default targets) -- FAILED.
Done Building Project "C:\project\bsb4_pi\build\package.vcxproj" (default targets) -- FAILED.

[/QUOTE]
Yet in dir c:\project\bsb4_pi\build we find that the three files that failed do exist! :

05/14/2019 09:53 PM 46,172 ALL_BUILD.vcxproj05/14/2019 09:53 PM 273 ALL_BUILD.vcxproj.filters
05/14/2019 09:53 PM 45,855 bsb4-i18n.vcxproj
05/14/2019 09:53 PM 273 bsb4-i18n.vcxproj.filters
05/14/2019 09:53 PM 49,496 bsb4-po-update.vcxproj
05/14/2019 09:53 PM 687 bsb4-po-update.vcxproj.filters
05/14/2019 09:53 PM 54,647 bsb4-pot-update.vcxproj
05/14/2019 09:53 PM 866 bsb4-pot-update.vcxproj.filters
05/14/2019 09:53 PM 7,327 bsb4_pi.sln
05/14/2019 09:53 PM 62,899 bsb4_pi.vcxproj
05/14/2019 09:53 PM 1,180 bsb4_pi.vcxproj.filters
05/14/2019 09:53 PM 12,305 PACKAGE.vcxproj
05/14/2019 09:53 PM 515 PACKAGE.vcxproj.filters
05/14/2019 09:53 PM 25,032 CMakeCache.txt

[rgleason]

Then I tried to compile bsb4 locally Windows MSVS (ov42-ov48 wxWidgets 3.0.2) and the appropriate opencpn.lib. I thought it would work.


I get the same error and the path for finding opencpn.lib is incorrect for a standalone compile and appears to be looking in the wrong place.


So in conclusion, the CMAKE files need to be fixed for standalone compiling before I can build this plugin. Sorry JohnK