Need help with barrels

I'm looking for some help with Barrels. I'm trying to remove some code out of my main project and put them into a barrel. The current problem is that I'm unable to test my barrel code.

I'm doing stuff with the CLI as described here: https://developer.garmin.com/connect-iq/core-topics/shareable-libraries/

> barreltest -o <output.barrel> -f <barrel.jungle> -d <device_id>

This however doesn't do much. Also, the output doesn't seem to be a ZIP container with code, but a compiled project of sorts. However running monkeydo on it does nothing, it just hangs. It does open the device that was used to barreltest the code with, but other than that it just does nothing visible.

I opened a Virtual machine with VS code to see what the extension there does, but it claims barrels cannot be tested without an app present. Which led me to inspect the .barrel from barreltest and try and run monkeydo with it. But no success.

I made a small demo barrel to show what I'm doing:

https://github.com/waterkip/Monkey-Barrel-Demo

Does anyone know how to test barrel code? I have a small guess it needs a small side car application, but that would make barrel creation "complicated" and "complex" as you would need to include a test app in the barrel and exclude that from building with the barrelbuild process..?

0 jim_m_58 over 4 years ago

When I do barrels, I always have an app that uses the barrel and test it that way. For me, when I started with barrels, it was the case where I was moving code out of an app and into a barrel, so as I moved stuff, I could use the main app to test.

Something else to note is that using a barrel has overhead vs just using the code, and there are some devices without barrel support, so when I write a barrel, I do it in such a way that the barrel can be used, or with jungles, I can just use the mc/etc directly.

A .barrel file is a zip file, and there is a "content" folder in it so the barrel can be built when the main app is compiled. I use eclipse of VS Code with this, never CLI

0 jim_m_58 over 4 years ago

By the way, have you looked at the barrels Garmin has on github? Those may help explain how to do things.

https://github.com/garmin/connectiq-apps/tree/master/barrels

There's also this in the doc about barrels:

https://developer.garmin.com/connect-iq/core-topics/shareable-libraries/#shareablelibraries

0 waterkip over 4 years ago in reply to jim_m_58

Yes, I looked at the docs of Garmin:

> I'm doing stuff with the CLI as described here: https://developer.garmin.com/connect-iq/core-topics/shareable-libraries/

I also looked at their github, which is where I saw that they included tests, such as https://github.com/garmin/connectiq-apps/tree/master/barrels/Semicircles

However, they use classes in their examples and not modules as exampled in the docs. It also doesn't show HOW they test their barrels as there are no build instructions. However, if I use their sample projects with barreltest it also hangs and does not execute the tests: https://github.com/waterkip/connectiq-apps/tree/semicircle-build/barrels/Semicircles

0 waterkip over 4 years ago

I'm really stupid, or Barrels are really broken. I'm unable to even include a barrel into my project(s). It is either the undefined symbol or just whole namespaces that cannot be imported.

Unknown module MonkeyBarrelDemo.Demo in using or import clause

Does anyone have a demo barrel + project that I can use as a test case locally?

0 jim_m_58 over 4 years ago in reply to waterkip

How are you adding the barrel? in VS Code, you have Monkey C:Configure Monkey Barrel.

When you adda Barrel, things happen in two files.

In barrels.jungle, you'll get:

ClockMisc = C:\Users\James\workspace-prod\ClockMisc\bin\ClockMisc-1.0.0.barrel

base.barrelPath = $(base.barrelPath);$(ClockMisc)

and in manifest.xml,

<iq:barrels>

<iq:depends name="ClockMisc" version="1.0.0"/>

</iq:barrels>

What is the module name in your barrel? With the above, I have

module ClockMisc {

//...

}

0 waterkip over 4 years ago in reply to jim_m_58

That is how I add my barrels. With the exception of the barrels.jungle. I just add that section to the monkey.jungle file so I don't need to concatenate the files at the build command with -f "monkey.jungle;barrel.jungle", but the result is the same.

0 waterkip over 4 years ago

See https://github.com/waterkip/MonkeyBarrelInclude-Demo and https://github.com/waterkip/Monkey-Barrel-Demo

0 waterkip over 4 years ago in reply to waterkip

On https://github.com/waterkip/Monkey-Barrel-Demo checkout branch non-working-example

0 jim_m_58 over 4 years ago in reply to waterkip

Did you include the entry in manifest.xml too? It's not just in the jungle file.

Which SDK are you using? If you are using the latest beta, I'd go back to 4.1.4 in case it's an issue with the beta

0 waterkip over 4 years ago in reply to jim_m_58

See the github links, you can see exactly what my project is doing. The SDK which I tested with are 4.1.3 and 4.1.4