Hi Warren

you don't need change to to configname flex you can just add MXRoyale SWC

for example in asconfig.json or VSCode:

"library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],
"js-library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],

I think just need the second, but try first both.

in Maven will be something like:

<dependency>
<groupId>org.apache.royale.framework</groupId>
<artifactId>MXRoyale</artifactId>
<version>${royale.framework.version}</version>
<type>swc</type>
<scope>provided</scope>
<classifier>js</classifier>
</dependency>

I plan to create a jewel config that will add that, but maybe as we
separate MXRPC from MXRoyale some day

El jue., 24 sept. 2020 a las 18:45, wkoch (<[email protected]>)
escribió:

> Sorry about that.  I thought I had the right one.  I did get past the
> error I
> was getting.  I needed to include  +configname=flex in the compiler
> options.
> Now I have services-config issues but that's gotta be on my end.
>
>
>
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to