Some errors in your pubspec.yaml?

[rekire]

I just found your library and started looking at your code, I'm a bit confused about some details. You marked in your pubspec.yaml that you don't intend to publish it publish_to: 'none', but it is public on pub.dev.

On pub.dev are just Android and Web capabilities listed, but I see again in the pubspec targets for iOS, Linux, macOS and Windows. Are those not production ready? I also noticed that you use two packages for the darwin platforms (iOS and macOS) that is most likely not required. Are you aware of that?

[josxha]

You marked in your pubspec.yaml that you don't intend to publish it publish_to: 'none', but it is public on pub.dev.

Hi @rekire, we need to have this publish_to: 'none' temporarily until the maplibre_ios package is on pub.dev. Otherwise pub get won't run successfully as it uses maplibre_ios from a path dependency. Maybe we can get around this more early by using melos.

On pub.dev are just Android and Web capabilities listed, but I see again in the pubspec targets for iOS, Linux, macOS and Windows. Are those not production ready?

Yes, android and web are released on pub.dev. We are currently polishing support for the initial iOS release in version 0.3.0. Feel free to test it out and check if you notice any problems. Mind that you need to enable the Swift Package Manager to be able to use it.

I also noticed that you use two packages for the darwin platforms (iOS and macOS) that is most likely not required. Are you aware of that?

That's interesting. I've seen some projects to use a darwin directory for some shared classes but wasn't aware that you could get rid of the separation entirely. How does it work?

[rekire]

Hi rekire, we need to have this publish_to: 'none' temporarily until the maplibre_ios package is on pub.dev. Otherwise pub get won't run successfully as it uses maplibre_ios from a path dependency. Maybe we can get around this more early by using melos.

Thank you for clarification. There is always a reason. I personally never used melos so I don't know.

Yes, android and web are released on pub.dev. We are currently polishing support for the initial iOS release in version 0.3.0. Feel free to test it out and check if you notice any problems. Mind that you need to enable the Swift Package Manager to be able to use it.

I added the SPM support for one of my packages, too but I'm still not sure how to actually use it.

That's interesting. I've seen some projects to use a darwin directory for some shared classes but wasn't aware that you could get rid of the separation entirely. How does it work?

Basically you declare the module in your federated package like this (I use my autologin package as example):

platforms:
  ios:
    pluginClass: AutologinPlugin
    dartPluginClass: AutologinDarwin
    sharedDarwinSource: true
  macos:
    pluginClass: AutologinPlugin
    dartPluginClass: AutologinDarwin
    sharedDarwinSource: true

The darwin package will declare both platforms as well.

The swift code will need some conditional imports like:

#if os(iOS)
import Flutter
#elseif os(macOS)
import FlutterMacOS
#endif

That was for my use case quite easy.

[josxha]

Thank you for clarification. There is always a reason. I personally never used melos so I don't know.

I turned the project into a pub workspace, apparently this did the trick as well.

I added the SPM support for one of my packages, too but I'm still not sure how to actually use it.

Oh, then you propably already ran flutter config --enable-swift-package-manager. But that's basically it, Flutter should take care of the rest.

Basically you declare the module in your federated package like this (I use my autologin package as example):

Thanks a lot for the guidance. I might try it out in one of the following versions. 👍

[rekire]

@josxha I tried it again to run the windows build just to see where it starts crashing or something similar, instead it just doesn't build.

Without changes I get:

CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
  Could NOT find JNI (missing: JAVA_INCLUDE_PATH JAVA_INCLUDE_PATH2 JVM)

When I add this to the top of example/windows/CMakeLists.txt:

set(JAVA_HOME "C:/path/to/jdk-21.0.2")
set(JAVA_INCLUDE_PATH "${JAVA_HOME}/include")

The error changes to:

C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(166,5): error MSB3073: The command "setlocal [C:\dev\flutter-maplibre\example\build\windows\x64\INSTALL.vcxproj]

Which leads me to think that somewhere internal a powershell is used instead of cmd. Do you have an idea what's going on?

[josxha]

I tried it again to run the windows build just to see where it starts crashing or something similar, instead it just doesn't build.

Oh I see, there was a misunderstanding on my side. I thought that you were trying to run the package on iOS.
Unfortunately, the package does currently not support windows, macos or linux. The package uses platform views for iOS and android which aren't available on desktop (macos only limited). There is an open discussion about an alternative implementation in: #234

The mentioning of these platforms in the pubspec.yaml has no meaning. It's was generated when creating the initial project.

The accurate list of supported platforms is the one at the top:

flutter-maplibre/pubspec.yaml

Lines 15 to 18 in 3e6c428

	platforms:
	android:
	ios:
	web: